Merge branch 'master' into fix/showcase-navigation-issue

* master: (76 commits) chore(release): Publish Update relay version once again (gatsbyjs#11767) Update CHANGELOG.md (gatsbyjs#11764) chore(release): Publish Move to @gatsbyjs scoped version of yarn (gatsbyjs#11759) fix(blog): 2019-01-01 json code blocks (gatsbyjs#11750) fix(starters): update dependency gatsby to ^2.1.0 (gatsbyjs#11745) fix(starters): update dependency prop-types to ^15.7.2 (gatsbyjs#11748) feat(showcase): add Incremental.com.au (gatsbyjs#11729) feat(starters): add starter magicsoup.io (gatsbyjs#11670) docs(gatsby): Add documentation for useStaticQuery (gatsbyjs#11741) chore(release): Publish feat(gatsby): add useStaticQuery hook (gatsbyjs#11588) chore(release): Publish chore(docs): reword CSS in JS docs for clarity (gatsbyjs#11439) chore: Upgrade Prettier related packages to the latest (gatsbyjs#11735) fix(core): added event source polyfill in develop to fix IE/edge hmr (gatsbyjs#11582) chore: minify svg husky hook (gatsbyjs#10560) docs: add videos for Gatsby Link + rewrite for flow (gatsbyjs#11700) docs: add egghead lesson to quickstart (gatsbyjs#11699) ...
gurpreet-hanjra · Feb 14, 2019 · 72e6203 · 72e6203
2 parents c83d3f3 + 94a80b7
commit 72e6203
Show file tree

Hide file tree

Showing 255 changed files with 6,263 additions and 4,548 deletions.
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -130,16 +130,17 @@ jobs:
     executor: node
     <<: *test_template
 
-  integration_tests:
+  integration_tests_long_term_caching:
     executor: node
     steps:
-      - checkout
-      - run: ./scripts/assert-changed-files.sh "packages/*|integration-tests/*|.circleci/*"
-      - <<: *restore_cache
-      - <<: *install_node_modules
-      - <<: *persist_cache
-      - <<: *attach_to_bootstrap
-      - run: yarn test:integration
+      - e2e-test:
+          test_path: integration-tests/long-term-caching
+
+  integration_tests_gatsby_pipeline:
+    executor: node
+    steps:
+      - e2e-test:
+          test_path: integration-tests/gatsby-pipeline
 
   e2e_tests_gatsbygram:
     <<: *e2e-executor
@@ -210,8 +211,10 @@ workflows:
           <<: *ignore_docs
           requires:
             - bootstrap
-      - integration_tests:
-          <<: *ignore_docs
+      - integration_tests_long_term_caching:
+          <<: *e2e-test-workflow
+      - integration_tests_gatsby_pipeline:
+          <<: *e2e-test-workflow
       - e2e_tests_gatsbygram:
           <<: *e2e-test-workflow
       - e2e_tests_path-prefix:

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -31,4 +31,4 @@ What happened.
 
 ### Environment
 
-Run `gatsby info --clipboard` in your project directory and paste the output here. Not working? You may need to update your global gatsby-cli - `npm install -g gatsby-cli`
+Run `npx gatsby info --clipboard` in your project directory and paste the output here.
diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md
@@ -27,8 +27,7 @@ about: Usage question or discussion about Gatsby.
 ### Environment (if relevant)
 
 <!--
-  Required. Run `gatsby info --clipboard` in your gatsby project directory and paste its contents here.
-  Not working? You may need to update your global gatsby-cli - `npm install -g gatsby-cli`
+  Required. Run `npx gatsby info --clipboard` in your gatsby project directory and paste its contents here.
 -->
 
 ### File contents (if changed)

diff --git a/README.md b/README.md
@@ -98,11 +98,8 @@ You can get a new Gatsby site up and running on your local dev environment in 5
     Get your Gatsby blog set up in a single command:
 
     ```sh
-    # install the Gatsby CLI globally
-    npm install -g gatsby-cli
-
     # create a new Gatsby site using the default starter
-    gatsby new my-blazing-fast-site
+    npx gatsby new my-blazing-fast-site
     ```
 
 2.  **Start the site in `develop` mode.**

diff --git a/benchmarks/create-pages/package.json b/benchmarks/create-pages/package.json
@@ -8,8 +8,8 @@
     "serve": "gatsby serve"
   },
   "dependencies": {
-    "gatsby": "^2.0.0-beta.76",
-    "react": "^16.3.2",
-    "react-dom": "^16.3.2"
+    "gatsby": "^2.0.118",
+    "react": "^16.8.0",
+    "react-dom": "^16.8.0"
   }
 }
