Npm install serverless-plugin-typescript

#Npm install serverless plugin typescript code#

Incorrect serverless deployment console output and having successful deployments when there are OpenApi issues is unsatisfactory.Resources deleted from serverless configuration are not removed upon redeployment.Use of credential roles rather than policies for lambda resources is undesirable.Extensive CloudFormation configuration within Serverless YAML is less than ideal and starts to defeat some of the purpose for using Serverless in first place.The lambda function reference identifier being used with the OpenApi specification document is complex and not intuitive.Using CloudFormation and Serverless variables within the separate OpenApi specification creates undesired co-dependencies.

The mix of CloudFormation and Serverless variables adds to complexity.

see progress on serverless-heaven/serverless-webpack#397

Cannot add sourcemap support import globally to each file.

After executing the lamdba and revisiting the screen the validator was then shown to be selected

Experienced a bug in AWS UI where no request validator was shown to be selected even though set.

schema allOf not supported by AWS lambda.

AWS only supports JSON schema 0.4 therefore using string format 'date' within OpenApi is not supported as it was only introduced into JSON schema 0.7.

event configuration in serverless.yaml gets ignored when defining a separate gateway resource for openApi and serverless deployment console output with regards to endpoints is incorrect.

openApi errors are not shown when deploying which is misleading and concerning.

the reference to a named layer must start with a capital and end with 'LamdbaLayer'.

The plugin serverless-plugin-layer-manager was included so that node_modules based off a layers package.json file are updated appropriately upon each package/deploy

Serverless by itself can only reference layer content that pre exists and is the correct path format.

Unfortunately the role solution does mean additional latency and it is suggested that in order to keep the latency down to use appropriate regional AWS STS. Instead of creating manually policy resources for each function an appropriate credentials role was added to each x-amazon-apigateway-integration. Consequently permission errors occur when attempting to execute endpoints.

not defining the http events in serverless yaml prevents serverless generating AWS::IAM::Policy resources for each function.

Solution was for tsconfig not to transpile to older versions and set module property to 'ES6' and target as 'es2018' within tsconfig. Module import style must be correct for webpack to process imports.

webpack was not performing tree shaking.

Had to add '.js' to webpacks 'resolve.extensions'

javascript library files for importing 'source-map-support/register' were not being found.

Additionally had to add tsconfig-paths-webpack-plugin to webpack so it is aware that transpiling needs to change imports to relative in generated JS output

Solution was to set baseUrl in tsconfig.json, however transpiled output still had non relative imports causing javascript errors.

got compilation errors when not using relative paths for local imports.

Needed to change target in tsconfig from ESNext to ES2018 in order to support elvis operator.

Solution was to remove nodeExternals() from being excluded in webpacks externals meaning tree shaking could take place

#Npm install serverless plugin typescript code#

no code imported from node_modules was being included at all.This maybe due to use of serverless-webpack plugin Changed webpack devtool value to 'nosources-source-map', but is kind of strange how original devtool value of 'source-map' didn't include sources. After this change sourceMap files started to include actual source code. added terser-webpack-plugin in order to override webpacks default behaviour and so that comments of dependent modules are removed.added ts-config-paths-webpack-plugin so that typescript baseUrl is observed.Npm install -D tsconfig-paths-webpack-plugin Npm install -D serverless-plugin-layer-manager serverless-pseudo-parameters Sls config credentials -provider aws -key YOUR_ACCESS_KEY -secret YOUR_SECRET_KEY

Npm install serverless-plugin-typescript