• @jquense changed the default host on Windows to localhost https://github.com/gatsbyjs/gatsby/commit/6543ece4bc65ef841ebaa15bbf2223659e75b410
• @kyleamathews changed the compilation mode for the html.js file to development. https://github.com/gatsbyjs/gatsby/commit/f9ae585a22bd282a240a2dabb40e33667a269aea

Noted fixer of NPM packages for Windows @NogsMPLS submitted a PR to get Gatsby (hopefully) completely working on Windows! 🎉 🎉 🎉

@gesposito added support to Webpack for requiring fonts https://github.com/gatsbyjs/gatsby/pull/162

@kyleamathews made a few miscallaneous changes

• Replace remaining uses of Underscore with Lodash https://github.com/gatsbyjs/gatsby/commit/486bd298a6a211d38d7e68f5509d4efa27c9073a
• Integrate the scroll-behavior package so clicking between links with react-router is more browser-like https://github.com/gatsbyjs/gatsby/commit/b4122dbb36fac74b1e3e7f814a90ab4cfbb71155
• Add parentTemplateFile to routes for use in theming https://github.com/gatsbyjs/gatsby/commit/86204882ebe7aa6657ab76974b40c194d858e013

Thanks everyone!

Hi folks,
Finished off a major new release of Gatsby in time for ReactConf 🎉

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.css file.
• React-Router 2.0 🎉

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 [email protected] react-transform-catch-errors react-transform-hmr redbox-react
• Adjust templates and wrappers (and other components as necessary) to account for the React Router changes.
• onRouteChange is now passed the location object from History.

• @kyleamathews added an .eslintrc config to keep our code tidy and consistent.
• @fson fixed both some problems with NPM 3 installs as well as made builds throw errors so automated builds will fail properly.
• @ChristopherBiscardi added integration with the debug module to give you insight into what Gatsby is doing.

> DEBUG=gatsby:* gatsby build

@ChristopherBiscardi added a PR to make it simple to override or extend the default Gatsby Webpack configuration. Gatsby tries to anticipate most needs out of the box but many projects will need some customizations to Webpack.

See the PR and new documentation.

Update to React 0.14

The big change for this release was updating React to 0.14. Thanks to @patrykkopycinski for his PR!

We're still on the 0.13 series of React Router as their recent 1.0 release will require internal updates to Gatsby. Follow along at https://github.com/gatsbyjs/gatsby/issues/32 if interested.

gatsby serve now gatsby develop

Serve implied Gatsby was just serving up files. Develop conveys the idea better that you're starting up a full-fledged development server with the intent to start developing.

Can now do webpack requires in your html.jsx

Previously you couldn't do webpack requires in your html component as the development server was requiring the module in node context. But with the help of @petehunt's webpack-require project, you can now require css or anything else you'd like in your html.jsx.

Improved support for prefixing site links e.g. when building for Github Pages.

See the documentation that's been added to the README.

How to upgrade

You'll need to update React in your project to React 0.14 as well as upgrade any React components that relied on older React APIs. Make sure to not install the latest react-router.

Hopefully this will be fixed soon.

Reported by @luandro at https://github.com/gatsbyjs/gatsby/issues/54

Babel bug report at https://github.com/babel/babel/issues/1889

Bug fix

• Previously Gatsby was compiling the production bundle.js with source-maps inlined. @fson noticed this and wrote a PR to fix this which reduced bundle.js size by 3x! https://github.com/gatsbyjs/gatsby/pull/48

Gatsby previously was crashing when trying to copy assets in the post-build step where the asset was not in a directory with a page.

#39

Fixed in https://github.com/gatsbyjs/gatsby/commit/55fee06a11299ae0d761323e35a80e7c49e1aa74

@fson added SVG support to the Webpack config in #34

@gesposito fixed up Gatsby's support for Babel in https://github.com/gatsbyjs/gatsby/pull/31 as well as converting the starter blog to ES6

Thanks!

@phlogisticfugu created a PR to fix #14

Bugs fixed:

• #11 Error: Cannot find module '../lib/utils/init-starter' on second step of tutorial

First somewhat stable public release

Features added:

• Install pre-built starter sites from Github.
• Support adding link prefixes e.g. for Github sites.
• Added two demo/starter sites, a blog and documentation site
• Added two helper functions for auto-prefixing links and for finding the child pages for a template.