[v2] Upgrade Gatsby v2 to webpack 4

docs/blog/2018-02-28-documentation-project/index.md

@@ -12,7 +12,6 @@ People really like Gatsby docs and Gatsby. In fact, we’ve talked about trackin
 
 ![Stupid fast tweet](stupid-fast-tweet.png)
 
-
 ## How much do people like the docs? :D
 
 In my interviews with over 60 Gatsby users, I asked “What do you like about Gatsby?”. Documentation comes out as one of the clear winners, as you can see in this list of the top ten things interviewees like, courtesy of [Unbird.com](https://unbird.com/#/) analytics:
@@ -33,20 +32,20 @@ And some tweets:
 
 ![Usability docs](usability-docs.png)
 
-So here's the bottom line: nearly everyone we’ve interviewed loves the Gatsby development experience and what the community has produced with the docs, guides, and tutorials. 
+So here's the bottom line: nearly everyone we’ve interviewed loves the Gatsby development experience and what the community has produced with the docs, guides, and tutorials.
 
 So why fix what isn’t broken?
 
 ## Enhancing the Tutorials
 
-Many people have contributed to the docs and tutorials already and have done an excellent job. With that being said, there is still room to grow. 
+Many people have contributed to the docs and tutorials already and have done an excellent job. With that being said, there is still room to grow.
 
 Here is a brief overview of issues that have come up again and again as I've interviewed people and observed them going through the tutorials and docs (see [Issue #4175](https://github.com/gatsbyjs/gatsby/issues/4175) on Github to follow this and contribute):
 
 * Gatsby is beginner-friendly; however, _true_ beginners to programming need an intro to basic tools like the command line, code editors, and browser consoles.
 * Upon first visit to Gatsbyjs.org, most visitors click “Get Started.” This is the perfect solution for them if they prefer to jump into coding without reading much. If they prefer step-by-step instructions, it takes some looking around before they see the tutorial tab across the top.
 * Installing new starters for every part of tutorial feels like a distraction to some beginners.
-"Part 1" is not a descriptive title for a tutorial if someone wants to preview or remember what was covered.
+  "Part 1" is not a descriptive title for a tutorial if someone wants to preview or remember what was covered.
 * Almost everyone is new to GraphQL and gets overwhelmed when we introduce it in Part 4.
 
 ## Documentation project beginnings

docs/docs/add-custom-webpack-config.md

@@ -23,10 +23,9 @@ call each build type a "stage". The following stages exist:
    reloading and CSS injection into page
 2. develop-html: same as develop but without react-hmre in the babel config for
    rendering the HTML component.
-3. build-css: production build of CSS
+3. build-javascript: production JavaScript and CSS build. Creates route JS bundles as well
+   as commons chunks for JS and CSS.
 4. build-html: production build static HTML pages
-5. build-javascript: production JavaScript build. Creates route bundles as well
-   as a `commons` and `app bundle`.
 
 Check
 [webpack.config.js](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/utils/webpack.config.js)

examples/using-css-modules/package.json

@@ -4,13 +4,15 @@
   "description": "Gatsby example site demonstrating using css modules in Gatsby with normal (Postcss) css and sass/scss.",
   "author": "Kyle Mathews <[email protected]>",
   "dependencies": {
-    "gatsby": "latest",
-    "gatsby-plugin-sass": "latest"
+    "gatsby": "canary",
+    "gatsby-plugin-sass": "canary",
+    "react": "^16.2.0",
+    "react-dom": "^16.2.0"
   },
   "license": "MIT",
   "main": "n/a",
   "scripts": {
     "develop": "gatsby develop",
     "build": "gatsby build"
   }
-}
+}

examples/using-glamor/gatsby-config.js

@@ -4,12 +4,12 @@ module.exports = {
   },
   plugins: [
     `gatsby-plugin-glamor`,
-    {
-      resolve: `gatsby-plugin-google-analytics`,
-      options: {
-        trackingId: `UA-93349937-2`,
-      },
-    },
+    // {
+    // resolve: `gatsby-plugin-google-analytics`,
+    // options: {
+    // trackingId: `UA-93349937-2`,
+    // },
+    // },
     `gatsby-plugin-offline`,
   ],
 }

examples/using-glamor/package.json

@@ -5,10 +5,10 @@
   "version": "1.0.0",
   "author": "Kyle Mathews <[email protected]>",
   "dependencies": {
-    "gatsby": "next",
-    "gatsby-plugin-glamor": "next",
-    "gatsby-plugin-google-analytics": "next",
-    "gatsby-plugin-offline": "next",
+    "gatsby": "2.0.0-alpha.9fe50b00",
+    "gatsby-plugin-glamor": "canary",
+    "gatsby-plugin-google-analytics": "canary",
+    "gatsby-plugin-offline": "canary",
     "glamor": "^2.20.40",
     "lodash": "^4.16.4",
     "react": "^16.2.0",

examples/using-glamor/src/pages/other-page.js

@@ -1,4 +1,5 @@
 import React from "react"
+import { Link } from "gatsby"
 
 export default () => (
   <div
@@ -12,5 +13,6 @@ export default () => (
   >
     <h1>Weeee...</h1>
     <img src="https://media1.giphy.com/media/urVO9yrQhKwDK/200.webp#1-grid1" />
+    <Link to="/">Back home</Link>
   </div>
 )