github-action
serverless-webpack
| github-action | serverless-webpack | |
|---|---|---|
| 3 | 5 | |
| 641 | 1,719 | |
| 1.2% | 0.1% | |
| 2.0 | 9.3 | |
| 3 months ago | about 20 hours ago | |
| Dockerfile | JavaScript | |
| Apache License 2.0 | 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.
github-action
-
Migrating a classic Express.js to Serverless Framework
Our deploys don't deploy on merges to main. For this though, we can just use the official Serverless Github Action. Alternatively, we could purchase a license to the Serverless Dashboard, but this option is a bit more expensive, and we're not using all of its features on this project. However, we've used this on other client projects, and it really helped us manage and monitor our deployments.
-
Consuming SQS Messages with Lambda(TypeScript)
Now that we have our Serverless Deployment script ready, we can deploy this to AWS Lambda using this script with Github Actions.
-
Publicando aplicações serverless com github actions
Link da action no github https://github.com/serverless/github-action
serverless-webpack
-
Using pure ESM npm packages in serverless-webpack bundles
Since I was using serverless-webpack along with Prisma's serverless-webpack-prisma helper, this meant a bit of extra Webpack config setup to get it all using the same module syntax without the usual dreaded 'Unexpected token export' or import error from Node.
-
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.
-
Running a scalable & reliable GraphQL endpoint with Serverless
cd app-backend/dynamodb yarn install To test the GraphQL endpoint locally on my machine, I’m using these three plugins for the Serverless Framework: Serverless Offline, Serverless Webpack and Serverless DynamoDB Local.
-
How we keep our Serverless deploy times short and avoid headaches
Serverless Webpack
-
Package your NodeJS Lambda functions individually with esbuild for faster cold-start times
The serverless framework supports an excellent workflow with the serverless-webpack plugin to package your functions individually with webpack. For AWS SAM, it's probably worth checking out the aws-sam-webpack-plugin, but I've found it far simpler to configure esbuild to perform the same task.
What are some alternatives?
ActionServerless - Use GitHub Actions to create a Serverless service.
esbuild - An extremely fast bundler for the web
serverless-bundle - Optimized packages for ES6 and TypeScript Node.js Lambda functions without any configuration.
serverless-jetpack - A faster JavaScript packager for Serverless applications.
git-cliff-action - GitHub action to generate a changelog based on the Git history
serverless-plugin-tree-shake - Shake the dependency tree and only package files needed
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
lambda-layer-sharp - An AWS Lambda Layer for the Sharp node module. Automatically published on updates.
php-cs-fixer-ga - GithubAction for PHP-CS-Fixer
chrome-aws-lambda - Chromium Binary for AWS Lambda and Google Cloud Functions
climateclock-gh-action - Action to update markdown with climateclock.world
Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.