Merge branch 'master' into fix/validate/warnonunknown

* master: (24 commits) chore(docs): Release Notes v4.5 (gatsbyjs#34425) chore(docs): Update quick-start guide (gatsbyjs#34445) chore(docs) : Typo fix GatbsyImage -> GatsbyImage (gatsbyjs#34439) perf(gatsby): reuse rootNode & trackedRootNodes caches across instances of graphqlRunner (gatsbyjs#33695) Update media-item-processing.md (gatsbyjs#34434) chore(docs): Update localization doc (gatsbyjs#34429) test(ssr): Fix flakes (gatsbyjs#34443) chore(release): Publish next Revert "docs: Match egghead.io video instructions (gatsbyjs#34315)" (gatsbyjs#34384) fix(gatsby-plugin-manifest): generate icons sequentially (gatsbyjs#34331) Fix misspelling of "precedence" in log message (gatsbyjs#34428) chore(docs): Adjust doc mentions of gatsby-plugin-create-client-paths (gatsbyjs#34424) chore(docs): Update static-folder doc (gatsbyjs#34392) Upgrade to strip-ansi ^6.0.1 (gatsbyjs#34383) chore(gatsby-plugin-create-client-paths): Update client paths plugin readme with migration info (gatsbyjs#34423) chore: Remove deprecated client paths plugin references (gatsbyjs#34422) chore(docs): Old occurrences of gatbyjs.org (gatsbyjs#34402) Update plugins.md to have correct URL for gatsby-plugin-segment-js (gatsbyjs#34397) chore(gatsby): Give option to ignore output from workers and silence validate-engines (gatsbyjs#34416) chore(release): Publish next pre-minor ...
moonmeister · Jan 11, 2022 · eb2a22a · eb2a22a
2 parents 3113e29 + f5c8c20
commit eb2a22a
Show file tree

Hide file tree

Showing 160 changed files with 660 additions and 465 deletions.
diff --git a/deprecated-packages/gatsby-recipes/package.json b/deprecated-packages/gatsby-recipes/package.json
@@ -57,7 +57,7 @@
     "resolve-from": "^5.0.0",
     "semver": "^7.3.5",
     "single-trailing-newline": "^1.0.0",
-    "strip-ansi": "^6.0.0",
+    "strip-ansi": "^6.0.1",
     "style-to-object": "^0.3.0",
     "unified": "^8.4.2",
     "unist-util-remove": "^2.0.0",

diff --git a/docs/contributing/gatsby-style-guide.md b/docs/contributing/gatsby-style-guide.md
@@ -42,8 +42,8 @@ If the content is already somewhere else on the .org site, feel free to copy and
 
 Possible sources of great research materials:
 
-- blogposts (on gatsbyjs.org and other sites)
-- docs (on gatsbyjs.org and other sites)
+- blogposts (on gatsbyjs.com and other sites)
+- docs (on gatsbyjs.com and other sites)
 - video tutorials
 - Discord or Twitter conversations
 - search engine results
@@ -495,7 +495,7 @@ Attributes:
 
 - intermediate to advanced at React
 - frontend developer
-- prefer using a search engine and/or `ctrl + f` to find things on the gatsbyjs.org site
+- prefer using a search engine and/or `ctrl + f` to find things on the gatsbyjs.com site
 
 Looking for:
 

diff --git a/docs/contributing/managing-pull-requests.md b/docs/contributing/managing-pull-requests.md
@@ -73,7 +73,7 @@ For PRs that add a blog post, we ought to check:
 
 ## Automated Checks
 
-Our repository on [GitHub](https://github.com/gatsbyjs/gatsby) has several automated CI checks that are run automatically for all PRs. These include tests, linting and even preview builds for [gatsbyjs.org](https://www.gatsbyjs.com).
+Our repository on [GitHub](https://github.com/gatsbyjs/gatsby) has several automated CI checks that are run automatically for all PRs. These include tests, linting and even preview builds for [gatsbyjs.com](https://www.gatsbyjs.com).
 
 We want all of these checks to pass. While we'll sometimes review a work in progress PR with some failed checks, a PR is only ready to ship when all the tests have passed.
 

diff --git a/docs/contributing/where-to-participate.md b/docs/contributing/where-to-participate.md
@@ -7,7 +7,7 @@ We want contributing to Gatsby to be fun, enjoyable, and educational for anyone
 - Blogging, speaking about, or creating tutorials about one of Gatsby's many features. Mention [@gatsbyjs on Twitter](https://twitter.com/gatsbyjs) and/or email `devrel [at] gatsbyjs [dot] com` so we can give pointers and tips (if you want them 😄) and help you spread the word. Please add your blog posts and videos of talks to our [Awesome Gatsby](/docs/awesome-gatsby-resources/) page.
 - Presenting at meetups and conferences about your Gatsby projects. Your unique challenges and successes in building things with Gatsby can provide great speaking material. We'd love to review your talk abstract/CFP, so get in touch with us if you'd like some help!
 - [Submitting new feature ideas through an RFC](/blog/2018-04-06-introducing-gatsby-rfc-process/)
-- Submitting new documentation; titles in the side navigation on [docs](/docs) which are lighter in color on gatsbyjs.org are stubs and need contributions
+- Submitting new documentation; titles in the side navigation on [docs](/docs) which are lighter in color on gatsbyjs.com are stubs and need contributions
 - Tweeting about things you [#buildwithgatsby](https://twitter.com/search?q=%23buildwithgatsby) (make sure to use the hashtag and/or @ mention us!)
 - Submitting documentation updates, enhancements, designs, or bug fixes
 - Submitting spelling or grammar fixes

diff --git a/docs/docs/conceptual/building-with-components.md b/docs/docs/conceptual/building-with-components.md
@@ -79,7 +79,7 @@ pages are React components but very often these components are just wrappers aro
 `src/templates/post.js` is an example of a page component. It queries GraphQL
 for markdown data and then renders the page using this data.
 
-See [part seven](/docs/tutorial/part-7/) of the tutorial for a detailed
+See [part six](/docs/tutorial/part-6/) of the tutorial for a detailed
 introduction to programmatically creating pages.
 
 Example:

diff --git a/docs/docs/conceptual/image-plugin-architecture.md b/docs/docs/conceptual/image-plugin-architecture.md
@@ -70,7 +70,7 @@ The `GatsbyImage` component supports three types of layout, which define the res
 
 #### Placeholder
 
-`GatbsyImage` supports displaying a placeholder while the main image loads. There are two kinds of placeholder that are currently supported: flat colors and images. The type of placeholder is set via the image data object, and will either be a data URI for the image, or a CSS color value. The image will either be a base64-encoded low resolution raster image (called `BLURRED` when using sharp) or a URI-encoded SVG (called `TRACED_SVG`). The raster image will by default be 20px wide, and the same aspect ratio as the main image. This will be resized to fill the full container, giving a blurred effect. The SVG image is expected to be a single-color, simplified SVG generated using [potrace](http://potrace.sourceforge.net/). While these are the defaults produced by sharp, and also used by many third-party source plugins, we do not enforce this, and it can be any URI. We strongly encourage the use of inline data URIs, as any placeholder that needs to make a network request will defeat much of the purpose of using a placeholder. The actual placeholder element is a regular `<img>` tag, even for SVGs.
+`GatsbyImage` supports displaying a placeholder while the main image loads. There are two kinds of placeholder that are currently supported: flat colors and images. The type of placeholder is set via the image data object, and will either be a data URI for the image, or a CSS color value. The image will either be a base64-encoded low resolution raster image (called `BLURRED` when using sharp) or a URI-encoded SVG (called `TRACED_SVG`). The raster image will by default be 20px wide, and the same aspect ratio as the main image. This will be resized to fill the full container, giving a blurred effect. The SVG image is expected to be a single-color, simplified SVG generated using [potrace](http://potrace.sourceforge.net/). While these are the defaults produced by sharp, and also used by many third-party source plugins, we do not enforce this, and it can be any URI. We strongly encourage the use of inline data URIs, as any placeholder that needs to make a network request will defeat much of the purpose of using a placeholder. The actual placeholder element is a regular `<img>` tag, even for SVGs.
 
 The alternative placeholder is a flat color. This is expected to be calculated from the dominant color of the source image. sharp supports performing this calculation, and some CMSs provide it in the image metadata. This color is applied as a background color to a placeholder `<div>` element.
 

diff --git a/docs/docs/gatsby-internals-terminology.md b/docs/docs/gatsby-internals-terminology.md
@@ -40,8 +40,6 @@ Contains a map of Page [path](#path) -> [Page object](#page-object).
 
 Think of this instead as `client matchPath`. It is ignored when creating pages during the build. But on the frontend, when resolving the page from the path ([find-path.js]()), it is used (via [reach router](https://github.com/reach/router/blob/master/src/lib/utils.js)) to find the matching page. Note that the [pages are sorted](https://github.com/gatsbyjs/gatsby/blob/7d6a0aa47b37f39aafd7c7b1debfe2cc88c5d540/packages/gatsby/src/bootstrap/requires-writer.ts#L154) so that those with matchPaths are at the end, so that explicit paths are matched first.
 
-This is also used by [gatsby-plugin-create-client-paths](/plugins/gatsby-plugin-create-client-paths/?=client). It duplicates pages whose path match some client-only prefix (e.g. `/app/`). The duplicated page has a `matchPath` so that it is resolved first on the frontend.
-
 It is also used by [gatsby-plugin-netlify](/plugins/gatsby-plugin-netlify/?=netlify) when creating `_redirects`.
 
 #### jsonName

diff --git a/docs/docs/how-to/adding-common-features/localization-i18n.md b/docs/docs/how-to/adding-common-features/localization-i18n.md
@@ -57,4 +57,4 @@ This framework also has experimental support for the React suspense API and it s
 
 - [Gatsby i18n articles](https://www.gatsbyjs.com/blog/tags/localization/)
 
-- [W3C's i18n resources](https://w3c.github.io/i18n-drafts/getting-started/contentdev.en#reference)
+- [W3C's i18n resources](https://www.w3.org/International/i18n-drafts/nav/contentdev#reference)
diff --git a/docs/docs/how-to/images-and-media/static-folder.md b/docs/docs/how-to/images-and-media/static-folder.md
@@ -50,7 +50,7 @@ folder is useful as a workaround for a number of less common cases:
   [`manifest.webmanifest`](https://developer.mozilla.org/en-US/docs/Web/Manifest).
 - You have thousands of images and need to dynamically reference their paths.
 - You want to include a small script like
-  [`pace.js`](http://github.hubspot.com/pace/docs/welcome/) outside of the
+  [`pace.js`](https://codebyzach.github.io/pace/) outside of the
   bundled code.
 - Some libraries may be incompatible with webpack and you have no other option but to include it as a `<script>` tag.
 - You need to import JSON file that doesn't have a consistent schema, like [TopoJSON files](https://en.wikipedia.org/wiki/GeoJSON#TopoJSON), which is difficult to handle with GraphQL. Note that importing JSON files directly inside a page, a template, or a component using `import` syntax results in adding that file to the app bundle and increasing the size of all site's pages. Instead, it's better to place your JSON file inside the `static` folder and use the dynamic import syntax (`import('/static/myjson.json')`) within the `componentDidMount` lifecycle or the `useEffect` hook.