Update all dependencies

[skylerwshaw]

The new Gatsby Cloud product uses "Distributed Builds", which requires gatsby@^2.19.5 and gatsby-plugin-sharp@^2.4.0 according to this post.

In addition to the above dependencies, I've updated all others. Though there aren't tests against which we could validate, I've ensured this branch/PR can:

• Generate a new Gatsby site
• Build properly (manual click-through of built site)
• Use all of the yarn scripts: https://github.com/skylerwshaw/gatsby-contentful-starter/blob/a2725f1f392e7b1bdda348363e1e4c5178d40cd0/package.json#L47-L61

Console log of app creation with this branch

```bash $ gatsby new blog.skylershaw.com ./gatsby-contentful-starter info Creating new site from local starter: ./gatsby-contentful-starter Copying local starter to blog.skylershaw.com ... success Created starter directory layout info Installing packages... yarn install v1.21.1 [1/4] 🔍 Resolving packages... success Already up-to-date. $ node ./bin/hello.js Hey there! 👋 Thanks for giving the gatsby-contentful-starter a try. 🎉 To get you going really quickly this project includes a setup step. yarn run setup automates the following steps for you: - creates a config file ./.contentful.json - imports a predefined content model When this is done run: yarn run dev to start a development environment at localhost:8000 or yarn run build to create a production ready static site in ./public For further information check the readme of the project (https://github.com/contentful-userland/gatsby-contentful-starter) ✨ Done in 1.32s. info Your new Gatsby site has been successfully bootstrapped. Start developing it by running: cd blog.skylershaw.com gatsby develop ``` ```bash $ cd blog.skylershaw.com && yarn run setup yarn run v1.21.1 $ node ./bin/setup.js To set up this project you need to provide your Space ID and the belonging API access tokens. You can find all the needed information in your Contentful space under: app.contentful.com -> Space Settings -> API keys The Content Management API Token will be used to import and write data to your space. The Content Delivery API Token will be used to ship published production-ready content in your Gatsby app. The Content Preview API Token will be used to show not published data in your development environment. Ready? Let's do it! 🎉 ? Your Space ID [REDACTED] ? Your Content Management API access token [REDACTED] ? Your Content Delivery API access token [REDACTED] Writing config file... Config file /Users/skylershaw/Developer/blog.skylershaw.com/.env.development written Config file /Users/skylershaw/Developer/blog.skylershaw.com/.env.production written ┌──────────────────────────────────────────────────┐ │ The following entities are going to be imported: │ ├─────────────────────────────────┬────────────────┤ │ Content Types │ 2 │ ├─────────────────────────────────┼────────────────┤ │ Editor Interfaces │ 2 │ ├─────────────────────────────────┼────────────────┤ │ Entries │ 4 │ ├─────────────────────────────────┼────────────────┤ │ Assets │ 4 │ ├─────────────────────────────────┼────────────────┤ │ Locales │ 1 │ ├─────────────────────────────────┼────────────────┤ │ Webhooks │ 0 │ └─────────────────────────────────┴────────────────┘ ✔ Validating content-file ✔ Initialize client (1s) ✔ Checking if destination space already has any content and retrieving it (2s) ✔ Apply transformations to source data (1s) ✔ Push content to destination space ✔ Connecting to space (1s) ✔ Importing Locales (1s) ✔ Importing Content Types (4s) ✔ Publishing Content Types (4s) ✔ Importing Editor Interfaces (3s) ✔ Importing Assets (9s) ✔ Publishing Assets (2s) ✔ Archiving Assets (1s) ✔ Importing Content Entries (4s) ✔ Publishing Content Entries (2s) ✔ Archiving Entries (0s) ✔ Creating Web Hooks (1s) Finished importing all data ┌───────────────────────┐ │ Imported entities │ ├───────────────────┬───┤ │ Locales │ 1 │ ├───────────────────┼───┤ │ Content Types │ 2 │ ├───────────────────┼───┤ │ Editor Interfaces │ 2 │ ├───────────────────┼───┤ │ Assets │ 4 │ ├───────────────────┼───┤ │ Published Assets │ 4 │ ├───────────────────┼───┤ │ Archived Assets │ 0 │ ├───────────────────┼───┤ │ Entries │ 4 │ ├───────────────────┼───┤ │ Published Entries │ 4 │ ├───────────────────┼───┤ │ Archived Entries │ 0 │ ├───────────────────┼───┤ │ Webhooks │ 0 │ └───────────────────┴───┘ The import took a few seconds (26s) No errors or warnings occurred The import was successful. All set! You can now run yarn run dev to see it in action. ✨ Done in 39.78s. ``` ```bash $ yarn run dev yarn run v1.21.1 $ npm run develop npm WARN lifecycle The node binary used for scripts is /var/folders/bv/sng806552j75qcjyz9db8mth0000gn/T/yarn--1582116573203-0.11074682276777303/node but npm is using /Users/skylershaw/.nvm/versions/node/v12.16.1/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with. > gatsby-contentful-starter@1.0.0 develop /Users/skylershaw/Developer/blog.skylershaw.com > gatsby develop success open and validate gatsby-configs - 0.027s success load plugins - 3.625s success onPreInit - 0.006s success initialize cache - 0.021s success copy gatsby files - 0.055s success onPreBootstrap - 0.015s success createSchemaCustomization - 0.007s Starting to fetch data from Contentful Fetching default locale default locale is : en-US contentTypes fetched 2 Updated entries 5 Deleted entries 0 Updated assets 6 Deleted assets 0 Fetch Contentful data: 1553.621ms success source and transform nodes - 1.676s success building schema - 0.355s success createPages - 0.033s success createPagesStatefully - 0.053s success onPreExtractQueries - 0.003s success update schema - 0.034s success extract queries from components - 0.351s success write out requires - 0.037s success write out redirect data - 0.002s success onPostBootstrap - 0.002s ⠀ info bootstrap finished - 9.519 s ⠀ success run queries - 2.226s - 7/7 3.14/s warn WARNING: We noticed you're using the `useBuiltIns` option without declaring a core-js version. Currently, we assume version 2.x when no version is passed. Since this default version will likely change in future versions of Babel, we recommend explicitly setting the core-js version you are using via the `corejs` option. You should also be sure that the version you pass to the `corejs` option matches the version specified in your `package.json`'s `dependencies` section. If it doesn't, you need to run one of the following commands: ⠀ You can now view gatsby-contentful-starter in the browser. ⠀ http://localhost:8000/ ⠀ View GraphiQL, an in-browser IDE, to explore your site's data and schema ⠀ http://localhost:8000/___graphql ⠀ Note that the development build is not optimized. To create a production build, use gatsby build ⠀ success Building development bundle - 3.160s ——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————— 7 pages Success gatsby-contentful-starter ```

[skylerwshaw]

@Putnam14 @cdtinney Able to take a look at this PR? 🙏 😄

[skylerwshaw]

Thanks @cdtinney, I don't have write access to the repo so am unable to merge myself.

[Putnam14]

Approved and merged. Thanks @skylerwshaw!