gatsby
5.16.1 · 10 Feb 2026MIT252.9k / weekRepositoryHomepagenpmAtom feed
Upgrading gatsby from 0.8.11 to 0.9.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 0
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- breaking0.9.0
Security
1 advisory still affects 0.9.0
- Gatsby develop server has Local File Inclusion vulnerabilitymoderate · GHSA-c6f8-8r25-c4gc
Upgrading to 4.25.7 clears it.
9 other lines we could not sort, mostly version bumps
- 0.9.0
Install Gatsby —
npm install --save gatsby - 0.9.0
Install new Babel 6 dependencies (they must be installed locally) —
npm install --save babel-plugin-add-module-exports babel-preset-es2015 babel-preset-react babel-preset-stage-1andnpm install --save-dev babel-preset-react-hmre. - 0.9.0
Uninstall old Babel 5 dependencies (if you added any).
- 0.9.0
The
linkfunction fromgatsby-helpers.jswas renamed toprefixLinkto clarify its purpose. - 0.9.0
Your
.babelrcfile needs to be upgraded to look like: - 0.9.0
If you modified the default Webpack config in
gatsby.config.js, this functionality is now moved togatsby-node.jsand instead of using module.exports, export your config modification function asmodifyWebpackConfig. See the updated instructions in the README. - 0.9.0
If you were differentiating between pages with content (like .md files) and pages without (like pages/profile.js) by looking for truthy
page.data, you'll now need check for truthypage.data.body. - 0.9.0
If your site is under version control, you might want to ignore the new auto-written module
.gatsby-context.js. - 0.9.0
rare if you used the
rewritePath,onRouteChangehooks in your app.js — app.js is now not supported. Instead you should exportrewritePathingatsby-node.jsandonRouteChangeingatsby-browser.js. The function signatures didn't change. These new files will be gaining more functionality in future releases.