diff --git a/benchmarks/markdown/package.json b/benchmarks/markdown/package.json
@@ -8,10 +8,10 @@
     "serve": "gatsby serve"
   },
   "dependencies": {
-    "gatsby": "^2.0.9",
-    "gatsby-transformer-remark": "^2.1.4",
-    "react": "^16.3.2",
-    "react-dom": "^16.3.2"
+    "gatsby": "^2.0.118",
+    "gatsby-transformer-remark": "^2.2.4",
+    "react": "^16.8.0",
+    "react-dom": "^16.8.0"
   },
   "devDependencies": {
     "faker": "^4.1.0",

diff --git a/benchmarks/query/package.json b/benchmarks/query/package.json
@@ -9,9 +9,9 @@
   },
   "dependencies": {
     "faker": "^4.1.0",
-    "gatsby": "next",
+    "gatsby": "^2.0.118",
     "lodash": "^4.17.11",
-    "react": "^16.3.2",
-    "react-dom": "^16.3.2"
+    "react": "^16.8.0",
+    "react-dom": "^16.8.0"
   }
 }
diff --git a/docs/blog/2017-02-21-1-0-progress-update-where-came-from-where-going/index.md b/docs/blog/2017-02-21-1-0-progress-update-where-came-from-where-going/index.md
@@ -1,6 +1,6 @@
 ---
 title: What's coming in Gatsby 1.0
-date: "2017-02-23"
+date: 2017-02-23
 author: "Kyle Mathews"
 image: "ui-and-code.png"
 draft: true
@@ -270,7 +270,7 @@ Say we had a markdown file that looked like:
 ```markdown
 ---
 title: A sweet post
-date: "2017-02-23"
+date: 2017-02-23
 ---
 
 This is my sweet blog post. **Cool!**

diff --git a/docs/blog/2017-05-31-introduction-to-gatsby/index.md b/docs/blog/2017-05-31-introduction-to-gatsby/index.md
@@ -16,7 +16,7 @@ Having never used an SSG before (although I’ve read about them), and with very
 
 It turns out that getting started with Gatsby is pretty easy. The Gatsby site features a fantastic, step-by-step tutorial that walks you through getting your first site up and running (even down to deploying), and contains a wealth of resources for when you’ve mastered the basics. You don’t need any prior experience with React, although working with Gatsby definitely made me want to learn React to take full advantage of its power.
 
-One thing that prohibits me from publishing side projects is the thought of configuring a whole build setup with Gulp, webpack, etc. just for something small. This is where Gatsby really appeals to me. Gatsby provides an entire out-of-the-box build setup. Yep. Run `gatsby develop` and immediately you can bypass all that configuration and start building cool stuff in the browser (with live reloads). Run `gatsby build` and your production code is optimised (including progressive image loading and code splitting, among many other features) with _absolutely no effort on your part whatsoever_. You could feasibly get a small, performant site built and deployed in just minutes. You can also add a custom webpack config if you need to.
+One thing that prohibits me from publishing side projects is the thought of configuring a whole build setup with Gulp, webpack, etc. just for something small. This is where Gatsby really appeals to me. Gatsby provides an entire out-of-the-box build setup. Yep. Run `npm run develop` and immediately you can bypass all that configuration and start building cool stuff in the browser (with live reloads). Run `npm run build` and your production code is optimised (including progressive image loading and code splitting, among many other features) with _absolutely no effort on your part whatsoever_. You could feasibly get a small, performant site built and deployed in just minutes. You can also add a custom webpack config if you need to.
 
 ### CSS
 

diff --git a/docs/blog/2017-07-19-creating-a-blog-with-gatsby/index.md b/docs/blog/2017-07-19-creating-a-blog-with-gatsby/index.md
@@ -1,6 +1,6 @@
 ---
 title: Creating a Blog with Gatsby
-date: "2017-07-19"
+date: 2017-07-19
 author: "Dustin Schau"
 image: "../images/15009741473_9ced5e3209_o.jpg"
 imageAuthor: Daniel Go
@@ -33,25 +33,22 @@ these new features by creating a static blog. Let's get on it!
 
 ## Getting started
 
-### Installing the CLI
-
-`npm install -g gatsby-cli`
+### Using the CLI
 
 Gatsby ships with a great CLI (command line interface) that contains the
 functionality of scaffolding out a working site, as well as commands to help
 develop the site once created.
 
-`gatsby new personal-blog && cd $_`
+`npx gatsby new personal-blog && cd $_`
 
 This command will create the folder `personal-blog` and then change into that
 directory. A working `gatsby` statically generated application can now be
-developed upon. The Gatsby CLI includes many common development features such as
-`gatsby build` (build a production, statically generated version of the
-project), `gatsby develop` (launch a hot-reload enabled web development server),
+developed upon. The CLI generates common development scripts to help you get started.
+For example you can run `npm run build` (build a production, statically generated version of the project) or `npm run develop` (launch a hot-reload enabled web development server),
 etc.
 
 We can now begin the exciting task of _actually_ developing on the site, and
-creating a functional, modern blog. You'll generally want to use `gatsby develop` to launch the local development server to validate functionality as we
+creating a functional, modern blog. You'll generally want to use `npm run develop` to launch the local development server to validate functionality as we
 progress through the steps.
 
 ## Adding necessary plugins
@@ -229,7 +226,7 @@ The content of this Markdown file will be our blog post, authored in Markdown
 ```markdown:title=src/pages/07-12-2017-getting-started/index.md
 ---
 path: "/hello-world"
