Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: gatsbyjs/gatsby
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: babel-preset-gatsby@2.22.1
Choose a base ref
...
head repository: gatsbyjs/gatsby
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: babel-preset-gatsby@2.23.0
Choose a head ref

Commits on Aug 25, 2022

  1. chore(release): Publish next pre-minor

     - babel-plugin-remove-graphql-queries@4.23.0-next.0
     - babel-preset-gatsby-package@2.23.0-next.0
     - babel-preset-gatsby@2.23.0-next.0
     - create-gatsby@2.23.0-next.0
     - gatsby-cli@4.23.0-next.0
     - gatsby-codemods@3.23.0-next.0
     - gatsby-core-utils@3.23.0-next.0
     - gatsby-cypress@2.23.0-next.0
     - gatsby-design-tokens@4.23.0-next.0
     - gatsby-dev-cli@4.23.0-next.0
     - gatsby-graphiql-explorer@2.23.0-next.0
     - gatsby-legacy-polyfills@2.23.0-next.0
     - gatsby-link@4.23.0-next.0
     - gatsby-page-utils@2.23.0-next.0
     - gatsby-parcel-config@0.14.0-next.0
     - @gatsbyjs/parcel-namer-relative-to-cwd@1.8.0-next.0
     - gatsby-plugin-benchmark-reporting@2.23.0-next.0
     - gatsby-plugin-canonical-urls@4.23.0-next.0
     - gatsby-plugin-catch-links@4.23.0-next.0
     - gatsby-plugin-coffeescript@4.23.0-next.0
     - gatsby-plugin-cxs@4.23.0-next.0
     - gatsby-plugin-emotion@7.23.0-next.0
     - gatsby-plugin-facebook-analytics@4.23.0-next.0
     - gatsby-plugin-feed@4.23.0-next.0
     - gatsby-plugin-flow@3.23.0-next.0
     - gatsby-plugin-fullstory@4.23.0-next.0
     - gatsby-plugin-gatsby-cloud@4.23.0-next.0
     - gatsby-plugin-google-analytics@4.23.0-next.0
     - gatsby-plugin-google-gtag@4.23.0-next.0
     - gatsby-plugin-google-tagmanager@4.23.0-next.0
     - gatsby-plugin-image@2.23.0-next.0
     - gatsby-plugin-jss@4.23.0-next.0
     - gatsby-plugin-layout@3.23.0-next.0
     - gatsby-plugin-less@6.23.0-next.0
     - gatsby-plugin-lodash@5.23.0-next.0
     - gatsby-plugin-manifest@4.23.0-next.0
     - gatsby-plugin-mdx@4.2.0-next.0
     - gatsby-plugin-netlify-cms@6.23.0-next.0
     - gatsby-plugin-no-sourcemaps@4.23.0-next.0
     - gatsby-plugin-nprogress@4.23.0-next.0
     - gatsby-plugin-offline@5.23.0-next.0
     - gatsby-plugin-page-creator@4.23.0-next.0
     - gatsby-plugin-postcss@5.23.0-next.0
     - gatsby-plugin-preact@6.23.0-next.0
     - gatsby-plugin-preload-fonts@3.23.0-next.0
     - gatsby-plugin-react-css-modules@4.23.0-next.0
     - gatsby-plugin-react-helmet@5.23.0-next.0
     - gatsby-plugin-sass@5.23.0-next.0
     - gatsby-plugin-schema-snapshot@3.23.0-next.0
     - gatsby-plugin-sharp@4.23.0-next.0
     - gatsby-plugin-sitemap@5.23.0-next.0
     - gatsby-plugin-styled-components@5.23.0-next.0
     - gatsby-plugin-styled-jsx@5.23.0-next.0
     - gatsby-plugin-styletron@7.23.0-next.0
     - gatsby-plugin-stylus@4.23.0-next.0
     - gatsby-plugin-subfont@4.23.0-next.0
     - gatsby-plugin-twitter@4.23.0-next.0
     - gatsby-plugin-typescript@4.23.0-next.0
     - gatsby-plugin-typography@4.23.0-next.0
     - gatsby-plugin-utils@3.17.0-next.0
     - gatsby-react-router-scroll@5.23.0-next.0
     - gatsby-remark-autolink-headers@5.23.0-next.0
     - gatsby-remark-code-repls@6.23.0-next.0
     - gatsby-remark-copy-linked-files@5.23.0-next.0
     - gatsby-remark-custom-blocks@4.23.0-next.0
     - gatsby-remark-embed-snippet@7.23.0-next.0
     - gatsby-remark-graphviz@4.23.0-next.0
     - gatsby-remark-images-contentful@5.23.0-next.0
     - gatsby-remark-images@6.23.0-next.0
     - gatsby-remark-katex@6.23.0-next.0
     - gatsby-remark-prismjs@6.23.0-next.0
     - gatsby-remark-responsive-iframe@5.23.0-next.0
     - gatsby-remark-smartypants@5.23.0-next.0
     - gatsby-script@1.8.0-next.0
     - gatsby-sharp@0.17.0-next.0
     - gatsby-source-contentful@7.21.0-next.0
     - gatsby-source-drupal@5.24.0-next.0
     - gatsby-source-faker@4.23.0-next.0
     - gatsby-source-filesystem@4.23.0-next.0
     - gatsby-source-graphql@4.23.0-next.0
     - gatsby-source-hacker-news@4.23.0-next.0
     - gatsby-source-lever@4.23.0-next.0
     - gatsby-source-medium@4.23.0-next.0
     - gatsby-source-mongodb@4.23.0-next.0
     - gatsby-source-npm-package-search@4.23.0-next.0
     - gatsby-source-shopify@7.12.0-next.0
     - gatsby-source-wikipedia@4.23.0-next.0
     - gatsby-source-wordpress@6.23.0-next.0
     - gatsby-telemetry@3.23.0-next.0
     - gatsby-transformer-asciidoc@3.23.0-next.0
     - gatsby-transformer-csv@4.23.0-next.0
     - gatsby-transformer-documentationjs@6.23.0-next.0
     - gatsby-transformer-excel@4.23.0-next.0
     - gatsby-transformer-hjson@4.23.0-next.0
     - gatsby-transformer-javascript-frontmatter@4.23.0-next.0
     - gatsby-transformer-javascript-static-exports@4.23.0-next.0
     - gatsby-transformer-json@4.23.0-next.0
     - gatsby-transformer-pdf@3.23.0-next.0
     - gatsby-transformer-react-docgen@7.23.0-next.0
     - gatsby-transformer-remark@5.23.0-next.0
     - gatsby-transformer-screenshot@4.23.0-next.0
     - gatsby-transformer-sharp@4.23.0-next.0
     - gatsby-transformer-sqip@4.23.0-next.0
     - gatsby-transformer-toml@4.23.0-next.0
     - gatsby-transformer-xml@4.23.0-next.0
     - gatsby-transformer-yaml@4.23.0-next.0
     - gatsby-worker@1.23.0-next.0
     - gatsby@4.23.0-next.0
    imjoshin committed Aug 25, 2022
    Copy the full SHA
    b08336b View commit details
  2. chore(gatsby): Add env log for build and remove incorrect log for fun…

    …ctions (#36462)
    
    Add env log for build and remove incorrect log for functions
    imjoshin authored Aug 25, 2022
    Copy the full SHA
    613729d View commit details
  3. chore(docs): Fix path to components in part 6 (#36463)

    Fix path
    
    The path to the component was incorrect
    IObert authored Aug 25, 2022
    Copy the full SHA
    9647517 View commit details
  4. Copy the full SHA
    1b7d686 View commit details

Commits on Aug 26, 2022

  1. Copy the full SHA
    320efb7 View commit details
  2. fix(gatsby-source-wordpress): match full urls when replacing media it…

    …em links to static (#36447)
    
    * match full urls when replacing media item links to static
    
    * add fallback empty array incase no matches are returned
    
    * fix yoast seo - it stopped installing for some reason
    
    * add full url static file transformation integration test
    
    * add examples for regexs
    TylerBarnes authored Aug 26, 2022
    Copy the full SHA
    dbbda9e View commit details
  3. chore(docs): Fix gatsby-source-filesystem typo (#36471)

    Update README.md
    
    fix `gatsby-source-filesytem` to `gatsby-source-filesystem` @ line 36
    dreibona authored Aug 26, 2022
    Copy the full SHA
    e8d7446 View commit details

Commits on Aug 27, 2022

  1. Copy the full SHA
    434ca56 View commit details

Commits on Aug 29, 2022

  1. fix(gatsby): fix partial hydration constraints (#36468)

    * fix(gatsby): fix partial hydration constraints
    
    * Update flags.ts
    
    * Update flags.ts
    
    * lint
    wardpeet authored Aug 29, 2022
    Copy the full SHA
    58eee35 View commit details
  2. Copy the full SHA
    215ce0e View commit details
  3. fix(deps): update starters and examples (#36483)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    renovate[bot] authored Aug 29, 2022
    Copy the full SHA
    061fb49 View commit details
  4. chore(gatsby-plugin-sharp): upgrade svgo (#36445)

    Co-authored-by: pieh <misiek.piechowiak@gmail.com>
    marvinjude and pieh authored Aug 29, 2022
    Copy the full SHA
    4707fb8 View commit details
  5. chore(docs): migrate cloud docs to .com (#36389)

    * push up site creation & node version docs
    
    * migrate doc for apex and subdomains
    
    * migrate doc for netlify trailing slash
    
    * move webhook/deploy docs to this branch
    
    * migrate doc for outgoing webhooks
    
    * rerun prettier
    
    * format subheaders
    
    * fix casing in docs descriptions
    
    * remove we/lesson refs & netlify doc
    
    * Update docs/docs/how-to/cloud/set-node-version.md
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    
    * Update docs/docs/how-to/cloud/create-site-from-repository.md
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    
    * rework create site from repo doc
    
    * additional adjustments
    
    * match description & file title
    
    * adjust VCS references
    
    * adjust links/bolding
    
    * final adjustments
    
    * Update docs/docs/how-to/cloud/create-site-from-repository.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/reference/cloud/build-and-preview-webhooks.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/how-to/cloud/create-site-from-template.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/how-to/cloud/deploying-to-gatsby-cloud-hosting.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/how-to/cloud/set-node-version.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/reference/cloud/apex-and-subdomains.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    Co-authored-by: “Marcus <“mcolelittle”@gmail.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    4 people authored Aug 29, 2022
    Copy the full SHA
    e421c10 View commit details

Commits on Aug 30, 2022

  1. chore(gatsby, gatsby-transformer-remark, gatsby-plugin-sharp): Cleanu…

    …p v4 compile flag conditions (#36486)
    
    Co-authored-by: Ward Peeters <ward@coding-tech.com>
    marvinjude and wardpeet authored Aug 30, 2022
    Copy the full SHA
    9dcc773 View commit details
  2. fix(gatsby-source-wordpress): match more urls wp on delta (#36474)

    * create a new page with a full file url in a field to be transformed to static
    
    * fix the new failing test
    
    * update snapshots
    
    * media items are cached by source url. update test so cached results aren't retrieved
    
    * Revert "media items are cached by source url. update test so cached results aren't retrieved"
    
    This reverts commit 7e5b52d.
    
    * Revert "Revert "media items are cached by source url. update test so cached results aren't retrieved""
    
    This reverts commit b2b8594.
    TylerBarnes authored Aug 30, 2022
    Copy the full SHA
    5302b7a View commit details
  3. chore(docs): Release Notes for 4.22 (#36464)

    * chore(docs): Release Notes for 4.22
    
    * Update index.md
    
    * Add release notes from git history, open RFCs highlight
    
    * Add contributors
    
    * Update index.md
    
    Co-authored-by: Josh <jcjohnson77@gmail.com>
    Co-authored-by: Dustin Schau <DSchau@users.noreply.github.com>
    3 people authored Aug 30, 2022
    Copy the full SHA
    341bd6d View commit details

Commits on Aug 31, 2022

  1. chore(release): Publish next

     - gatsby-link@4.23.0-next.1
     - gatsby-plugin-image@2.23.0-next.1
     - gatsby-plugin-mdx@4.2.0-next.1
     - gatsby-plugin-sharp@4.23.0-next.1
     - gatsby-script@1.8.0-next.1
     - gatsby-source-graphql@4.23.0-next.1
     - gatsby-source-shopify@7.12.0-next.1
     - gatsby-source-wordpress@6.23.0-next.1
     - gatsby-transformer-remark@5.23.0-next.1
     - gatsby-transformer-sqip@4.23.0-next.1
     - gatsby@4.23.0-next.1
    marvinjude committed Aug 31, 2022
    Copy the full SHA
    232d3b6 View commit details

Commits on Sep 1, 2022

  1. fix(gatsby-dev-cli): adjust setup to 'just work' with npm 8.5 (#36498)

    Co-authored-by: Jude Agboola <marvinjudehk@gmail.com>
    pieh and marvinjude authored Sep 1, 2022
    Copy the full SHA
    3f5e57c View commit details
  2. feat(gatsby): support node: protocol when bundling engines (#36506)

    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    pieh and imjoshin authored Sep 1, 2022
    Copy the full SHA
    d6293e3 View commit details

Commits on Sep 2, 2022

  1. chore(release): Publish next

     - gatsby-dev-cli@4.23.0-next.1
     - gatsby@4.23.0-next.2
    pieh committed Sep 2, 2022
    Copy the full SHA
    30b874b View commit details
  2. Copy the full SHA
    3bc957b View commit details
  3. chore(docs): update url of deleteNode (#36502)

    docs(gatsby): update url of `deleteNode`
    
    Co-authored-by: nnmax <hi.max@foxemail.com>
    nnmax and nnmax authored Sep 2, 2022
    Copy the full SHA
    0d4dfe9 View commit details
  4. fix(deps): update starters and examples - gatsby (#36503)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    renovate[bot] authored Sep 2, 2022
    Copy the full SHA
    59c1f4f View commit details

Commits on Sep 5, 2022

  1. chore(docs): migrate cloud docs to dotcom(1) (#36452)

    * push up site creation & node version docs
    
    * migrate doc for apex and subdomains
    
    * migrate doc for netlify trailing slash
    
    * move webhook/deploy docs to this branch
    
    * migrate doc for outgoing webhooks
    
    * rerun prettier
    
    * migrate doc for platform limits
    
    * format subheaders
    
    * migrate doc for deploying functions on cloud
    
    * fix casing in docs descriptions
    
    * remove we/lesson refs & netlify doc
    
    * Update docs/docs/how-to/cloud/set-node-version.md
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    
    * Update docs/docs/how-to/cloud/create-site-from-repository.md
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    
    * rework create site from repo doc
    
    * additional adjustments
    
    * match description & file title
    
    * adjust VCS references
    
    * adjust links/bolding
    
    * final adjustments
    
    * next batch
    
    * additional docs/fixes
    
    * fix linting issues
    
    * Update docs/docs/reference/cloud/platform-limits.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/reference/cloud/what-is-gatsby-cloud.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/how-to/cloud/managing-workspace-members.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/reference/cloud/build-logs.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/reference/cloud/cms-previews.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/reference/cloud/hosting-and-data-source-integrations.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    * Update docs/docs/reference/cloud/quick-connect.md
    
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    
    Co-authored-by: “Marcus <“mcolelittle”@gmail.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    Co-authored-by: Dustin Schau <DSchau@users.noreply.github.com>
    Co-authored-by: Josh Johnson <jcjohnson77@gmail.com>
    5 people authored Sep 5, 2022
    Copy the full SHA
    bc04e8f View commit details
  2. fix(deps): update dependency react-docgen to ^5.4.3 for gatsby-transf…

    …ormer-react-docgen (#36277)
    
    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    renovate[bot] authored Sep 5, 2022
    Copy the full SHA
    7fe8e51 View commit details

Commits on Sep 6, 2022

  1. fix: ci pipeline (#36544)

    Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
    wardpeet and pieh authored Sep 6, 2022
    Copy the full SHA
    1125e58 View commit details
  2. chore(gatsby): perfect GatsbyConfig.proxy type (#36548)

    Co-authored-by: nnmax <hi.max@foxemail.com>
    nnmax and nnmax authored Sep 6, 2022
    Copy the full SHA
    dc9aa9a View commit details

Commits on Sep 7, 2022

  1. feat(gatsby): split up head & page component loading (#36545)

    * separate chunk for head, remove default
    
    * use partial hydration env in loader
    
    Co-authored-by: Jude Agboola <marvinjudehk@gmail.com>
    wardpeet and marvinjude authored Sep 7, 2022
    Copy the full SHA
    42e241c View commit details
  2. Copy the full SHA
    9c5eacf View commit details
  3. fix(gatsby): pass custom graphql context provided by createResolverCo…

    …ntext to materialization executor (#36552)
    pieh authored Sep 7, 2022
    Copy the full SHA
    8aeae21 View commit details
  4. chore(docs): monorepos support (#36504)

    Co-authored-by: Lennart <lekoarts@gmail.com>
    Khaledgarbaya and LekoArts authored Sep 7, 2022
    Copy the full SHA
    b55e1d5 View commit details
  5. chore(deps): update [dev] minor and patch dependencies for gatsby-sou…

    …rce-shopify (#34363)
    
    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    3 people authored Sep 7, 2022
    Copy the full SHA
    afba8ca View commit details
  6. fix(deps): update dependency eslint-plugin-jsx-a11y to ^6.6.1 (#36039)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    renovate[bot] and LekoArts authored Sep 7, 2022
    Copy the full SHA
    34c8e51 View commit details
  7. chore(deps): update dependency microbundle to ^0.15.1 for gatsby-scri…

    …pt (#36513)
    
    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    renovate[bot] and LekoArts authored Sep 7, 2022
    Copy the full SHA
    80f6616 View commit details
  8. chore(deps): update dependency microbundle to ^0.15.1 for gatsby-link (

    …#36512)
    
    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    renovate[bot] and LekoArts authored Sep 7, 2022
    Copy the full SHA
    0e56ad6 View commit details
  9. chore(deps): update dependency @types/semver to ^7.3.12 (#36510)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    renovate[bot] and LekoArts authored Sep 7, 2022
    Copy the full SHA
    0b6e823 View commit details
  10. chore(deps): update [dev] minor and patch dependencies for gatsby-leg…

    …acy-polyfills (#35547)
    
    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    renovate[bot] and LekoArts authored Sep 7, 2022
    Copy the full SHA
    856b695 View commit details
  11. fix(deps): update dependency eslint-plugin-react-hooks to ^4.6.0 (#36040

    )
    
    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    renovate[bot] and LekoArts authored Sep 7, 2022
    Copy the full SHA
    cc3ef79 View commit details
  12. chore(deps): update dependency autoprefixer to ^10.4.8 for gatsby-plu…

    …gin-sass (#36273)
    
    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    Co-authored-by: Lennart <lekoarts@gmail.com>
    renovate[bot] and LekoArts authored Sep 7, 2022
    Copy the full SHA
    5f6ad91 View commit details
  13. Copy the full SHA
    bac1e7a View commit details
  14. Copy the full SHA
    fab2db2 View commit details
  15. fix(gatsby): Remove default support for non ESM browsers (#36522)

    Co-authored-by: Ward Peeters <ward@coding-tech.com>
    marvinjude and wardpeet authored Sep 7, 2022
    Copy the full SHA
    8b59183 View commit details

Commits on Sep 8, 2022

  1. Copy the full SHA
    a373d80 View commit details
  2. fix(create-gatsby): Missing "plugins" in cmses.json (#36566)

    * initial
    
    * update all
    
    * update stuff :D
    LekoArts authored Sep 8, 2022
    Copy the full SHA
    e79623c View commit details

Commits on Sep 13, 2022

  1. chore(release): Publish

     - babel-plugin-remove-graphql-queries@4.23.0
     - babel-preset-gatsby-package@2.23.0
     - babel-preset-gatsby@2.23.0
     - create-gatsby@2.23.0
     - gatsby-cli@4.23.0
     - gatsby-codemods@3.23.0
     - gatsby-core-utils@3.23.0
     - gatsby-cypress@2.23.0
     - gatsby-design-tokens@4.23.0
     - gatsby-dev-cli@4.23.0
     - gatsby-graphiql-explorer@2.23.0
     - gatsby-legacy-polyfills@2.23.0
     - gatsby-link@4.23.0
     - gatsby-page-utils@2.23.0
     - gatsby-parcel-config@0.14.0
     - @gatsbyjs/parcel-namer-relative-to-cwd@1.8.0
     - gatsby-plugin-benchmark-reporting@2.23.0
     - gatsby-plugin-canonical-urls@4.23.0
     - gatsby-plugin-catch-links@4.23.0
     - gatsby-plugin-coffeescript@4.23.0
     - gatsby-plugin-cxs@4.23.0
     - gatsby-plugin-emotion@7.23.0
     - gatsby-plugin-facebook-analytics@4.23.0
     - gatsby-plugin-feed@4.23.0
     - gatsby-plugin-flow@3.23.0
     - gatsby-plugin-fullstory@4.23.0
     - gatsby-plugin-gatsby-cloud@4.23.0
     - gatsby-plugin-google-analytics@4.23.0
     - gatsby-plugin-google-gtag@4.23.0
     - gatsby-plugin-google-tagmanager@4.23.0
     - gatsby-plugin-image@2.23.0
     - gatsby-plugin-jss@4.23.0
     - gatsby-plugin-layout@3.23.0
     - gatsby-plugin-less@6.23.0
     - gatsby-plugin-lodash@5.23.0
     - gatsby-plugin-manifest@4.23.0
     - gatsby-plugin-mdx@4.2.0
     - gatsby-plugin-netlify-cms@6.23.0
     - gatsby-plugin-no-sourcemaps@4.23.0
     - gatsby-plugin-nprogress@4.23.0
     - gatsby-plugin-offline@5.23.0
     - gatsby-plugin-page-creator@4.23.0
     - gatsby-plugin-postcss@5.23.0
     - gatsby-plugin-preact@6.23.0
     - gatsby-plugin-preload-fonts@3.23.0
     - gatsby-plugin-react-css-modules@4.23.0
     - gatsby-plugin-react-helmet@5.23.0
     - gatsby-plugin-sass@5.23.0
     - gatsby-plugin-schema-snapshot@3.23.0
     - gatsby-plugin-sharp@4.23.0
     - gatsby-plugin-sitemap@5.23.0
     - gatsby-plugin-styled-components@5.23.0
     - gatsby-plugin-styled-jsx@5.23.0
     - gatsby-plugin-styletron@7.23.0
     - gatsby-plugin-stylus@4.23.0
     - gatsby-plugin-subfont@4.23.0
     - gatsby-plugin-twitter@4.23.0
     - gatsby-plugin-typescript@4.23.0
     - gatsby-plugin-typography@4.23.0
     - gatsby-plugin-utils@3.17.0
     - gatsby-react-router-scroll@5.23.0
     - gatsby-remark-autolink-headers@5.23.0
     - gatsby-remark-code-repls@6.23.0
     - gatsby-remark-copy-linked-files@5.23.0
     - gatsby-remark-custom-blocks@4.23.0
     - gatsby-remark-embed-snippet@7.23.0
     - gatsby-remark-graphviz@4.23.0
     - gatsby-remark-images-contentful@5.23.0
     - gatsby-remark-images@6.23.0
     - gatsby-remark-katex@6.23.0
     - gatsby-remark-prismjs@6.23.0
     - gatsby-remark-responsive-iframe@5.23.0
     - gatsby-remark-smartypants@5.23.0
     - gatsby-script@1.8.0
     - gatsby-sharp@0.17.0
     - gatsby-source-contentful@7.21.0
     - gatsby-source-drupal@5.24.0
     - gatsby-source-faker@4.23.0
     - gatsby-source-filesystem@4.23.0
     - gatsby-source-graphql@4.23.0
     - gatsby-source-hacker-news@4.23.0
     - gatsby-source-lever@4.23.0
     - gatsby-source-medium@4.23.0
     - gatsby-source-mongodb@4.23.0
     - gatsby-source-npm-package-search@4.23.0
     - gatsby-source-shopify@7.12.0
     - gatsby-source-wikipedia@4.23.0
     - gatsby-source-wordpress@6.23.0
     - gatsby-telemetry@3.23.0
     - gatsby-transformer-asciidoc@3.23.0
     - gatsby-transformer-csv@4.23.0
     - gatsby-transformer-documentationjs@6.23.0
     - gatsby-transformer-excel@4.23.0
     - gatsby-transformer-hjson@4.23.0
     - gatsby-transformer-javascript-frontmatter@4.23.0
     - gatsby-transformer-javascript-static-exports@4.23.0
     - gatsby-transformer-json@4.23.0
     - gatsby-transformer-pdf@3.23.0
     - gatsby-transformer-react-docgen@7.23.0
     - gatsby-transformer-remark@5.23.0
     - gatsby-transformer-screenshot@4.23.0
     - gatsby-transformer-sharp@4.23.0
     - gatsby-transformer-sqip@4.23.0
     - gatsby-transformer-toml@4.23.0
     - gatsby-transformer-xml@4.23.0
     - gatsby-transformer-yaml@4.23.0
     - gatsby-worker@1.23.0
     - gatsby@4.23.0
    tyhopp committed Sep 13, 2022
    Copy the full SHA
    92543af View commit details
Showing 416 changed files with 7,390 additions and 17,967 deletions.
6 changes: 4 additions & 2 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
@@ -169,7 +169,7 @@ commands:
command: "REACT_VERSION=<< parameters.react_version >> TEST_PATH=<< parameters.test_path >> node ./scripts/upgrade-react"
- run:
name: Install gatsby-dev@next
command: yarn global add gatsby-dev-cli@next
command: yarn global add gatsby-dev-cli@next --ignore-engines
- run:
name: Run tests (using defaults)
command: ./scripts/e2e-test.sh "<< parameters.test_path >>" "<< parameters.test_command >>"
@@ -280,7 +280,9 @@ jobs:
test_path: integration-tests/gatsby-pipeline

integration_tests_gatsby_cli:
executor: node
executor:
name: node
image: "14.16.0"
steps:
- e2e-test:
test_path: integration-tests/gatsby-cli
23 changes: 11 additions & 12 deletions docs/docs/glossary/wpgraphql.md
Original file line number Diff line number Diff line change
@@ -34,31 +34,30 @@ Then you can configure Gatsby to work with your new endpoint.

### Using WPGraphQL with Gatsby

We recommend using the official [gatsby-source-wordpress](/plugins/gatsby-source-wordpress/) plugin, which sources data from the WPGraphQL plugin.

You'll need to do two more things before you can use your WordPress-backed GraphQL server with Gatsby:

1. install the [gatsby-source-graphql](/docs/third-party-graphql/) plugin; and
2. update `gatsby-config.js`.
1. Install the [gatsby-source-wordpress](/plugins/gatsby-source-wordpress/) plugin; and
2. Update `gatsby-config.js`.

Use [npm](/docs/glossary#npm) to install [gatsby-source-graphql](/docs/third-party-graphql/).
Use [npm](/docs/glossary#npm) to install [gatsby-source-wordpress](/plugins/gatsby-source-wordpress/).

```shell
npm install gatsby-source-graphql
npm install gatsby-source-wordpress
```

Then update `gatsby-config.js`. Add the plugin to your Gatsby instance. Specify the URL of the GraphQL endpoint and set other [configuration options](/plugins/gatsby-source-graphql/).
Then update `gatsby-config.js`. Specify the URL of the WPGraphQL endpoint and set other [configuration options](/plugins/gatsby-source-wordpress/).

```javascript
module.exports = {
plugins: [
{
resolve: "gatsby-source-graphql",
resolve: "gatsby-source-wordpress",
options: {
// Remote schema query type. This is an arbitrary name.
typeName: "WPGraphQL",
// Field name under which it will be available. Used in your Gatsby query. This is also an arbitrary name.
fieldName: "wpcontent",
// GraphQL endpoint, relative to your WordPress home URL.
url: "https://example.com/blog/graphql",
url:
process.env.WPGRAPHQL_URL ||
`https://path-to-your-wordpress-instance.com/graphql`,
},
},
],
36 changes: 36 additions & 0 deletions docs/docs/how-to/cloud/create-a-deploy-to-gatsby-cloud-button.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
title: "Create a Deploy to Gatsby Cloud Button"
description: "Learn how to add a deploy button to your Github repository"
---

Gatsby Cloud supports Deploy Buttons which you can use to quickly create new sites from Github repositories.

[![Deploy to Gatsby Cloud](https://www.gatsbyjs.com/deploynow.svg)](https://www.gatsbyjs.com/dashboard/deploynow?url=https://github.com/gatsbyjs/gatsby-starter-blog)

At this time, only public Github repos are supported.

Have a feature request for Deploy Buttons? [Suggest a feature](https://gatsby.canny.io/gatsby-cloud).

### Configure a button

Set the `url` parameter of the link to your public Github repo.

HTML snippet:

```html
<a
href="https://www.gatsbyjs.com/dashboard/deploynow?url=https://github.com/gatsbyjs/gatsby-starter-blog"
target="_blank"
>
<img
src="https://www.gatsbyjs.com/deploynow.svg"
alt="Deploy to Gatsby Cloud"
/>
</a>
```

Markdown:

```markdown
[![Deploy to Gatsby Cloud](https://www.gatsbyjs.com/deploynow.svg)](https://www.gatsbyjs.com/dashboard/deploynow?url=https://github.com/gatsbyjs/gatsby-starter-blog)
```
73 changes: 73 additions & 0 deletions docs/docs/how-to/cloud/create-site-from-repository.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
title: "Create a Site from a Repository"
description: "Learn how to create a Gatsby Cloud site from a repository"
---

## Introduction

Gatsby Cloud allows you to create a site by importing your Gatsby project from a Git repository. This guide provides the steps for importing a repository from your Git provider and building that site on Gatsby Cloud.

## Prerequisites

You can use the [gatsby-starter-blog](https://github.com/gatsbyjs/gatsby-starter-blog) as a starting point. Select **"Use this template"** to create a new repository using the starter as a template.

![Button to create a new repository from a starter](../../images/use-this-template.png)

## Directions

### 1. Select a Git provider

From your Gatsby Cloud dashboard, click **"Add a Site"**.

![Button to add a site from the Gatsby Cloud dashboard](../../images/add-site.png)

In the "Import from a Git repository" section, choose your Git provider and install the Gatsby Cloud app. For the sake of this article you'll use Github, however GitLab and BitBucket are also supported.

![List of Git Providers](../../images/import-from-repo.png)

### 2. Specify repository details

Once connected to your Git provider, find the repository you would like to add to Gatsby Cloud and click **"Import"**. You can then provide the details for your site:

1. The site name (defaults to `<repo name>-<branch name>`).
1. The branch to import from and set as your "Production branch" in Gatsby Cloud (in this case, the `main` branch).
1. The base directory, i.e., the directory containing the Gatsby site (the root directory, `/`, is default).

![Basic site configuration](../../images/basic-configuration.png)

After you enter the site details, click **"Next"**.

### 3. Add optional integrations

Next, you will be prompted to connect an optional content management system (CMS) to your site. This step will vary depending on the CMS provider, so there are [separate tutorials](https://support.gatsbyjs.com/hc/en-us/articles/1500000746742) for each supported CMS. However, for this specific example, you can scroll past this card to continue on.

![No Supported Integrations Found](../../images/no-integrations.png)

### 4. Configure environment variables

Now, you will be asked to [set up environment variables](/docs/reference/cloud/managing-environment-variables) for your site. The "Default" starter does not use any environment variables so you will skip this step as well. Click **"Build Site"** to continue.

![Section to add environment variables to a new Gatbsy Cloud site](../../images/no-environment-variables.png)

### 5. Finish

Once your site is done building, you can view the site in two places:

#### Private build URL

Use the build URL to preview the deployed site. This URL is not indexed and is only accessible via direct link.

![Gatsby Cloud Private Build URL link](../../images/private-build-link.png)

#### Public default domain

Use your Gatsby Hosting provided "default domain" to access the public deployment of your site. Gatsby Hosting is turned on by default and the "default domain" is listed under "Site Settings > Hosting".

![Gatsby Cloud default hosting domain](../../images/default-domain.png)

### Troubleshooting

When creating a site from a Github repository, you'll be asked to authenticate with Github. In instances where you're having trouble authenticating and importing your site:

1. Log out and log back in. If you are still aren't able to import the site, your Github repository is part of a Github organization, and you are not an owner of that organization, then you may not have sufficient permission to install the Gatsby Cloud app to Github.
1. When you try to import your repository to Gatsby Cloud, an email is sent to the owner(s) of that organization to authorize Gatsby Cloud. Once they authorize via the link in that email, then you will be able to import your repository into Gatsby Cloud.
66 changes: 66 additions & 0 deletions docs/docs/how-to/cloud/create-site-from-template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
---
title: "Create a Site from a Template"
description: "Learn how to create a Gatsby Cloud site from a template"
---

## Introduction

This guide covers how to create a Gatsby Cloud site by cloning a Gatsby starter. Note, cloning of starters is only supported for Github. If you use GitLab or BitBucket, you'll have to follow the [Create a Site from a Repository](/docs/how-to/cloud/create-site-from-repository/) guide instead.

## Directions

### 1. Choose your starter template

From your Gatsby Cloud dashboard, click **"Add a Site"**.

![Button to add a site from the Gatsby Cloud dashboard](../../images/add-site.png)

On the right hand side, click on the card labeled "Gatsby Default Starter".

![Clone Gatsby Default Starter](../../images/default-starter.png)

### 2. Configure your repository

The first time you set up a Gatsby Cloud site, you will need to connect your Gatsby account to Github by clicking on the "Github" icon in the "Create a Git repository" card.

![Create a Git Repository](../../images/create-git-repo.png)

Next, a pop up window should appear and prompt you to install the Gatsby Cloud app to your Github personal account. Click **"Install"**.

![Gatsby Cloud app permissions](../../images/install-gatsby-cloud-app.png)

After the Github app is installed, you will return to Gatsby Cloud. Here you can select a different Github organization to host the repository under as well as change the name of the repository that will be created if you prefer. Then click **"Next"** to create the site.

![Configure Git repository settings](../../images/configure-repository.png)

### 3. Connect integrations

Next, you'll be prompted to connect any integrations. Here is where you can connect your Gatsby Cloud site to your CMS instance. For the purposes of this tutorial, you can select **"Skip this step"**.

![List of available integrations](../../images/connect-integrations.png)

### 4. Set-up summary

After the repository is created, you'll be given the option to configure any necessary environment variables. This step allows you to add both build and preview variables to your site.

![Section to add environment variables](../../images/setup-summary.png)

Next, click **"Create Site"** and you will be taken to the main tab of the Site Overview page for your new site.

![Site Overview screen](../../images/site-overview.png)

### 5. Finish

Once your site is done building, you can view the site in two places:

#### Private build URL

Use the build URL to preview the deployed site. This URL is not indexed and is only accessible via direct link.

![Private Build URL Link](../../images/private-build-link.png)

#### Public default domain

Use your Gatsby Hosting provided "default domain" to access the public deployment of your site. Gatsby Hosting is turned on by default and the "default domain" is listed under "Site Settings > Hosting".

![Default Domain URL link](../../images/default-domain-link.png)
68 changes: 68 additions & 0 deletions docs/docs/how-to/cloud/deploying-functions-on-gatsby-cloud.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,68 @@
---
title: "Deploying Functions on Gatsby Cloud"
description: "Learn how to deploy Gatsby Serverless Functions on Gatsby Cloud"
---

## Introduction

The Gatsby framework now supports general access to serverless functions in local development as well as in Gatsby Cloud. These [express](https://expressjs.com/)-style functions allow Gatsby developers to build out secure, scalable APIs alongside their Gatsby projects.

### Prerequisites

Functions are a Gatsby core feature and are not specific to Gatsby Cloud. To learn more about how to implement functions in the Gatsby framework, check out the [Reference guide](/docs/reference/functions/).

### Routing in Gatsby Cloud

Functions that are included in a Gatsby project and deployed on Gatsby cloud are available at any build URL. This includes any preview URLs (`gstb.io` domain) or hosting URLs (`gatsbyjs.io` or your custom domain).

```javascript:title=src/api/hello-world.js
const sample = (req, res) => {
res.status(200).json({"message": "Hello, World!"})
};

export default sample;
```

### Environment variables

Functions will have access to any environment variables that you’ve added to either the production or preview environments in Gatsby Cloud.

![Gatsby Cloud environment variables settings](../../images/env_vars.png)

```javascript:title=src/api/hello-world.js
const sample = (req, res) => {
let key = process.env.SAMPLE_VAR;
//run code that uses key

res.status(200).json({ message: "Hello, World!" });
};

export default sample;
```

### Setting cache headers for functions

Users can set custom headers to control cache settings to ensure that function invocations are appropriately handled when served to [CDN](/docs/glossary/content-delivery-network/) users. Any cache-header setting that users add to their function will be passed through and respected on the CDN:

```javascript:title=src/api/hello-world.js
const sample = (req, res) => {
res.setHeader(`Cache-Control`, `public, max-age=60`);
res.status(200).json({ message: "Hello, World!" });
};

export default sample;
```

### Accessing logs for functions

You can access function logs by viewing the build details for the CMS Preview, Pull Request Build, or Production build. See the [Build Logs](/docs/reference/cloud/build-logs) article for more information on accessing build details.

![Gatsby Cloud Function Invocations Log](../../images/function-invocation-log.png)

### Tracking invocation counts

Like the bandwidth and request tracking in Gatsby Cloud, users can track their invocation count across all their Gatsby sites on any workspace landing page as well as site-specific usage on any site page.

Additionally, users can view function-specific invocation counts in the function logs of the build details for any build that implements that function. See the [Platform Limits](/docs/reference/cloud/platform-limits) article for information on function invocation limits.

![Invocations Count on the Gatsby Cloud dashboard](../../images/function-invocation-count.png)
65 changes: 65 additions & 0 deletions docs/docs/how-to/cloud/deploying-to-firebase.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
---
title: "Deploying to Firebase on Gatsby Cloud"
description: "Learn how to deploy your Gatsby Cloud site to Firebase"
---

## Introduction

Gatsby Cloud is a performant platform for building your Gatsby site. Even better, it integrates with Content Delivery Networks (CDNs) like [Firebase](https://firebase.google.com/) so you can build and deploy your site seamlessly.

## Prerequisites

This guide assumes you already:

- Have a Firebase account.
- Have a Gatsby Cloud site created.

You can use either of the following site creation options if you don't have one already:

- [Create a Site from a Template](/docs/how-to/cloud/create-site-from-template)
- [Create a Site from a Repository](/docs/how-to/cloud/create-site-from-repository)

## Setting up a hosting integration

Once your site is available inside Gatsby Cloud, navigate to the "Site Settings" tab.

Inside "Site Settings," select **"Hosting > Hosting integrations."** Here you'll see Firebase listed among the other available hosting providers.

![Select Firebase from hosting integrations](../../images/firebase-hosting.png)

Click **“Connect”** to the right of the Firebase logo, and you’ll be prompted to login into your Firebase account. If you don’t have one, you can create one now.

Once you’re authenticated with Firebase, you’ll be prompted to authorize Gatsby Cloud to interact with Firebase on your behalf. After you’ve completed this step, you’re ready to configure deployment in Gatsby Cloud.

### Connect with a Firebase project

If you don’t already have one, create a Firebase project in your [Firebase console](https://console.firebase.google.com/).

On the “Firebase Integration” screen choose a Firebase project for deployment from the dropdown. Note that you can enter a Firebase site name for projects with multiple sites.

### Configuration with Firebase

Firebase allows you to configure customized hosting behavior such as redirects, headers, cache settings, and which files to deploy. You can define these behaviors in a `firebase.json` file. See [Deploying to Firebase](/docs/how-to/previews-deploys-hosting/deploying-to-firebase/) for the Gatsby recommended caching settings.

In order for Gatsby Cloud to use these settings for your Firebase hosting, you’ll need to make sure that your `firebase.json` file ends up in your `/public` directory when your build is complete.

One way you can accomplish this is by adding the following code to your `gatsby-node.js` file:

```javascript:title=gatsby-node.js
const fs = require("fs");
exports.onPostBuild = () => {
fs.copyFile(`./firebase.json`, `./public/firebase.json`, (err) => {
if (err) {
throw err;
}
});
};
```

Please see the [Firebase Hosting Configuration](https://firebase.google.com/docs/hosting/full-config) documentation for more deployment customization options.

## Finishing Up

And that’s it! Your site is now set up to build and deploy. Gatsby Cloud will handle everything for you. However, if you want to make a change to your domain, you’ll want to do that directly on the Firebase dashboard.

Note that you can only have one hosting integration. If you choose to configure another provider, that will override your existing Firebase integration.
Loading