gatsby
5.16.1 · 10 Feb 2026MIT252.9k / weekRepositoryHomepagenpmAtom feed
0.12.48 is the newest release of 0.8.x.
In short
1 breaking3 new5 changed
- breaking
But as Gatsby uses React Router heavily, its breaking changes often cause breaking changes within Gatsby.
Security
1 advisory affects 0.8.3; 4.25.7 fixes them
- ModerateGatsby develop server has Local File Inclusion vulnerabilityGHSA-c6f8-8r25-c4gc · 9 Jun 2023Fixed in 4.25.7
Release note
Hi folks,
Finished off a major new release of Gatsby in time for ReactConf :tada:
New features
Support Less/Sass/Postcss out of the box. CSS files are processed using the excellent cssnext.
Support extracting and minifying css on production builds to an external
styles.cssfile.React-Router 2.0 :tada:
Internals work
We're using Webpack Hot Middleware + react-transform-hmr now instead of react-hot-loader.
All remaining Coffeescript files have been converted to JS.
Breaking changes.
React Router has made two major releases since Gatsby was first built with a ton of nice improvements. But as Gatsby uses React Router heavily, its breaking changes often cause breaking changes within Gatsby.
The main change is what props are passed to _template and wrapper components. Previously each component was passed the current page data and a pages array of all pages. Now this information is put onto the route prop passed in by React Router.
Also where previously React Router provided a <RouteHandler/> component which rendered the children components in _template files, you should now replace those with {this.props.children}.
Upgrading
Install new packages:
npm install --save react-router@latest lodash@latest&&npm install --save-dev babel-plugin-react-transform@1.1.1 react-transform-catch-errors react-transform-hmr redbox-reactAdjust templates and wrappers (and other components as necessary) to account for the React Router changes.
onRouteChangeis now passed thelocationobject from History.