Chore: drop Node.js 8 support
See original GitHub issueFollowing up with https://github.com/netlify/cli/issues/1568, we should be good now with dropping Node.js 8 support for the zip-it-and-ship-it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
chore: drop node 8 support #9423 - facebook/jest · GitHub
Summary Node v8.x stopped support since 1 january 2020. https://github.com/nodejs/Release I made PR to master because master already has breaking changes ...
Read more >Netlify CLI: Dropping support for Node.js 8 - Updates - Netlify ...
As Node.js 8 is out of the maintenance window we will be dropping support for it and require Node.js 10 in Netlify CLI....
Read more >chore: drop support for Node.js 10 (#6371) · a59a494e64 ... - Gitnet
Playwright requires Node.js 10 or higher. Node.js 8 is not supported, and will cause you to receive this error.
Read more >Node.js Agent version 3.x - Elastic
While the APM agent still supports it, that instrumentation is no longer tested and support will be dropped in the next major version...
Read more >webfont: Versions | Openbase
Drop support for Node.js 8 and Node.js 11 (please use Node.js 10, 12 or higher) ... Chore: minimum require svgicons2svgfont version is now...
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

This sounds great, thanks for following up on this @ehmicky!
I’ve assigned this to myself, I’m happy to take it from here.
After doing some research, I would suggest that we directly drop Node 8 support in the whole package (including
list()andlistAll()) due to the very minimal risk:@netlify/functions-utilsdirectly@netlify/functions-utilsisnetlify-plugin-inline-functions-env. From Humio logs, it appears that no site using this plugin is both installing it inpackage.jsonand using Node 8utils.functionswhile using Node 8 seems minimal, although there is no available data about thisWhat are your thoughts?
Note: this would also moving the
require('archiver')statement back to the top-level scope.