Updates to webpack config

@KyleAMathews KyleAMathews released this Jan 9, 2017 · 1 commit to master since this release

  • @antoniocapelo noticed that while our README promised you could override plugins like you can override loaders... we hadn't defined core plugins with webpack-configurator (the lib that makes it easy to override Gatsby's webpack config in userspace) and then submitted a PR to fix this! Thanks! #626

  • @jbolda added postcss to the loader stack for Sass/Less so they can take advantage of the prefixing built in to our postcss config. https://github.com/gatsbyjs/gatsby/pull/628/files


Support more markdown extensions

@KyleAMathews KyleAMathews released this Dec 19, 2016 · 13 commits to master since this release

@mkdong becomes our 100th contributor in #612 where he added support for additional markdown extensions (e.g. mdwn).

Thanks Mingkai and our 99 other contributors!

screen shot 2016-12-19 at 2 21 35 pm


JS Frontmatter!

@KyleAMathews KyleAMathews released this Dec 10, 2016 · 27 commits to master since this release

@jbolda fixed the 2nd issue ever filed for Gatsby! Supporting "frontmatter" in javascript files. This should still be considered experimental but you can now export an object from your JS pages and that data will be available in your templates, other pages, etc.

I added a quick example of how this works on the starter blog

Note that this initial release is still fairly limited at the moment. This only works in js/jsx files and you must export your data using commonjs (e.g. exports.data = {}). Also we only parse data layer one level deep so

this works:

exports.data = {
  title: "My sweet title",

this still does not work:

exports.data = {
  title: "My sweet title",
  goingDeeper: {
    word: "to your mother",

PRs welcome to make this work on es6 exports (export const data) as well as for subobjects!


UX improvements and support .yml files

@KyleAMathews KyleAMathews released this Nov 28, 2016 · 45 commits to master since this release

  • We tell people Gatsby sites work w/o Javascript and then people fire up a development server w/o javascript... and see a blank screen. The development server actually does need javascript to power hot-reloading, etc. @nason add a default <noscript /> message for people who've turned off Javascript to tell them what's happening and how to test their site w/ no javascript (gatsby build; gatsby serve-build) #566
  • @vinnymac borrowed a nice recent addition to create-react-app where they're not just telling you that your desired port is taken but also which process is (probably) using it #579 ~
  • @briancappello added support for the .yml file extension (a less common variant file extension for YAML files). #580

Thanks everyone!



@KyleAMathews KyleAMathews released this Nov 18, 2016 · 114 commits to master since this release


  • Did the intitial build of the new gatsbyjs.org! It's in the www subdirectory on the 1.0 branch and is built on each push! That's my kind of integration testing ๐Ÿ˜Ž You can see the early version of the site at https://gatsbyjs.netlify.com/.
  • Added <link preload> for page JS bundles. This speeds up loading scripts slightly by telling the browser to start downloading the scripts when the HTML first starts being parsed instead of when the browser reaches the end. This is especially helpful for large HTML documents on slow mobile networks. PR


  • Use namedmodulesplugin instead of recordsPath for ensuring deterministic builds and long-term cachability. The previous PR adding support for recordsPath proved unpleasant as you had to build locally and commit the outputted records.json which was confusing and annoying. PR
  • Replaced the scripts prop that was passed into the body with a postBodyComponents prop that mirrors the headerComponents prop. This is more flexible as it'll let sites/plugins to do things like pass in analytics snippets, etc. easily.