Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(blog): bump node min version -> remove local domain #22490

Merged
merged 1 commit into from Mar 23, 2020
Merged

fix(blog): bump node min version -> remove local domain #22490

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/blog/2020-03-20-dropping-support-for-node-8/index.md
View file
Open in desktop
Expand Up @@ -7,7 +7,7 @@ tags:
- releases
---

Effective in Gatsby v2.20.0, we are making a potentially breaking change and dropping support for Node 8. The new minimal Node version that Gatsby supports is 10.13.0. We are doing it in a minor release as per [Gatsby Node Support Policy](https://www.gatsbyjs.org/docs/upgrading-node-js/#gatsbys-nodejs-support-policy).
Effective in Gatsby v2.20.0, we are making a potentially breaking change and dropping support for Node 8. The new minimal Node version that Gatsby supports is 10.13.0. We are doing it in a minor release as per [Gatsby Node Support Policy](/docs/upgrading-node-js/#gatsbys-nodejs-support-policy).

Node 8 reached end of life in December of 2019. There were deprecation warnings about it in previous Gatsby versions. Less than 3% of Gatsby users are still using Node 8. Some libraries that Gatsby or Gatsby plugins depend on have dropped Node 8. This meant that we were locked into using an older version of packages and couldn't apply the latest bugfixes (that was a case with, e.g., `sharp` or `got`). Some performance and memory improvements were only possible with newer versions of Node too.

Expand All @@ -17,4 +17,4 @@ Evaluating all those factors, we decided that it's better to drop Node 8 support

You should be fine if you have already upgraded your Node version to 10.13.0 or higher as you won't be affected.

Otherwise, follow the [Upgrading your Node guide](https://www.gatsbyjs.org/docs/upgrading-node-js).
Otherwise, follow the [Upgrading your Node guide](/docs/upgrading-node-js).