gatsby

@0x80 noticed that source maps weren't working in Chrome in development and asked about it. That, combined with a serendipitous tweet by @gaearon, led to #812 where we swapped out using the eval source-maps technique for cheap-module-source-maps.

@donysukardi got us React 16 ready by removing our uses of React.createClass and the built-in proptypes #809

@danperkins fixed a logic bug in our router generation where nested templates weren't being tied to their parent templates correctly #808

@kyleamathews replaced the old default starter with a much simpler one to make it simpler to understand Gatsby when new plus easier to use the starter as a base for building new sites #806

@donysukardi added support for using Yarn over NPM when creating a new Gatsby site using gatsby new #782

@Tom-Bonnike extended our JavaScript frontmatter code to support array values. #784 So now the parsing code can extract values in this form:

@ahonn noticed we were doing a full clone of Gatsby starters when running gatsby new which is wasteful as we just throw away the git repo. So in #730 he fixed that to just do a shallow clone.

@dbismut fixed the default markdown loader to add in a site's prefix/basename to links within markdown. #710

@mtt87 needed to support rendering translations correctly for his site during the static HTML build so added support for SSR APIs through a new gatsby-ssr.js file which can be added to your site similar to gatsby-browser.js and gatsby-node.js. He added a wrapRootComponent API similar to what was recently added to the browser but the method is now available if we need to add additional SSR APIs.

@mjesuele added support for extracting data from JS frontmatter when using template literal strings in additional to normal strings