gatsbyjs/gatsby
### [`v0.9.1`](https://togithub.com/gatsbyjs/gatsby/releases/v0.9.1)
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.9.0...v0.9.1)
### New tests!
[@benstepp](https://togithub.com/benstepp) [waded into the center of Gatsby and refactored one of the core functions](https://twitter.com/supermoof/status/478322429257715712) AND setup a test framework AND added a number of tests. Awesome! [#232](https://togithub.com/gatsbyjs/gatsby/pull/232)
### Bug fixes
- [@BerkeleyTrue](https://togithub.com/BerkeleyTrue) fixed route => template matching which was broken for some edge cases [#230](https://togithub.com/gatsbyjs/gatsby/pull/230)
- [@BerkeleyTrue](https://togithub.com/BerkeleyTrue) pointed out that errors in `gatsby-node.js` were being swallowed. [@kyleamathews](https://togithub.com/kyleamathews) fixed that in [`859e412`](https://togithub.com/gatsbyjs/gatsby/commit/859e412211364a56ed61da80f43268809d4c9ed9)
- The Autoprefixer plugin was being added to the Postcss multiple times which [@kyleamathews](https://togithub.com/kyleamathews) fixed in [`dd2e960`](https://togithub.com/gatsbyjs/gatsby/commit/dd2e960bc05cbc2e9a708f71bff16b16d91e5b0c)
### Developer Experience (DX) improvements
- [@michaeljdeeb](https://togithub.com/michaeljdeeb) added a check that hard-coded paths in pages have a path prefix. This is a problem that's bit several people as it's easy to miss [#223](https://togithub.com/gatsbyjs/gatsby/pull/223). Invariants are awesome!
- [@alehlopeh](https://togithub.com/alehlopeh) added a new cli command `gatsby serve-build` so you can easily check that your built site is working as expected. [#237](https://togithub.com/gatsbyjs/gatsby/pull/237)
Thanks everyone!
### [`v0.9.0`](https://togithub.com/gatsbyjs/gatsby/releases/v0.9.0)
[Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.8.0...v0.9.0)
Another release with two nice DX improvements.
Also we hit 2500 stars as I was writing this review :tada:
#### Babel 6
Gatsby started its life on Babel 5 but Babel 6 is out and stable so we'll upgrade along with the rest of the ecosystem and take advantage of [its improved performance and awesome new plugin api](https://babeljs.io/blog/2015/10/29/6.0.0).
#### Gatsby must now be installed as a dependency of the site
The global Gatsby install now defers to the local install of Gatsby (and throws if it can't find one). This means you can build a site and not worry about needing to upgrade it again as Gatsby accumulates breaking changes. This also helps ensure Gatsby works in environments where you don't want a global install e.g. build servers.
##### Upgrade instructions
- Install Gatsby — `npm install --save gatsby`
- 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-1` and `npm install --save-dev babel-preset-react-hmre`.
- Uninstall old Babel 5 dependencies (if you added any).
- The `link` function from `gatsby-helpers.js` was renamed to `prefixLink` to clarify its purpose.
- Your `.babelrc` file needs to be upgraded to look like:
{
"presets": ['react', 'es2015', 'stage-1'],
"plugins": ['add-module-exports']
}
- If you modified the default Webpack config in `gatsby.config.js`, this functionality is now moved to `gatsby-node.js` and instead of using module.exports, export your config modification function as `modifyWebpackConfig`. See the [updated instructions in the README](https://togithub.com/gatsbyjs/gatsby#how-to-use-your-own-webpack-loaders).
- 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 truthy `page.data.body`.
- If your site is under version control, you might want to ignore the new auto-written module `.gatsby-context.js`.
- **rare** if you used the `rewritePath`, `onRouteChange` hooks in your app.js — app.js is now not supported. Instead you should export `rewritePath` in `gatsby-node.js` and `onRouteChange` in `gatsby-browser.js`. The function signatures didn't change. These new files will be gaining more functionality in future releases.
That's it! See you in the issue queues :-)
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled due to failing status checks.
:recycle: Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
0.8.0
->0.9.1
2.28.2
->2.29.3
2.7.0
->2.8.0
2.9.0
->2.10.0
1.6.0
->1.7.0
2.7.0
->2.8.0
3.6.0
->3.7.0
2.7.1
->2.11.2
2.8.0
->2.9.0
3.7.1
->3.8.1
4.2.1
->4.3.1
2.7.0
->2.8.1
2.12.0
->2.13.1
2.5.21
->2.9.0
Release Notes
gatsbyjs/gatsby
### [`v0.9.1`](https://togithub.com/gatsbyjs/gatsby/releases/v0.9.1) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.9.0...v0.9.1) ### New tests! [@benstepp](https://togithub.com/benstepp) [waded into the center of Gatsby and refactored one of the core functions](https://twitter.com/supermoof/status/478322429257715712) AND setup a test framework AND added a number of tests. Awesome! [#232](https://togithub.com/gatsbyjs/gatsby/pull/232) ### Bug fixes - [@BerkeleyTrue](https://togithub.com/BerkeleyTrue) fixed route => template matching which was broken for some edge cases [#230](https://togithub.com/gatsbyjs/gatsby/pull/230) - [@BerkeleyTrue](https://togithub.com/BerkeleyTrue) pointed out that errors in `gatsby-node.js` were being swallowed. [@kyleamathews](https://togithub.com/kyleamathews) fixed that in [`859e412`](https://togithub.com/gatsbyjs/gatsby/commit/859e412211364a56ed61da80f43268809d4c9ed9) - The Autoprefixer plugin was being added to the Postcss multiple times which [@kyleamathews](https://togithub.com/kyleamathews) fixed in [`dd2e960`](https://togithub.com/gatsbyjs/gatsby/commit/dd2e960bc05cbc2e9a708f71bff16b16d91e5b0c) ### Developer Experience (DX) improvements - [@michaeljdeeb](https://togithub.com/michaeljdeeb) added a check that hard-coded paths in pages have a path prefix. This is a problem that's bit several people as it's easy to miss [#223](https://togithub.com/gatsbyjs/gatsby/pull/223). Invariants are awesome! - [@alehlopeh](https://togithub.com/alehlopeh) added a new cli command `gatsby serve-build` so you can easily check that your built site is working as expected. [#237](https://togithub.com/gatsbyjs/gatsby/pull/237) Thanks everyone! ### [`v0.9.0`](https://togithub.com/gatsbyjs/gatsby/releases/v0.9.0) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/v0.8.0...v0.9.0) Another release with two nice DX improvements. Also we hit 2500 stars as I was writing this review :tada: #### Babel 6 Gatsby started its life on Babel 5 but Babel 6 is out and stable so we'll upgrade along with the rest of the ecosystem and take advantage of [its improved performance and awesome new plugin api](https://babeljs.io/blog/2015/10/29/6.0.0). #### Gatsby must now be installed as a dependency of the site The global Gatsby install now defers to the local install of Gatsby (and throws if it can't find one). This means you can build a site and not worry about needing to upgrade it again as Gatsby accumulates breaking changes. This also helps ensure Gatsby works in environments where you don't want a global install e.g. build servers. ##### Upgrade instructions - Install Gatsby — `npm install --save gatsby` - 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-1` and `npm install --save-dev babel-preset-react-hmre`. - Uninstall old Babel 5 dependencies (if you added any). - The `link` function from `gatsby-helpers.js` was renamed to `prefixLink` to clarify its purpose. - Your `.babelrc` file needs to be upgraded to look like: { "presets": ['react', 'es2015', 'stage-1'], "plugins": ['add-module-exports'] } - If you modified the default Webpack config in `gatsby.config.js`, this functionality is now moved to `gatsby-node.js` and instead of using module.exports, export your config modification function as `modifyWebpackConfig`. See the [updated instructions in the README](https://togithub.com/gatsbyjs/gatsby#how-to-use-your-own-webpack-loaders). - 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 truthy `page.data.body`. - If your site is under version control, you might want to ignore the new auto-written module `.gatsby-context.js`. - **rare** if you used the `rewritePath`, `onRouteChange` hooks in your app.js — app.js is now not supported. Instead you should export `rewritePath` in `gatsby-node.js` and `onRouteChange` in `gatsby-browser.js`. The function signatures didn't change. These new files will be gaining more functionality in future releases. That's it! See you in the issue queues :-)Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled due to failing status checks.
:recycle: Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.