-date: "2017-07-12T17:12:33.962Z"
+date: 2017-07-12T17:12:33.962Z
 title: "My First Gatsby Post"
 ---
 

diff --git a/docs/blog/2017-09-13-why-is-gatsby-so-fast/index.md b/docs/blog/2017-09-13-why-is-gatsby-so-fast/index.md
@@ -1,6 +1,6 @@
 ---
 title: Web Performance 101—also, why is Gatsby so fast?
-date: "2017-09-13"
+date: 2017-09-13
 author: "Kyle Mathews"
 image: "reactnext-gatsby-performance.001.png"
 showImageInArticle: false

diff --git a/docs/blog/2017-09-18-gatsby-modern-static-generation/index.md b/docs/blog/2017-09-18-gatsby-modern-static-generation/index.md
@@ -1,6 +1,6 @@
 ---
 title: "Modern static site generation with Gatsby"
-date: "2017-09-18"
+date: 2017-09-18
 image: "code-image.jpg"
 author: "Kostas Bariotis"
 excerpt: "In this post, I will talk about static site generators -- how they have evolved and why I switched from a Ghost powered site to Gatsby.js, a modern static site generator."

diff --git a/docs/blog/2017-09-26-embracing-graphql/index.md b/docs/blog/2017-09-26-embracing-graphql/index.md
@@ -1,6 +1,6 @@
 ---
 title: "Embracing GraphQL — How I migrated React FAQ to Gatsby v1"
-date: "2017-09-26"
+date: 2017-09-26
 image: "toa-heftiba-274947.jpg"
 author: "Tim Arney"
 excerpt: "Moving to Gatsby 1.x and embracing the new GraphQL setup can be daunting but the effort is going to payoff"

diff --git a/docs/blog/2017-10-01-migrating-my-blog-from-hexo-to-gatsby/index.md b/docs/blog/2017-10-01-migrating-my-blog-from-hexo-to-gatsby/index.md
@@ -1,6 +1,6 @@
 ---
 title: "Migrating My Blog From Hexo To Gatsby"
-date: "2017-10-01"
+date: 2017-10-01
 image: "hexo-to-gatsby.png"
 author: "Ian Sinnott"
 excerpt: "How I migrated my blog to Gatsby and how you can do the same."
