base-x is not compatible with AWS Lambda Execution Environment (Node LTS 4.3.2)
See original GitHub issuePackage engine requirement makes base-x incompatible with AWS Lambda deployments. Lambda’s current execution environment is Node LTS 4.3.2 and is not expected to move to LTS 6 until April 2017.
"engines": {
"node": ">=4.5.0"
}
Is there any reason this cannot be revised back to 4.3.2?
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Lambda runtimes - AWS Documentation
The Lambda execution environment provides a runtime interface for getting invocation events and sending responses. You can deploy a custom runtime alongside ...
Read more >Node.js 16.x runtime now available in AWS Lambda
This runtime version is supported by functions running on either Arm-based AWS Graviton2 processors or x86-based processors. Using the Graviton2 ...
Read more >Node.js 18.x runtime now available in AWS Lambda
You can now develop AWS Lambda functions using the Node.js 18 runtime. This version is in active LTS status and considered ready for...
Read more >AWS Lambda Supports Node.js 4.3
To get started deploying your Node. js code as a Lambda function, you simply upload your node code as a ZIP through the...
Read more >AWS Lambda releases
js 16 uses Amazon Linux 2. For details, see Building Lambda functions with Node.js. May 11, 2022. Lambda function URLs. Lambda ...
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
Deprecated
2.0.1->2.0.4
. Published2.0.5
without safe buffer changes or engine restrictions Published3.0.0
with safe buffer changes and4.5.0
engine restriction.@fanatid I rebased/squashed and force pushed from 35cae44359f9df36ee4fe5c9e3ae156d023467d3, to avoid confusion and keep the extra fixes that were added since.
See https://github.com/cryptocoinjs/base-x/commits/master for the 5 commits to review (if needed).
Refreshed browser a few times, but still isn’t showing up for me. Weird. Maybe there is some system latency / catching going on, or I’m not looking in the right spot. No worries.