Make into Two Words (#13084)

* docs(gatsby-source-shopify): Add note about API permissions (#13037) Note which permissions you should enable on the Shopify Storefront API. Without these permissions you'll get a fairly cryptic error message. * chore(docs): match the Wording Style of Other Tutorial Parts (#13034) * chore(docs): fix typo in convincing others doc (#13033)  ## Description Fixes a misspelled word. * fix(docs): expand guidelist on partnering with gatsby page (#13029) Following up on #12970. Current https://www.gatsbyjs.org/docs/partnering-with-gatsby/: ![image](https://user-images.githubusercontent.com/21834/55404445-2f445080-5558-11e9-84d8-f75db8dd7297.png) * fix(starters): update gatsby monorepo (#12925) This PR contains the following updates: | Package | Type | Update | Change | References | |---|---|---|---|---| | gatsby | dependencies | patch | [`^2.3.3` -> `^2.3.5`](https://diff.intrinsic.com/gatsby/2.3.3/2.3.5) | [source](https://togithub.com/gatsbyjs/gatsby) | | gatsby-image | dependencies | patch | [`^2.0.35` -> `^2.0.37`](https://diff.intrinsic.com/gatsby-image/2.0.35/2.0.37) | [source](https://togithub.com/gatsbyjs/gatsby) | | gatsby-plugin-manifest | dependencies | patch | [`^2.0.25` -> `^2.0.26`](https://diff.intrinsic.com/gatsby-plugin-manifest/2.0.25/2.0.26) | [source](https://togithub.com/gatsbyjs/gatsby) | --- ### Release Notes <details> <summary>gatsbyjs/gatsby</summary> ### [`v2.3.5`](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.5) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.5) ### [`v2.3.4`](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.4) [Compare Source](https://togithub.com/gatsbyjs/gatsby/compare/[email protected]@2.3.4) </details> --- ### Renovate configuration :date: **Schedule**: At any time (no schedule defined). :vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied. :recycle: **Rebasing**: Whenever PR becomes conflicted, or if you modify the PR title to begin with "`rebase!`". :ghost: **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/config-help/issues) if that's undesired. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#gatsbyjs/gatsby). * feat(blog): add gatsby is great blog post (#12777) * chore: add blog post * chore: keep iterating * chore: more tweaks * feat: nearly finish up * chore: run tinypng * chore: fix some typos * chore: fix snippet * chore: add a gif, it gets the people going * chore: more * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * Update docs/blog/2019-03-25-behind-the-scenes-what-makes-gatsby-great/index.md Co-Authored-By: DSchau <[email protected]> * chore: change date * chore: tighten up last section * chore: change data * chore: update per feedback * chore(docs): replace absolute links with relative links (#12949)  ## Description Suggest a more complete structure to the example gatsby-config.js file ## Related Issues Along with #12103 this PR fixes #11957  * chore(showcase): Add Assortment to site showcase (#13002) ## Description Adding [assortment.io](https://assortment.io) to site showcase. Assortment is my Web Development blog that I've recently updated to Gatsby, Netlify, Netlify CMS and Emotion. It'd be cool to see it on the showcase 😃 * feat(gatsby-dev-cli): add verdaccio support (#11525) * feat(gatsby-dev-cli): add verdaccio support [wip] * yuck - don't look * just to verify verdaccio * fix gitignore and add htpasswd with dummy gatsby-dev user * some logging to understand why it tries to handle all the packages * just temporarily so it hopefully at least works * moar data * don't copy all the packages right now * don't rely on package name starting with "gatsby" heuristic * tmp commit * tmp * fs change * tmp * a * updates * remove random files that shouldn't be here * tmp * revert dep changes * ignore changes to package.json created during publishing * testing of dep change in gatsby-cli is picked up by gatsby-dev-cli * let's see if gatsby-dev will handle case of no node_modules * sanity check * adjust console message * add missing devDeps * more missing devDeps * grab package.json from unpkg if package is not yet installed locally * correctly ignore package.json changes during publishing * cleaning things up * htpasswd loc * restore gatsby package.json * adjust ignore files * gatsby-dev-cli: ignore tests * remove extra ln * less console output * turns out you don't need htpasswd after all * use exact when installing local packages - timestamp is used in version * why it failed? * use yarn for publishing - see verdaccio/verdaccio#997 * v0.1.1 * add temporary .npmrc file to allow anonymous publishes * add some jsdocs * update yarn.lock * oops * debug why still can't publish anon * adjust npmrc content * doh * Revert "debug why still can't publish anon" This reverts commit fc1045a. * handle package installation of deps didn't change * skip version changes for packages in gatsby mono-repo, queue copying instead of doing it immediately * fix tests * packages stored in verdaccio storage seems to be picked up by jest and causing trouble, so let's ignore verdaccio storage directory * bye "wat", you will be missed * bail early to avoid conditional bracket hell * more bailing early * more concise * new line * use exaca to simplify running yarn * clean up www/.gitignore * handle not existing packages * remove unused (was needed for basic auth) * cleanup temp file changes when process exit in middle of publishing * ops * Apply suggestions from code review Co-Authored-By: pieh <[email protected]> * cleanup unpkg response handler * move stuff around * remove tmp comment * document traversePackageDocs fn * restrcuture files * add basic tests for traversingPackageDeps * add basic tests for generating packages to publish (based on dep graph) * fix tests on windows * handle circular dependencies when constructing list of packages to publish * remove cat ;( * restore original e2e-test script * update gitignore * chore(release): Publish - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] - [email protected] * chore(release): Publish - [email protected] * docs(gatsby-dev-cli): Edit README (#13049) * Build out Gatsby media information in docs (#12906) * add video info, delete unnecessary stubs Related to #12903 * fix internal link for html5 video section * update videoTitle example Co-Authored-By: marcysutton <[email protected]> * Apply suggestions from code review thanks for the feedback! Co-Authored-By: marcysutton <[email protected]> * incorporate feedback, make into real docs!! * delete unused stubs * Update docs/docs/working-with-video.md Co-Authored-By: marcysutton <[email protected]> * Update docs/docs/working-with-video.md Co-Authored-By: marcysutton <[email protected]> * chore(gatsby): fix domready package to be compatible with ie10 (#13027) * changed domready package to domready-loaded which is compatible with ie10 * updated domready to @mikaelkristiansson/domready * updated packages/gatsby to use @mikaelkristiansson/domready * chore(release): Publish - [email protected] * feat(gatsby-transformer-react-docgen): use local babel config for react-docgen (#12001) * feat: use local babel config for react-docgen BREAKING CHANGE: now uses the local babel config with a fallback * Update README.md * chore(release): Publish - [email protected] * chore(docs): add “Why I used GatsbyJS (#12954) Why I used GatsbyJS  ## Description  ## Related Issues  * feat(www): don't check for overview frontmatter (#13060) Fixes `[[guidelist]]` not being replaced in few pages (i.e. in https://www.gatsbyjs.org/docs/winning-over-stakeholders/ ) The code is handling cases when there are no children (tried building locally and it worked just fine). Follow up to this would be to clear `.md` files that use `overview` and adjust page query. But this is just quick fix. * chore(docs): add starter library to docs sidebar under starters (#12963) 40% of people visiting the starters page go here next, so we should probably add this: ![image](https://user-images.githubusercontent.com/4388699/55285012-58d26180-5337-11e9-9259-68e81b4894ad.png) * chore(showcase): Add gmartinez.dev to showcase (#13067)  ## Description Adding gmartinez.dev to showcase list in site.yml  Co-authored-by: Lennart <[email protected]> * fix(gatsby): don't try to statically analyze gatsby-node, require it and examine exports instead (#13053) * fix: don't try to statically analyze gatsby-node, require it and examine exports instead * differentiate test names * Update packages/gatsby/src/bootstrap/resolve-module-exports.js Co-Authored-By: pieh <[email protected]> * chore(release): Publish - [email protected] * Use Loki's elemMatch operator (#13025) * feat(gatsby): add util.promisify polyfill for older node version (#13024) * refactor(gatsby): gatsby develop: cleanup port detection (#13006) * chore(release): Publish - [email protected] * fix(gatsby): ignore __esModule export in gatsby-node exports (#13081) I introduced bug/regression in #13053 by not removing `__esModule` export name from resolved export names - it break some plugins Fixes: #13079 * chore(release): Publish - [email protected] * fix(www): Hubspot form UI (#13080) * fix(www): Work around HubSpot’s CSS being loaded …by pulling in react-hubspot-form locally, and modifying it slightly. See comment in `www/src/components/react-hubspot-form` for more info. * Fix `formInput` styles … now matching the reference homepage newsletter form — no more Futura PT for input text. * Return nothing because linter * Make into Two Words
gatsbyjs · Apr 3, 2019 · 8969502 · 8969502
1 parent 09d9b4b
commit 8969502
Show file tree

Hide file tree

Showing 63 changed files with 4,537 additions and 296 deletions.
diff --git a/docs/docs/awesome-gatsby.md b/docs/docs/awesome-gatsby.md
@@ -66,6 +66,7 @@ See the [library of official and community plugins](/plugins/)
 - [Zero to Deploy: A Practical Guide to Static Sites with Gatsby.js](https://scotch.io/tutorials/zero-to-deploy-a-practical-guide-to-static-sites-with-gatsbyjs)
 - [Build blazing fast web applications with Gatsby 101](https://gatsbyguides.com/)
 - [Build a Coffee Shop Website w/ Gatsby, Contentful, SnipCard & Formspree](https://www.youtube.com/watch?v=oAVhEPey_qA)
+- [Why I used GatsbyJS](https://medium.com/@jameshunt.co/why-i-used-gatsbyjs-70bbb0f5c4a7)
 
 ### German
 

diff --git a/docs/docs/dropping-images-into-static-folders.md b/docs/docs/dropping-images-into-static-folders.md
diff --git a/docs/docs/images-and-files.md b/docs/docs/images-and-files.md
@@ -1,8 +1,8 @@
 ---
-title: Images and Files
+title: Images, Video, and Files
 overview: true
 ---
 
-Gatsby provides multiple solutions for adding images and files into your projects. This section will walk you through several common patterns for handling images and files in Gatsby projects.
+Gatsby provides multiple solutions for adding images, video, and files into your projects. This section will walk you through several common patterns for handling media in Gatsby projects.
 
 [[guidelist]]
diff --git a/docs/docs/importing-media-content.md b/docs/docs/importing-media-content.md
@@ -1,9 +1,25 @@
 ---
-title: Importing media content
-issue: https://github.com/gatsbyjs/gatsby/issues/8103
+title: Importing Media Content
 ---
 
-This is a stub. Help our community expand it.
+"Media content" is a broad term that generally includes images, videos, documents and files that are displayed on your website. For Gatsby sites, you have multiple options for importing media content depending on the type:
 
-Please use the [Gatsby Style Guide](/contributing/gatsby-style-guide/) to ensure your
-pull request gets accepted.
+## Images, SVG, and PDFs
+
+- [Image graphics can be imported](/docs/adding-images-fonts-files/) with Webpack and queried with GraphQL.
+- Images can also be [included from the `static folder`](/docs/adding-images-fonts-files/#using-the-static-folder).
+- SVG content can be embedded into JSX. Here's a [handy JSX converter](https://transform.now.sh/html-to-jsx/).
+- SVG can be included in `img` tags or CSS backgrounds. [SVG Tips from CSS Tricks](https://css-tricks.com/using-svg/).
+- For PDF files, we recommend embedding an [image of the PDF](https://helpx.adobe.com/acrobat/using/exporting-pdfs-file-formats.html) with [alternative text](https://a11y-101.com/development/infographics), and providing a link to download a [tagged PDF](https://helpx.adobe.com/acrobat/using/creating-accessible-pdfs.html).
+
+## Video assets
+
+Like images, video assets present many options and requirements for cross-browser support. Learn about video embeds on the Gatsby docs page on [working with video](/docs/working-with-video/).
+
+## Canvas and WebGL
+
+The HTML5 `<canvas>` element provides a space for 2-dimensional drawing in a web environment. In Gatsby and React, it may help to include a library like [react-konva](https://github.com/konvajs/react-konva) or one of the comparison libraries to cut down on boilerplate and make drawing easier.
+
+[WebGL](https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API/Tutorial/Getting_started_with_WebGL), on the other hand, creates a 3-dimensional space in a web environment using the `<canvas>` element. Libraries like [Three.js](https://threejs.org/) are often used to enable WebGL experiences in React apps.
+
+> Using canvas and/or WebGL may require modifying your Webpack config. Do you have experience with making this work in your Gatsby site? Contribute to the docs by adding more details to this page.
diff --git a/docs/docs/importing-single-files.md b/docs/docs/importing-single-files.md
diff --git a/docs/docs/working-with-video.md b/docs/docs/working-with-video.md
@@ -0,0 +1,142 @@
+---
+title: Working With Video
+---
+
+- [Sourcing video from a host](#sourcing-video-from-a-host)
+- [Embedding hosted videos in Markdown](#embedding-hosted-videos-in-markdown)
+- [Writing custom components for hosted video](#writing-custom-components-for-hosted-video)
+- [Querying video data from Markdown with GraphQL](#querying-video-data-from-markdown-with-graphql)
+- [Hosting your own HTML5 video files](#hosting-your-own-html5-video-files)
+- [Using custom video players](#using-custom-video-players)
+
+## Sourcing video from a host
+
+The easiest method for including video on a Gatsby site is to source an uploaded file from a site like YouTube, Vimeo, or Twitch. Using the source URL from one of those hosts, you can use Remark plugins or create a custom `<iframe>` solution to embed videos into your Gatsby site.
+
+## Embedding hosted videos in Markdown
+
+There are numerous Gatsby plugins for working with hosted video in your Markdown posts and pages. We recommend checking out the [gatsby-remark-embed-video](/packages/gatsby-remark-embed-video/?=video) plugin for sourcing from a variety of hosts.
+
+### Writing custom components for hosted video
+
+If you would like more control over how YouTube (or similar) videos are embedded into your Gatsby posts and pages, you can write a reusable custom `iframe` component and include it in a JSX template or in your content [with MDX](/docs/mdx/).
+
+In this reusable sample component, you could include props for video data like URL or title, any necessary markup for styling purposes, and the common `iframe` embed code:
+
+```js:title=components/video.js
+const Video = ({ videoSrcURL, videoTitle, ...props }) => (
+  <div className="video">
+    <iframe
+      src={videoSrcURL}
+      title={videoTitle}
+      allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture"
+      frameBorder="0"
+      webkitallowfullscreen="true"
+      mozallowfullscreen="true"
+      allowFullScreen
+    />
+  </div>
+)
+```
+
+You would then include this component in a template or page with a video source URL and title passed in as props. The data for video URLs and titles can be sourced in multiple ways, such as importing JSON or [querying data from Markdown with GraphQL](#querying-data-from-markdown-with-graphql). You can also hard-code video data for something fun, like a custom 404 page with an Easter egg YouTube video:
+
+```jsx:title=src/pages/404.js
+import React from "react"
+
+import Layout from "../components/layout"
+import SEO from "../components/seo"
+import Video from "../components/video"
+
+const NotFoundPage = () => (
+  <Layout>
+    <SEO title="404: Not found" />
+    <section>
+      <h1>NOT FOUND</h1>
+      <p>You just hit a page that doesn't exist... the sadness.</p>
+      <p>May I suggest a video instead?</p>
+      <Video
+        videoSrcURL="https://www.youtube.com/embed/dQw4w9WgXcQ"
+        videoTitle="Official Music Video on YouTube"
+      />
+    </section>
+  </Layout>
+)
+
+export default NotFoundPage
+```
+
+## Querying video data from Markdown with GraphQL
+
+If a Markdown page or post has a featured video, you might want to include a video URL and title in [its frontmatter](/docs/adding-markdown-pages#note-on-creating-markdown-files). That makes it easy to pass those values into our custom component:
+
+```markdown:title=my-first-post.md
+---
+path: "/blog/my-first-post"
+date: "2019-03-27"
+title: "My first blog post"
+videoSourceURL: https://www.youtube.com/embed/dQw4w9WgXcQ
+videoTitle: "Gatsby is Never Gonna Give You Up"
+---
+```
+
+To include a video component in a template, you could start with something like this:
+
+```jsx:title=vlog-template.js
+import React from "react"
+import { graphql } from "gatsby"
+
+import Video from "../components/video"
+
+export default function VlogTemplate({
+  data, // this prop will be injected by the GraphQL query below.
+}) {
+  const { markdownRemark } = data // data.markdownRemark holds our post data
+  const { frontmatter, html } = markdownRemark
+  return (
+    <div className="blog-post-container">
+      <div className="blog-post">
+        <h1>{frontmatter.title}</h1>
+        <h2>{frontmatter.date}</h2>
+        <Video
+          videoSrcURL={frontmatter.videoSrcURL}
+          videoTitle={frontmatter.videoTitle}
+        />
+        <div
+          className="blog-post-content"
+          dangerouslySetInnerHTML={{ __html: html }}
+        />
+      </div>
+    </div>
+  )
+}
+
+export const pageQuery = graphql`
+  query($path: String!) {
+    markdownRemark(frontmatter: { path: { eq: $path } }) {
+      html
+      frontmatter {
+        date(formatString: "MMMM DD, YYYY")
+        path
+        title
+        videoSrcURL
+        videoTitle
+      }
+    }
+  }
+`
+```
+
+## Hosting your own HTML5 video files
+
+It's super common to source video from YouTube, Twitch or Vimeo. But what if you want to host your own video and include it as HTML5 video?
+
+> This discussion is ongoing on GitHub, chime in with your ideas in the Gatsby issue [#3346 Create a special component for HTML5 videos](https://github.com/gatsbyjs/gatsby/issues/3346)
+
+To include your own video files that will work in multiple web browsers and platforms, you'll need to read up a bit on video extensions and codecs. We recommend MDN as a resource: [Media formats for HTML audio and video](https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats). You may need video converter software to produce the necessary formats to support a range of devices and environments, such as `.webm` and `.mp4`.
+
+## Using custom video players
+
+One advantage of integrating a custom component with your own hosted video is it can give you more control over the video player, including its accessibility. It is strongly encouraged to provide captions and subtitles for your videos, and use a player with accessible controls.
+
+Check out the accessible [HTML5 video player from PayPal](https://github.com/paypal/accessible-html5-video-player#react-version) for an example compatible with Gatsby and React.
diff --git a/docs/sites.yml b/docs/sites.yml
@@ -5158,3 +5158,14 @@
   built_by: Luke Whitehouse
   built_by_url: https://twitter.com/_lukewh
   featured: false
+- title: Gerald Martinez Dev
+  main_url: https://gmartinez.dev/
+  url: https://gmartinez.dev/
+  description: >
+    Personal web site for show my skills and my works.
+  categories:
+    - Web Development
+    - Portfolio
+  built_by: Gerald Martinez
+  built_by_url: https://twitter.com/GeraldM_92
+  featured: false
diff --git a/docs/tutorial/part-six/index.md b/docs/tutorial/part-six/index.md
@@ -213,7 +213,7 @@ Try creating a new page containing a blog post and see what happens to the list
 ## What's coming next?
 
 This is great! You've just created a nice index page where you're querying your markdown
-files and producing a list of blogpost titles and excerpts. But you don't want to just see excerpts, you want actual pages for your markdown files.
+files and producing a list of blog post titles and excerpts. But you don't want to just see excerpts, you want actual pages for your markdown files.
 
 You could continue to create pages by placing React components in `src/pages`. However, you'll
 next learn how to _programmatically_ create pages from _data_. Gatsby is _not_

diff --git a/jest.config.js b/jest.config.js
@@ -11,7 +11,12 @@ const builtTestsDirs = pkgs
   .filter(p => fs.existsSync(path.join(p, `src`)))
   .map(p => path.join(p, `__tests__`))
 const distDirs = pkgs.map(p => path.join(p, `dist`))
-const ignoreDirs = [].concat(gatsbyBuildDirs, builtTestsDirs, distDirs)
+const ignoreDirs = [`<rootDir>/packages/gatsby-dev-cli/verdaccio`].concat(
+  gatsbyBuildDirs,
+  builtTestsDirs,
+  distDirs
+)
+
 const coverageDirs = pkgs.map(p => path.join(p, `src/**/*.js`))
 const useCoverage = !!process.env.GENERATE_JEST_REPORT
 

diff --git a/packages/babel-plugin-remove-graphql-queries/CHANGELOG.md b/packages/babel-plugin-remove-graphql-queries/CHANGELOG.md
@@ -3,6 +3,12 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [2.6.3](https://github.com/gatsbyjs/gatsby/compare/babel-plugin-remove-graphql-queries@[email protected]) (2019-04-02)
+
+### Features
+
+- **gatsby-dev-cli:** add verdaccio support ([#11525](https://github.com/gatsbyjs/gatsby/issues/11525)) ([a4f7e77](https://github.com/gatsbyjs/gatsby/commit/a4f7e77))
+
 ## [2.6.2](https://github.com/gatsbyjs/gatsby/compare/babel-plugin-remove-graphql-queries@[email protected]) (2019-03-11)
 
 **Note:** Version bump only for package babel-plugin-remove-graphql-queries

diff --git a/packages/babel-plugin-remove-graphql-queries/package.json b/packages/babel-plugin-remove-graphql-queries/package.json
@@ -1,11 +1,12 @@
 {
   "name": "babel-plugin-remove-graphql-queries",
-  "version": "2.6.2",
+  "version": "2.6.3",
   "author": "Jason Quense <[email protected]>",
   "devDependencies": {
     "@babel/cli": "^7.0.0",
     "@babel/core": "^7.0.0",
-    "babel-preset-gatsby-package": "^0.1.4"
+    "babel-preset-gatsby-package": "^0.1.4",
+    "cross-env": "^5.1.4"
   },
   "license": "MIT",
   "main": "index.js",

diff --git a/packages/babel-preset-gatsby/CHANGELOG.md b/packages/babel-preset-gatsby/CHANGELOG.md
@@ -3,6 +3,12 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [0.1.11](https://github.com/gatsbyjs/gatsby/compare/[email protected]@0.1.11) (2019-04-02)
+
+### Features
+
+- **gatsby-dev-cli:** add verdaccio support ([#11525](https://github.com/gatsbyjs/gatsby/issues/11525)) ([a4f7e77](https://github.com/gatsbyjs/gatsby/commit/a4f7e77))
+
 ## [0.1.10](https://github.com/gatsbyjs/gatsby/compare/[email protected]@0.1.10) (2019-03-23)
 
 ### Bug Fixes

diff --git a/packages/babel-preset-gatsby/package.json b/packages/babel-preset-gatsby/package.json
@@ -1,6 +1,6 @@
 {
   "name": "babel-preset-gatsby",
-  "version": "0.1.10",
+  "version": "0.1.11",
   "author": "Philipp Spiess <[email protected]>",
   "dependencies": {
     "@babel/plugin-proposal-class-properties": "^7.0.0",
@@ -21,6 +21,8 @@
     "watch": "babel -w src --out-dir . --ignore **/__tests__"
   },
   "devDependencies": {
-    "babel-preset-gatsby-package": "^0.1.4"
+    "@babel/cli": "^7.0.0",
+    "babel-preset-gatsby-package": "^0.1.4",
+    "cross-env": "^5.1.4"
   }
 }
diff --git a/packages/gatsby-dev-cli/.gitignore b/packages/gatsby-dev-cli/.gitignore
@@ -28,3 +28,6 @@ node_modules
 
 decls
 dist
+
+# verdaccio local storage
+verdaccio
diff --git a/packages/gatsby-dev-cli/.npmignore b/packages/gatsby-dev-cli/.npmignore
@@ -1,2 +1,3 @@
 src
 flow-typed
+verdaccio
diff --git a/packages/gatsby-dev-cli/CHANGELOG.md b/packages/gatsby-dev-cli/CHANGELOG.md
@@ -3,6 +3,16 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [2.4.14](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-dev-cli/compare/[email protected]@2.4.14) (2019-04-02)
+
+**Note:** Version bump only for package gatsby-dev-cli
+
+## [2.4.13](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-dev-cli/compare/[email protected]@2.4.13) (2019-04-02)
+
+### Features
+
+- **gatsby-dev-cli:** add verdaccio support ([#11525](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-dev-cli/issues/11525)) ([a4f7e77](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-dev-cli/commit/a4f7e77))
+
 ## [2.4.12](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-dev-cli/compare/[email protected]@2.4.12) (2019-03-15)
 
 **Note:** Version bump only for package gatsby-dev-cli

diff --git a/packages/gatsby-dev-cli/README.md b/packages/gatsby-dev-cli/README.md
@@ -55,7 +55,7 @@ https://github.com/gatsbyjs/gatsby/blob/master/scripts/publish-site.sh.
 
 #### `--quiet`
 
-Don't output anything except for a quit message when used together with
+Don't output anything except for a success message when used together with
 `--scan-once`.
 
 #### `--copy-all`

diff --git a/packages/gatsby-dev-cli/package.json b/packages/gatsby-dev-cli/package.json
@@ -1,7 +1,7 @@
 {
   "name": "gatsby-dev-cli",
   "description": "CLI helpers for contributors working on Gatsby",
-  "version": "2.4.12",
+  "version": "2.4.14",
   "author": "Kyle Mathews <[email protected]>",
   "bin": {
     "gatsby-dev": "./dist/index.js"
@@ -13,9 +13,13 @@
     "@babel/runtime": "^7.0.0",
     "chokidar": "^1.7.0",
     "configstore": "^3.1.0",
+    "execa": "^1.0.0",
     "fs-extra": "^4.0.1",
     "is-absolute": "^0.2.6",
     "lodash": "^4.17.10",
+    "request": "2.88.0",
+    "signal-exit": "^3.0.2",
+    "verdaccio": "^3.11.1",
     "yargs": "^8.0.2"
   },
   "devDependencies": {
@@ -32,9 +36,9 @@
   "main": "index.js",
   "repository": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-dev-cli",
   "scripts": {
-    "build": "babel src --out-dir dist",
+    "build": "babel src --out-dir dist --ignore **/__tests__",
     "prepare": "cross-env NODE_ENV=production npm run build",
     "test": "echo \"Error: no test specified\" && exit 1",
-    "watch": "babel -w src --out-dir dist"
+    "watch": "babel -w src --out-dir dist --ignore **/__tests__"
   }
 }
-Original file line number
+Diff line change
@@ Expand Up / @@ -28,3 +28,6 @@ node_modules @@
     decls
     dist
+    # verdaccio local storage
+    verdaccio