@@ -82,8 +82,7 @@ are many ways you could do this but I'll go over what I did.
 To get all the Gatsby files you can use the Gatsby CLI.
 
 ```yaml
-npm install -g gatsby-cli   # Install gatsby CLI
-gatsby new temp-gatsby-files # Initialize gatsby in a temp directory
+npx gatsby new temp-gatsby-files # Initialize gatsby in a temp directory
 cp -R temp-gatsby-files/* ./ # Copy all the files into your root directory
 rm -rf temp-gatsby-files     # Remove the temp directory
 ```

diff --git a/docs/blog/2017-10-03-smartive-goes-gatsby/index.md b/docs/blog/2017-10-03-smartive-goes-gatsby/index.md
@@ -1,6 +1,6 @@
 ---
 title: "Why we choose Gatsby over Next.js and Wintersmith"
-date: "2017-10-03"
+date: 2017-10-03
 image: "smartive-loves-gatsby.png"
 author: "Moreno Feltscher"
 excerpt: "At smartive we always saw the potential of static site generators. We recently made the switch to Gatsby.js for our company site. A decision we don’t regret. Here’s why."

diff --git a/docs/blog/2017-10-05-portfolio-site-gatsby-wordpress/index.md b/docs/blog/2017-10-05-portfolio-site-gatsby-wordpress/index.md
@@ -1,6 +1,6 @@
 ---
 title: "Rebuilding my portfolio website with the great GatsbyJS and WordPress"
-date: "2017-10-05"
+date: 2017-10-05
 image: "gatsby-article-cover-image.jpg"
 author: "David James"
 excerpt: "Recreating my WordPress portfolio site using GatsbyJS, React and the WordPress REST API"

diff --git a/docs/blog/2017-10-16-making-website-building-fun/index.md b/docs/blog/2017-10-16-making-website-building-fun/index.md
@@ -91,19 +91,17 @@ larger and larger.
 
 Fred Brooks wrote in his classic book _The Mythical Man-Month_:
 
-<pullquote>
-The programmer, like the poet, works only slightly removed from pure
-thought-stuff. He builds his castles in the air, from air, creating by
-exertion of the imagination. Few media of creation are so flexible, so easy to
-polish and rework, so readily capable of realizing grand conceptual
-structures…
-
-Yet the program construct, unlike the poet's words, is real in the sense that
-it moves and works, producing visible outputs separate from the construct
-itself. […] The magic of myth and legend has come true in our time. One types
-the correct incantation on a keyboard, and a display screen comes to life,
-showing things that never were nor could be.
-</pullquote>
+> The programmer, like the poet, works only slightly removed from pure
+> thought-stuff. He builds his castles in the air, from air, creating by
+> exertion of the imagination. Few media of creation are so flexible, so easy to
+> polish and rework, so readily capable of realizing grand conceptual
+> structures…
+>
+> Yet the program construct, unlike the poet's words, is real in the sense that
+> it moves and works, producing visible outputs separate from the construct
+> itself. […] The magic of myth and legend has come true in our time. One types
+> the correct incantation on a keyboard, and a display screen comes to life,
+> showing things that never were nor could be.
 
 Technology is incredibly fun when we, like the wizard of fantasy, can type an
 incantation on our computer and a new creation comes to life.

diff --git a/...og/2017-10-20-from-wordpress-to-developing-in-react-starting-to-see-it/index.md b/...og/2017-10-20-from-wordpress-to-developing-in-react-starting-to-see-it/index.md
@@ -1,6 +1,6 @@
 ---
 title: From WordPress to Developing in React — Starting to See It
-date: "2017-10-20"
+date: 2017-10-20
 author: "Benjamin Read"
 tags: ["React", "getting-started", "wordpress"]
 ---

diff --git a/...og/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md b/...og/2017-10-29-my-search-for-the-perfect-universal-javaScript-framework/index.md
@@ -1,6 +1,6 @@
 ---
 title: My search for the perfect universal JavaScript framework
-date: "2017-10-29"
+date: 2017-10-29
 author: "Tal Bereznitskey"
 tags: ["react", "ssr", "static"]
 ---

