Drop Node.js 12 support in CI
See original GitHub issueNode.js 12 is becoming a burden. We need to drop it to upgrade TypeScript and ESLint. This would also give us an opportunity to drop some hacks around CommonJS named exports. This would also let us drop a work-around for old V8 generator function behavior in streams. Neither of those changes need to be done to close this issue. We need:
- Remove 12 from CI matrixes.
- Update Node.js
engines
properties inpackage.json
where applicable. Soft requirement. - NEWS.md entries.
- This might be a whole-repo breaking change. Dropping an old Node.js version is breaking at least in principle.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Netlify CLI: Dropping support for Node.js version 12 - Updates
As Node.js version 12 reached its official end of life on April 30th 2022. We are going to stop the support and require...
Read more >Drop support for Node.js < 12 · Issue #4164 · rollup ... - GitHub
If we drop support for Node.js < 12, we can update the rollup configuration loader to use the Node.js native loader entirely, effectively...
Read more >Announcing the end of support for Node.js 12.x in the AWS ...
As of Oct 2022, Lambda is planning Node.js 12.x deprecation on Mar 31, 2023. ... We are seeing support drop within the Node.js...
Read more >The Difference Between Node.js 10 LTS and Node.js 12 LTS
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Read more >circleci/node@5.0.3
Easily install Node.js and its package managers (npm, yarn). Best of all, install your packages with caching enabled by default. Supports ...
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
No longer necessary for TS 4.5 update so reassigning.
Yes, please do!