serverless-plugin-warmup
serverless-bundle
serverless-plugin-warmup | serverless-bundle | |
---|---|---|
1 | 3 | |
951 | 531 | |
- | 0.0% | |
8.0 | 7.4 | |
about 2 years ago | 5 months ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
serverless-plugin-warmup
-
Structuring a Real-World Serverless App
We use the package.json at the project root to install the dependencies that will be shared across all the services. For example, if you are using serverless-bundle to optimally package the Lambda functions, or using the serverless-plugin-warmup to reduce cold starts, they should be installed at the root level. It doesn’t make sense to install them in each and every single service.
serverless-bundle
-
Migrating a classic Express.js to Serverless Framework
As you can see in the above handler.js file, we're getting CommonJS instead of modern JavaScript or TypeScript. To get these, you need webpack or some other bundler. serverless-webpack exists if you want full control over your ecosystem, but there is also serverless-bundle that gives you a set of reasonable defaults on webpack 4 out of the box. We opted into this option to get us started quickly.
-
Announcing a Serverless Microservices Template with GraphQL
One of the most important aspects of serverless development is keeping an eye on your bundle sizes and to reduce cold start times on Lambda. Keeping this in mind, the template utilizes serverless-esbuild and serverless-analyze-bundle-plugin to provide function analysis out-of-the-box. I opted for serverless-esbuild over serverless-bundle for a few reasons:
-
Structuring a Real-World Serverless App
We use the package.json at the project root to install the dependencies that will be shared across all the services. For example, if you are using serverless-bundle to optimally package the Lambda functions, or using the serverless-plugin-warmup to reduce cold starts, they should be installed at the root level. It doesn’t make sense to install them in each and every single service.
What are some alternatives?
serverless-python-requirements - ⚡️🐍📦 Serverless plugin to bundle Python packages
serverless-esbuild - 💨 A Serverless framework plugin to bundle JavaScript and TypeScript with extremely fast esbuild
serverless-chrome - 🌐 Run headless Chrome/Chromium on AWS Lambda
github-action - :zap::octocat: A Github Action for deploying with the Serverless Framework
homepage - Seed Homepage
PatrickJS-starter - MFE Starter
serverless-plugin-warmup - Keep your lambdas warm during winter. ♨
elasticmq - In-memory message queue with an Amazon SQS-compatible interface. Runs stand-alone or embedded.
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
serverless-webpack - Serverless plugin to bundle your lambdas with Webpack