Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

feat: remove Node 8 support #478

Merged
merged 4 commits into from
May 26, 2021
Merged

feat: remove Node 8 support #478

merged 4 commits into from
May 26, 2021

Conversation

eduardoboucas
Copy link
Member

@eduardoboucas eduardoboucas commented May 21, 2021

- Summary

Officially removes support for Node 8.

Closes #294.

- Test plan

N/A

- A picture of a cute animal (not mandatory but encouraged)

a-beary-sincere-goodbye

@eduardoboucas eduardoboucas added the type: feature code contributing to the implementation of a feature and/or user facing functionality label May 21, 2021
@github-actions
Copy link
Contributor

github-actions bot commented May 21, 2021

⏱ Benchmark results

Comparing with 67cb622

  • largeDepsEsbuild: 11.8s ⬇️ (0.12% decrease)
  • largeDepsZisi: 1m 1.3s ⬇️ (3.90% decrease)

package.json Outdated
@@ -94,7 +94,7 @@
"tmp-promise": "^3.0.2"
},
"engines": {
"node": ">=8.3.0"
"node": ">=10.3.0"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was torn on whether to use 10.0.0. which we technically should support, or 10.3.0, the lowest version we test against in the CI. @ehmicky what do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I answered in the other comment. 👍

package.json Outdated
@@ -94,7 +94,7 @@
"tmp-promise": "^3.0.2"
},
"engines": {
"node": ">=8.3.0"
"node": ">=10.3.0"
Copy link
Contributor

@ehmicky ehmicky May 21, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since cli is using >=10.18.0, should we re-use it?

https://github.com/netlify/cli/blob/2a662e4546520f31e003306b2d3e120d021f8ce4/package.json#L14

Link to builds usage data from 2 months ago.

Note: if we do so, we would want to update the Node.js version running GitHub actions tests.

cc @JGAntunes @erezrokah too

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That works for me. I'll update.

@@ -5,33 +5,10 @@
dependencyDashboard: true,
automerge: false,
packageRules: [
{
// Those cannot be upgraded to a major version until we drop support for Node 8
packageNames: [
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a possibility that some of these packages will also have problems in Node 10, but I think we can wait for Renovate to create the PRs and we evaluate them one-by-one. Unless anyone thinks otherwise?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Absolutely 👍

Many packages from Sindre Sorhus have dropped support for Node 10 recently, but we could check one by one.

@@ -5,33 +5,10 @@
dependencyDashboard: true,
automerge: false,
packageRules: [
{
// Those cannot be upgraded to a major version until we drop support for Node 8
packageNames: [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

This was referenced May 24, 2021
@eduardoboucas eduardoboucas merged commit aca350a into main May 26, 2021
@eduardoboucas eduardoboucas deleted the feat/node8-support branch May 26, 2021 14:45
Skn0tt pushed a commit to netlify/build that referenced this pull request May 21, 2024
* feat: remove Node 8 support

* chore: fix linting error

* chore: update minimum Node version
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
init/deprecate-node-8 type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Chore: drop Node.js 8 support
2 participants