Remove Node.js 6 and Node.js 8 support
See original GitHub issueFeature Proposal
Description
Both versions have already reached End-of-Life and no longer receive security updates. Supporting those versions, especially 6.x, stops the codebase of leveraging useful features from new ES versions, namely async..await
for instance.
See: https://github.com/nodejs/Release#end-of-life-releases
Similar or dependent issues:
- #6076 (this targetted Node.js 6 as well, but only deprecated Node.js 4)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to completely remove node.js from Windows
How to remove Node.js from Windows: Take a deep breath. Run npm cache clean --force. Uninstall from Programs & Features with the uninstaller ......
Read more >How to completely remove node.js from Windows
Step 3: Now open control panel in the computer. Search for Program and features. Under the program and features click on Uninstall a...
Read more >Manage Node.js versions using asdf - LogRocket Blog
Asdf is an extendible version manager that supports multiple languages like Ruby, Node.js, Elixir, Erlang, Python, and more, all at once.
Read more >Node v18.6.0 (Current)
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Read more >How To Reinstall NPM And Node.js On Any System
a) Reinstalling using a Node version manager · Go to the Windows Control Panel and uninstall the Node.js program. · If any Node.js...
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
@ronkorving I hope we will release v2 within 1 month time frame. Stay tuned
I’ve also renamed it to “Remove … support”, as technically we plan to remove support, not just deprecate.
Also as v6 and v8 are EOL’d I think they’re naturally assumed as deprecated, I assume it’s no point to add some extra warning logs in v1 for that.