github-action
serverless-bundle
github-action | serverless-bundle | |
---|---|---|
3 | 3 | |
641 | 530 | |
1.2% | 0.0% | |
2.0 | 7.4 | |
3 months ago | 5 months 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-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?
ActionServerless - Use GitHub Actions to create a Serverless service.
serverless-esbuild - 💨 A Serverless framework plugin to bundle JavaScript and TypeScript with extremely fast esbuild
git-cliff-action - GitHub action to generate a changelog based on the Git history
serverless-plugin-warmup - Keep your lambdas warm during winter. ♨ [Moved to: https://github.com/juanjoDiaz/serverless-plugin-warmup]
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project
PatrickJS-starter - MFE Starter
php-cs-fixer-ga - GithubAction for PHP-CS-Fixer
elasticmq - In-memory message queue with an Amazon SQS-compatible interface. Runs stand-alone or embedded.
climateclock-gh-action - Action to update markdown with climateclock.world
serverless-webpack - Serverless plugin to bundle your lambdas with Webpack
serverless-github-actions
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.