We're excited to announce Serverless Framework v1.20.
This is another release which mostly focuses on small enhancements and bug fixes. Big thanks to everyone in our community who reported bugs, opened issues and joined in on discussions.
You can find a complete list of all the updates in the CHANGELOG.md file.
This release contains lots of hard work from our beloved community, and wouldn't have been possible without passionate people who decided to spend their time contributing back to make the Serverless Framework better.
Huge round of applause to all of the contributors who submitted changes for this release:
The Serverless Team is currently working on some exciting new projects which will be announced at Emit conference on August 17th.
As a result, upcoming Serverless releases will likely focus on bug fixes and minor enhancements. But thanks to you, our stellar community, we still have some cool stuff coming up.
Do you want to help out and improve the Serverless Framework?
Great! We've compiled a list with some of the most wished features to make it easier for you to find areas where we could most use a hand.
We already started a WIP implementation with the following PR, but for now it only provides a partial solution. Do you have any ideas how we can improve the support for this feature?
Services can grow significantly in size. We've worked on different solutions for this problem (see this PR) but we're still not 100% there yet.
We're currently looking for a way to implement basic request validation via raw CloudFormation.
ApiGateway::Deployment resource has a random string in its name so that deployments are re-triggered on AWS end.
This makes it hard to create other CloudFormation resources which dependend on it.
It would be nice to skip resource delpoyments if the corresponding resource already exists (e.g. when using DynamoDB tables). Could you think of a reliable, production ready way that will detect which resources deployments could be skipped?
arns are used everywhere in CloudFormation. However some of our event sources don't support all the different types of intrinsic functions which can be used to reference
It would be great to have a global
arn parser which can be re-used throughout the whole codebase. This parser could also be exposed to the framework user e.g. via
this.provider.findAllCfReferences(), so that plugin authors can benefit from this functionality as well.
This list is just a gist with some of the most wished features from our community.
We have lots of other issues where you could leave some feedback or jump directly into the implementation.
Additionally PR reviews are also highly welcomed as they greatly speed up the time-to-merge.
Emit is today! We're meeting up at The Pearl SF to discuss the future of serverless architectures. Catch all the live-tweets with #EmitConf, and/or follow Emit at @emitconf and @goserverless. Subscribe to our newsletter to catch all the followup videos and blog posts.
The Serverless Examples Repository is an excellent resource if you want to explore some real world examples, or learn more about the Serverless Framework and serverless architectures in general.
Serverless provides a completely customizable and pluggable codebase. Our community has written a vast amount of awesome plugins you can use to further enhance the capabilities of the Framework. You can find the full list at our Serverless Plugins Repository.
Don't hestitate to open up a PR over there if you've authored or found a new Serverless plugin!
To get started, pop open your terminal & run
npm install serverless -g
Join 12,000+ other serverless devs & keep up to speed on the latest serverless trends