diff --git a/docs/blog/2017-11-08-migrate-from-jekyll-to-gatsby/gatsby.svg b/docs/blog/2017-11-08-migrate-from-jekyll-to-gatsby/gatsby.svg
diff --git a/docs/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/index.md b/docs/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/index.md
@@ -1,6 +1,6 @@
 ---
 title: Gatsby + Contentful + Netlify (and Algolia)
-date: "2017-12-06"
+date: 2017-12-06
 author: "Josh Weaver"
 image: "gatsby-contentful-netlify-algolia.jpg"
 excerpt: "Gatsby has been getting a lot of recognition and adoption lately, and for good reason. It’s so flexible and it works well with nearly everything."
@@ -286,7 +286,7 @@ And back to using it with Gatsby.
 
 After you link your Netlify site to a specific code repository, Netlify’s build
 bots take care of the rest. From that point on, when you push a change to your
-repo, the build bot says, “Hey look! a change! I need to run the `gatsby build`
+repo, the build bot says, “Hey look! a change! I need to run the `npm run build`
 command...”, then it follows the package.json (or yarn file) in the repo and
 downloads the necessary dependencies if they aren’t already cached, and then
 builds out the static site.

diff --git a/docs/blog/2017-12-07-taking-gatsby-for-a-spin/index.md b/docs/blog/2017-12-07-taking-gatsby-for-a-spin/index.md
@@ -1,6 +1,6 @@
 ---
 title: Taking Gatsby for a spin
-date: "2017-12-06"
+date: 2017-12-06
 author: "Arden de Raaij"
 image: "great-gatsby.jpg"
 excerpt: "A static site generator based on React, does that even make sense? GatsbyJS tries to answer this question with a hypermodern, feature-packed, *jamstacked* development tool that you can try out right now!"

diff --git a/docs/blog/2017-12-20-introducing-the-gatsby-ux-research-program/index.md b/docs/blog/2017-12-20-introducing-the-gatsby-ux-research-program/index.md
@@ -1,6 +1,6 @@
 ---
 title: Introducing the Gatsby UX Research Program
-date: "2017-12-20"
+date: 2017-12-20
 author: "Shannon Soper"
 tags: ["ux"]
 ---

diff --git a/...-boston-gov-used-gatsby-to-be-selected-as-an-amazon-hq2-candidate-city/index.md b/...-boston-gov-used-gatsby-to-be-selected-as-an-amazon-hq2-candidate-city/index.md
@@ -1,6 +1,6 @@
 ---
 title: How Boston.gov used Gatsby to be selected as an Amazon HQ2 candidate city
-date: "2018-01-18"
+date: 2018-01-18
 author: "Sam Bhagwat"
 tags: ["case-studies", "component-library", "iteration-speed"]
 ---

diff --git a/docs/blog/2018-01-22-getting-started-gatsby-and-wordpress/index.md b/docs/blog/2018-01-22-getting-started-gatsby-and-wordpress/index.md
@@ -1,6 +1,6 @@
 ---
 title: Getting Started with Gatsby and WordPress
-date: "2018-01-22"
+date: 2018-01-22
 author: "Amberley Romo"
 tags: ["getting-started", "wordpress"]
 ---
