Package Exports
- @aws-cdk/aws-lambda-nodejs
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@aws-cdk/aws-lambda-nodejs) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Amazon Lambda Node.js Library
This is a developer preview (public beta) module. Releases might lack important features and might have future breaking changes.
This API is still under active development and subject to non-backward compatible changes or removal in any future version. Use of the API is not recommended in production environments. Experimental APIs are not subject to the Semantic Versioning model.
This library provides constructs for Node.js Lambda functions.
Node.js Function
Define a NodejsFunction:
new lambda.NodejsFunction(this, 'my-handler');By default, the construct will use the name of the defining file and the construct's id to look up the entry file:
.
├── stack.ts # defines a 'NodejsFunction' with 'my-handler' as id
├── stack.my-handler.ts # exports a function named 'handler'This file is used as "entry" for Parcel. This means that your code is automatically transpiled and bundled whether it's written in JavaScript or TypeScript.
Alternatively, an entry file and handler can be specified:
new lambda.NodejsFunction(this, 'MyFunction', {
entry: '/path/to/my/file.ts'
handler: 'myExportedFunc'
});All other properties of lambda.Function are supported, see also the AWS Lambda construct library.
Configuring Parcel
The NodejsFunction construct exposes some Parcel options via properties: minify, sourceMaps,
buildDir and cacheDir.
Parcel transpiles your code (every internal module) with @babel/preset-env and uses the runtime version of your Lambda function as target.
Configuring Babel with Parcel is possible via a .babelrc or a babel config in package.json.