@jahed/aws-lambda-package

Packages your code to be executed on AWS Lambda.

Stats

StarsIssuesVersionUpdatedCreatedSize
@jahed/aws-lambda-package
1.0.43 years ago3 years agoMinified + gzip package size for @jahed/aws-lambda-package in KB

Readme

@jahed/aws-lambda-package

Packages your NodeJS code to be executed on AWS Lambda.

Travis npm Patreon Liberapay

Installation

yarn add -D @jahed/aws-lambda-package

Workspaces

If you're using workspaces, install it at the root package.

yarn add -W -D @jahed/aws-lambda-package

Usage

Building Single Packages

Running aws-lambda-package will do the following:

  • Run yarn pack to create a tgz similar to yarn publish
  • Extract the tgz to a temporary directory
  • Run yarn install --production on the directory
  • Create a ZIP of the directory's contents on your current working directory.
  • You will have to upload your ZIP to AWS Lambda or S3 manually (or using your own script)
yarn aws-lambda-package

If you're using workspaces and just want to build one workspace, you can do the following:

yarn workspaces your-package-name aws-lambda-package

Building all your workspaces

You can build all of your workspaces at once by running aws-lambda-workspaces at the root package.

yarn aws-lambda-workspaces

Caveats

  • To ensure full compatibility, you may need to run aws-lambda-package in an environment similar to AWS Lambda. Try out docker-lambda if you run into this issue.

Reasoning

A lot of ZIP tools assume Windows line separators (\) are okay. AWS Lambda however doesn't support these separators. So I made this project to work across systems and remove as many caveats as possible.

License

MIT

If you find any bugs or have a feature request, please open an issue on github!

The npm package download data comes from npm's download counts api and package details come from npms.io.