@@ -15,7 +15,7 @@ I recently decided to tackle a redo of my blog. I wanted to do something differ
 
 I generated a new site using the [default starter](https://github.com/gatsbyjs/gatsby-starter-default) and read through what it gave me. Assuming you have the [Gatsby CLI](/docs/) installed, run:
 
-`gatsby new gatsby-example-site`
+`npx gatsby new gatsby-example-site`
 
 That gets us a new site directory with a couple (mostly) empty "gatsby"-prefixed files and a src directory with some basic scaffolding. The configuration and lifecycle hooks for Gatsby get put in those "gatsby"-prefixed files, `gatsby-config.js`, `gatsby-node.js` and `gatsby-browser.js`.
 
@@ -132,7 +132,7 @@ If you include the "optional GraphQL query" noted above, the result of that quer
 
 ##Onward
 
-While this isn't a tutorial -- more a guided walkthrough of me familiarizing and stepping through an initial Gatsby setup -- if you're following along with the [demo code](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-wordpress) you're probably close to (or already!) seeing your WordPress data populate your Gatsby dev site if you run `gatsby develop`!
+While this isn't a tutorial -- more a guided walkthrough of me familiarizing and stepping through an initial Gatsby setup -- if you're following along with the [demo code](https://github.com/gatsbyjs/gatsby/tree/master/examples/using-wordpress) you're probably close to (or already!) seeing your WordPress data populate your Gatsby dev site if you run `npm run develop`!
 
 ##Sidenotes
 

diff --git a/docs/blog/2018-02-09-announcing-gatsby-manor-themes-for-gatsbyjs/index.md b/docs/blog/2018-02-09-announcing-gatsby-manor-themes-for-gatsbyjs/index.md
@@ -1,6 +1,6 @@
 ---
 title: Announcing Gatsby Manor, themes for Gatsby 🎉🎊
-date: "2018-02-09"
+date: 2018-02-09
 image: "gatsbymanor.jpg"
 author: "Steven Natera"
 ---

diff --git a/docs/blog/2018-02-16-bright-future-for-the-web/index.md b/docs/blog/2018-02-16-bright-future-for-the-web/index.md
@@ -1,6 +1,6 @@
 ---
 title: Gatsby And The JAMstack - A Bright Future For The Web
-date: "2018-02-16"
+date: 2018-02-16
 image: "bright-future.jpg"
 author: "Ryan Wiemer"
 tags: ["markdown", "JAMstack", "netlify", "contentful"]

diff --git a/docs/blog/2018-04-04-gatsby-contentful-starter-tutorial/index.md b/docs/blog/2018-04-04-gatsby-contentful-starter-tutorial/index.md
@@ -33,7 +33,7 @@ This guide assumes that you have [GatsbyJS installed](/docs/) and, optionally, a
 Start by using this with the Gatsby CLI:
 
 ```bash
-gatsby new contentful-starter https://github.com/contentful-userland/gatsby-contentful-starter
+npx gatsby new contentful-starter https://github.com/contentful-userland/gatsby-contentful-starter
 ```
 
 Alternatively, you can also clone a sample repo from GitHub:
Original file line number	Diff line number	Diff line change
Expand Up		@@ -31,4 +31,4 @@ What happened.

		### Environment

		Run `gatsby info --clipboard` in your project directory and paste the output here. Not working? You may need to update your global gatsby-cli - `npm install -g gatsby-cli`
		Run `npx gatsby info --clipboard` in your project directory and paste the output here.
-Original file line number
+Diff line change
@@ Expand Up @@
     It turns out that getting started with Gatsby is pretty easy. The Gatsby site features a fantastic, step-by-step tutorial that walks you through getting your first site up and running (even down to deploying), and contains a wealth of resources for when you’ve mastered the basics. You don’t need any prior experience with React, although working with Gatsby definitely made me want to learn React to take full advantage of its power.
-    One thing that prohibits me from publishing side projects is the thought of configuring a whole build setup with Gulp, webpack, etc. just for something small. This is where Gatsby really appeals to me. Gatsby provides an entire out-of-the-box build setup. Yep. Run `gatsby develop` and immediately you can bypass all that configuration and start building cool stuff in the browser (with live reloads). Run `gatsby build` and your production code is optimised (including progressive image loading and code splitting, among many other features) with _absolutely no effort on your part whatsoever_. You could feasibly get a small, performant site built and deployed in just minutes. You can also add a custom webpack config if you need to.
+    One thing that prohibits me from publishing side projects is the thought of configuring a whole build setup with Gulp, webpack, etc. just for something small. This is where Gatsby really appeals to me. Gatsby provides an entire out-of-the-box build setup. Yep. Run `npm run develop` and immediately you can bypass all that configuration and start building cool stuff in the browser (with live reloads). Run `npm run build` and your production code is optimised (including progressive image loading and code splitting, among many other features) with _absolutely no effort on your part whatsoever_. You could feasibly get a small, performant site built and deployed in just minutes. You can also add a custom webpack config if you need to.
     ### CSS
@@ Expand Down @@