Support for Node 6 (needed for AWS Lambda)
See original GitHub issueWould be great if you could adjust the babel compilation settings in a way that the resulting output also runs in Node 6 (or even lower). Otherwise it’s not possible to deploy apps using apollo-upload-server
to AWS Lambda.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
AWS Lambda Supports Node.js v6.10
You can now develop your AWS Lambda functions using Node.js v6.10. You simply upload your Node code as a ZIP using the AWS...
Read more >AWS Lambda Now Has Support for Node.js 16 Runtime - InfoQ
Recently AWS announced that Node.js version 16 supports its Function as a Service (FaaS) AWS Lambda and is in active LTS status (ready...
Read more >Support for Node.js in AWS Lambda slowly, but surely, evolves
Unfortunately, developers can only use the specific Node.js version that AWS Lambda supports and can't upgrade to take advantage of new features ...
Read more >NodeJS Lambda | The Complete Guide to Get Started 101
You'll need a NodeJS runtime first. Now you must install a NodeJS version that AWS Lambda supports. In this post, NodeJS 8.10 runtime...
Read more >AWS Lambda support for Node.js 10: Should you switch to v14?
AWS Lambda also only supports the long-term support (LTS) versions of Node.js: the even version numbers. Currently, versions 10, 12, and 14 are ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just published
apollo-upload-server
v4.0.0-alpha.2 🚀I know how to do it; we used to support Node.js v6.4. I and a lot of other package authors consciously chose to drop support for v6 since it is a year and a half old now; v7.6 with native async/await has been out for almost a year and v8.x LTS is out now.
The min required Node.js version has always been visible and accurate in package.json
engines
so there should not have been nasty surprises. As for best practices, AWS should really provide reasonably recent versions of Node.js, especially if users are becoming increasingly frustrated that newer packages are not compatible with the legacy environment.It’s a shame for the majority to lose native async/await, but until AWS Lambda provides more up-to-date versions of Node.js I can trial dropping support back down to Node.js v6.10+. I want everyone to have a great experience using
apollo-upload-server
🙏