JS CDK: mismatch between documented (10.13.0) and actual (14.15.0) minimum Node.js version
See original GitHub issueGeneral Issue
The Node.js version requirements in README.md and the engines section of package.json differ
The Question
README.md states
Node.js ≥ 10.13.0
However, in 9527bfa the Node.js version required in the engines
section of package.json
s was bumped to 14.15.0. One of these two is not correct.
CDK CLI Version
2.2.0
Framework Version
No response
Node.js Version
No response
OS
No response
Language
Typescript
Language Version
No response
Other information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
CDK docs could be clearer about Node.js dependency #291
It seems that 10.3 is required at a minimum, but it's not completely clear if versions newer than 13.6 are compatible. It's also...
Read more >How to solve CDK CLI version mismatch - Stack Overflow
I encountered this issue with a typescript package, after upgrading the cdk in package.json. As Maciej noted upgrading did not seem to work....
Read more >Prevent npm install for not supported Node.js versions
Use a local npm configuration to prevent users from installing your module/project with an unsupported Node.js version.
Read more >Working with the AWS CDK - AWS Documentation
All AWS CDK applications require Node.js 10.13 or later, even if you work in Python, Java, C#, or Go. You may download a...
Read more >Node v14.0.0 (Current)
It is expected that there will be an ABI mismatch on ARM between the Node.js binary and native addons. Native addons are only...
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 FreeTop 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
Top GitHub Comments
I’ve created a PR to update this in the repo.
Thanks @tmokmss, I’ll forward this to our docs writer
⚠️COMMENT VISIBILITY WARNING⚠️
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.