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: gatsby-plugin-feed@4.8.0
Choose a base ref
...
head repository: gatsbyjs/gatsby
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: gatsby-plugin-feed@4.9.0
Choose a head ref

Commits on Feb 17, 2022

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

     - babel-plugin-remove-graphql-queries@4.9.0-next.0
     - babel-preset-gatsby-package@2.9.0-next.0
     - babel-preset-gatsby@2.9.0-next.0
     - create-gatsby@2.9.0-next.0
     - gatsby-cli@4.9.0-next.0
     - gatsby-codemods@3.9.0-next.0
     - gatsby-core-utils@3.9.0-next.0
     - gatsby-cypress@2.9.0-next.0
     - gatsby-design-tokens@4.9.0-next.0
     - gatsby-dev-cli@4.9.0-next.0
     - gatsby-graphiql-explorer@2.9.0-next.0
     - gatsby-legacy-polyfills@2.9.0-next.0
     - gatsby-link@4.9.0-next.0
     - gatsby-page-utils@2.9.0-next.0
     - gatsby-plugin-benchmark-reporting@2.9.0-next.0
     - gatsby-plugin-canonical-urls@4.9.0-next.0
     - gatsby-plugin-catch-links@4.9.0-next.0
     - gatsby-plugin-coffeescript@4.9.0-next.0
     - gatsby-plugin-create-client-paths@4.9.0-next.0
     - gatsby-plugin-cxs@4.9.0-next.0
     - gatsby-plugin-emotion@7.9.0-next.0
     - gatsby-plugin-facebook-analytics@4.9.0-next.0
     - gatsby-plugin-feed@4.9.0-next.0
     - gatsby-plugin-flow@3.9.0-next.0
     - gatsby-plugin-fullstory@4.9.0-next.0
     - gatsby-plugin-gatsby-cloud@4.9.0-next.0
     - gatsby-plugin-google-analytics@4.9.0-next.0
     - gatsby-plugin-google-gtag@4.9.0-next.0
     - gatsby-plugin-google-tagmanager@4.9.0-next.0
     - gatsby-plugin-graphql-config@1.9.0-next.0
     - gatsby-plugin-image@2.9.0-next.0
     - gatsby-plugin-jss@4.9.0-next.0
     - gatsby-plugin-layout@3.9.0-next.0
     - gatsby-plugin-less@6.9.0-next.0
     - gatsby-plugin-lodash@5.9.0-next.0
     - gatsby-plugin-manifest@4.9.0-next.0
     - gatsby-plugin-mdx@3.9.0-next.0
     - gatsby-plugin-netlify-cms@6.9.0-next.0
     - gatsby-plugin-no-sourcemaps@4.9.0-next.0
     - gatsby-plugin-nprogress@4.9.0-next.0
     - gatsby-plugin-offline@5.9.0-next.0
     - gatsby-plugin-page-creator@4.9.0-next.0
     - gatsby-plugin-postcss@5.9.0-next.0
     - gatsby-plugin-preact@6.9.0-next.0
     - gatsby-plugin-preload-fonts@3.9.0-next.0
     - gatsby-plugin-react-css-modules@4.9.0-next.0
     - gatsby-plugin-react-helmet@5.9.0-next.0
     - gatsby-plugin-remove-trailing-slashes@4.9.0-next.0
     - gatsby-plugin-sass@5.9.0-next.0
     - gatsby-plugin-schema-snapshot@3.9.0-next.0
     - gatsby-plugin-sharp@4.9.0-next.0
     - gatsby-plugin-sitemap@5.9.0-next.0
     - gatsby-plugin-styled-components@5.9.0-next.0
     - gatsby-plugin-styled-jsx@5.9.0-next.0
     - gatsby-plugin-styletron@7.9.0-next.0
     - gatsby-plugin-stylus@4.9.0-next.0
     - gatsby-plugin-subfont@4.9.0-next.0
     - gatsby-plugin-twitter@4.9.0-next.0
     - gatsby-plugin-typescript@4.9.0-next.0
     - gatsby-plugin-typography@4.9.0-next.0
     - gatsby-plugin-utils@3.3.0-next.0
     - gatsby-react-router-scroll@5.9.0-next.0
     - gatsby-remark-autolink-headers@5.9.0-next.0
     - gatsby-remark-code-repls@6.9.0-next.0
     - gatsby-remark-copy-linked-files@5.9.0-next.0
     - gatsby-remark-custom-blocks@4.9.0-next.0
     - gatsby-remark-embed-snippet@7.9.0-next.0
     - gatsby-remark-graphviz@4.9.0-next.0
     - gatsby-remark-images-contentful@5.9.0-next.0
     - gatsby-remark-images@6.9.0-next.0
     - gatsby-remark-katex@6.9.0-next.0
     - gatsby-remark-prismjs@6.9.0-next.0
     - gatsby-remark-responsive-iframe@5.9.0-next.0
     - gatsby-remark-smartypants@5.9.0-next.0
     - gatsby-sharp@0.3.0-next.0
     - gatsby-source-contentful@7.7.0-next.0
     - gatsby-source-drupal@5.9.0-next.0
     - gatsby-source-faker@4.9.0-next.0
     - gatsby-source-filesystem@4.9.0-next.0
     - gatsby-source-graphql@4.9.0-next.0
     - gatsby-source-hacker-news@4.9.0-next.0
     - gatsby-source-lever@4.9.0-next.0
     - gatsby-source-medium@4.9.0-next.0
     - gatsby-source-mongodb@4.9.0-next.0
     - gatsby-source-npm-package-search@4.9.0-next.0
     - gatsby-source-shopify@6.9.0-next.0
     - gatsby-source-wikipedia@4.9.0-next.0
     - gatsby-source-wordpress@6.9.0-next.0
     - gatsby-telemetry@3.9.0-next.0
     - gatsby-transformer-asciidoc@3.9.0-next.0
     - gatsby-transformer-csv@4.9.0-next.0
     - gatsby-transformer-documentationjs@6.9.0-next.0
     - gatsby-transformer-excel@4.9.0-next.0
     - gatsby-transformer-hjson@4.9.0-next.0
     - gatsby-transformer-javascript-frontmatter@4.9.0-next.0
     - gatsby-transformer-javascript-static-exports@4.9.0-next.0
     - gatsby-transformer-json@4.9.0-next.0
     - gatsby-transformer-pdf@3.9.0-next.0
     - gatsby-transformer-react-docgen@7.9.0-next.0
     - gatsby-transformer-remark@5.9.0-next.0
     - gatsby-transformer-screenshot@4.9.0-next.0
     - gatsby-transformer-sharp@4.9.0-next.0
     - gatsby-transformer-sqip@4.9.0-next.0
     - gatsby-transformer-toml@4.9.0-next.0
     - gatsby-transformer-xml@4.9.0-next.0
     - gatsby-transformer-yaml@4.9.0-next.0
     - gatsby-worker@1.9.0-next.0
     - gatsby@4.9.0-next.0
    tyhopp committed Feb 17, 2022
    Copy the full SHA
    2846d70 View commit details

Commits on Feb 18, 2022

  1. feat(docs): new architecture and analytics docs (#34838)

    * new architecture and analytics docs
    
    * Update docs/docs/conceptual/building-architecture.md
    
    Co-authored-by: Kyle Mathews <mathews.kyle@gmail.com>
    
    * rename, edit analytics
    
    * prettier
    
    * fix link
    
    * Update docs/docs/conceptual/building-architecture.md
    
    Co-authored-by: Kyle Mathews <mathews.kyle@gmail.com>
    
    Co-authored-by: Kyle Mathews <mathews.kyle@gmail.com>
    calcsam and KyleAMathews authored Feb 18, 2022
    Copy the full SHA
    a76de9e View commit details
  2. Copy the full SHA
    1f3eee0 View commit details
  3. Copy the full SHA
    6dcf4b0 View commit details
  4. Copy the full SHA
    41a69d3 View commit details
  5. Copy the full SHA
    b16d0f1 View commit details

Commits on Feb 21, 2022

  1. fix(gatsby): Remove double enhanced-resolve dep (#34854)

    * initial
    
    * use 5.8.3 to not have multiple versions
    LekoArts authored Feb 21, 2022
    Copy the full SHA
    2c141b8 View commit details
  2. fix(gatsby-source-contentful): Don't use unique/personal info in (#34860

    )
    
    activity labels
    
    This causes issues with metric gathering on Gatsby Cloud as we treat
    each activity name as a unique thing so prefer to keep the numbers of
    these labels small.
    KyleAMathews authored Feb 21, 2022
    Copy the full SHA
    bf5f841 View commit details
  3. fix(create-gatsby): Add required deps for theme-ui option (#34885)

    * fix(create-gatsby): Add required deps for theme-ui option
    
    * Update styles.json
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    tyhopp and LekoArts authored Feb 21, 2022
    Copy the full SHA
    b2c1092 View commit details
  4. Copy the full SHA
    b4637c0 View commit details
  5. chore(gatsby): Update North Star in README (#34855)

    Co-authored-by: Lennart <lekoarts@gmail.com>
    pragmaticpat and LekoArts authored Feb 21, 2022
    Copy the full SHA
    b8a44a4 View commit details

Commits on Feb 22, 2022

  1. chore(docs): Release notes for 4.8 (#34850)

    * chore(docs): Release notes for 4.8
    
    * Couple misc edits
    
    * smaller edits
    
    * Add thank you contributors
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    tyhopp and LekoArts authored Feb 22, 2022
    Copy the full SHA
    3a9f429 View commit details
  2. chore(docs): Update trailingSlash default wording (#34898)

    Co-authored-by: gatsbybot <mathews.kyle+gatsbybot@gmail.com>
    pragmaticpat and gatsbybot authored Feb 22, 2022
    Copy the full SHA
    ee513cc View commit details
  3. fix(deps): update starters and examples - gatsby (#34901)

    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    renovate[bot] and renovate-bot authored Feb 22, 2022
    Copy the full SHA
    6d8f0bf View commit details
  4. fix(gatsby): Lock yarn version to previous for tests (#34905)

    Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
    imjoshin and pieh authored Feb 22, 2022
    Copy the full SHA
    d4f0cef View commit details
  5. chore(gatsby): Cache date formatting in lmdb cache (#34834)

    Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
    Co-authored-by: gatsbybot <mathews.kyle+gatsbybot@gmail.com>
    3 people authored Feb 22, 2022
    Copy the full SHA
    446f9ff View commit details

Commits on Feb 23, 2022

  1. Copy the full SHA
    b685687 View commit details
  2. chore(docs): Add search details (#34895)

    * Update adding-search.md
    
    * Make links relative
    
    Co-authored-by: Ty Hopp <hopp.ty.c@gmail.com>
    calcsam and tyhopp authored Feb 23, 2022
    Copy the full SHA
    255e438 View commit details
  3. Copy the full SHA
    088f23b View commit details
  4. Copy the full SHA
    7c064ac View commit details
  5. Copy the full SHA
    c708226 View commit details
  6. Copy the full SHA
    09a911e View commit details

Commits on Feb 25, 2022

  1. Update gatsby-config.js (#34924)

    fixed typo in gatsby-config.js
    brherr authored Feb 25, 2022
    Copy the full SHA
    0e67f09 View commit details
  2. fix(gatsby-core-utils): fix urls without extension (#34930)

    * add test
    
    * fix(gatsby-core-utils): fix urls without extension
    wardpeet authored Feb 25, 2022
    Copy the full SHA
    728af63 View commit details
  3. Copy the full SHA
    98c6c25 View commit details

Commits on Feb 28, 2022

  1. Copy the full SHA
    35a6d9c View commit details
  2. Copy the full SHA
    9ce5971 View commit details
  3. chore(docs): Update link to "How to create a Gatsby Starter" (#34937)

    The link was broken. It looks like it was moved from Medium to another platform (dev.to).
    benackles authored Feb 28, 2022
    Copy the full SHA
    cf5f9c3 View commit details
  4. feat(gatsby): Compile Gatsby Config Files AOT (#34776)

    * get simplest gatsby-config.ts working
    
    * make gatsby-node work
    
    * use program.directory for default-site-plugin for browser/ssr
    
    * chore(docs): update TS doc (#34757)
    
    Co-authored-by: LekoArts <lekoarts@gmail.com>
    
    * feat(gatsby-parcel-config): create parcel config package (#34779)
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    
    * refactor(core): Polish ahead of time ts implementation (#34773)
    
    Co-authored-by: LekoArts <lekoarts@gmail.com>
    
    * tmp
    
    * update parcel deps version
    
    * update snapshot
    
    * merge master
    
    * feat(core): TS compilation of local plugin gatsby files (#34827)
    
    Co-authored-by: LekoArts <lekoarts@gmail.com>
    
    * Update scaling-issues.md
    
    * Restore build.js
    
    * Restore develop.js
    
    * Restore repl.js
    
    * set flag to always true
    
    * chore(docs): update main tutorial to incorporate TS Updates to create-gatsby (#34890)
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    
    * chore(gatsby): compile only TS files (#34892)
    
    * use require resolve for defaultConfig
    
    * update doc to add limitations and migration guides
    
    * add structured error logging
    
    * fix cache reslience setup (#34915)
    
    * bump @parcel/source-map in monorepo lock
    
    * adjust tests so cache dirs are cleared only before compilations to workaround EBUSY problems on Windows
    
    * address review comments
    
    * docs: specify gatsby versions supporting particular TS features (#34945)
    
    Co-authored-by: Lennart <lekoarts@gmail.com>
    
    Co-authored-by: Jude Agboola <marvinjudehk@gmail.com>
    Co-authored-by: Ty Hopp <tyhopp@users.noreply.github.com>
    Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
    Co-authored-by: gatsbybot <mathews.kyle+gatsbybot@gmail.com>
    5 people authored Feb 28, 2022
    Copy the full SHA
    04d1d37 View commit details
  5. chore(release): Publish next

     - babel-plugin-remove-graphql-queries@4.9.0-next.1
     - babel-preset-gatsby@2.9.0-next.1
     - create-gatsby@2.9.0-next.1
     - gatsby-cli@4.9.0-next.1
     - gatsby-core-utils@3.9.0-next.1
     - gatsby-link@4.9.0-next.1
     - gatsby-page-utils@2.9.0-next.1
     - gatsby-parcel-config@0.0.1-next.1
     - gatsby-plugin-benchmark-reporting@2.9.0-next.1
     - gatsby-plugin-gatsby-cloud@4.9.0-next.1
     - gatsby-plugin-image@2.9.0-next.1
     - gatsby-plugin-manifest@4.9.0-next.1
     - gatsby-plugin-mdx@3.9.0-next.1
     - gatsby-plugin-offline@5.9.0-next.1
     - gatsby-plugin-page-creator@4.9.0-next.1
     - gatsby-plugin-preload-fonts@3.9.0-next.1
     - gatsby-plugin-sharp@4.9.0-next.1
     - gatsby-plugin-typescript@4.9.0-next.1
     - gatsby-remark-images@6.9.0-next.1
     - gatsby-source-contentful@7.7.0-next.1
     - gatsby-source-drupal@5.9.0-next.1
     - gatsby-source-filesystem@4.9.0-next.1
     - gatsby-source-graphql@4.9.0-next.1
     - gatsby-source-shopify@6.9.0-next.1
     - gatsby-source-wordpress@6.9.0-next.1
     - gatsby-telemetry@3.9.0-next.1
     - gatsby-transformer-remark@5.9.0-next.1
     - gatsby-transformer-sqip@4.9.0-next.1
     - gatsby@4.9.0-next.1
    LekoArts committed Feb 28, 2022
    Copy the full SHA
    79e3804 View commit details
  6. Copy the full SHA
    ce4cd26 View commit details

Commits on Mar 1, 2022

  1. initial (#34946)

    LekoArts authored Mar 1, 2022
    Copy the full SHA
    5f552d4 View commit details
  2. fix(gatsby-core-utils): fix caching when using remote-file (#34951)

    * fix(gatsby-core-utils): fix caching when using remote-file
    
    * Fix incorrect var name so bootstrap succeeds
    
    Co-authored-by: Ty Hopp <hopp.ty.c@gmail.com>
    wardpeet and tyhopp authored Mar 1, 2022
    Copy the full SHA
    98f2dfc View commit details
  3. chore(docs): Update Contributing section, RFC process, Governance Mod…

    …el (#34900)
    
    Co-authored-by: Ty Hopp <tyhopp@users.noreply.github.com>
    LekoArts and tyhopp authored Mar 1, 2022
    1
    Copy the full SHA
    4cb514f View commit details
  4. Copy the full SHA
    74df2f5 View commit details
  5. chore(deps): update dependency @testing-library/jest-dom to ^5.16.2 (#…

    …34956)
    
    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    renovate[bot] and renovate-bot authored Mar 1, 2022
    Copy the full SHA
    d30979d View commit details
  6. chore(deps): update dependency nock to ^13.2.4 for gatsby-source-cont…

    …entful (#34958)
    
    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    renovate[bot] and renovate-bot authored Mar 1, 2022
    Copy the full SHA
    f65c076 View commit details
  7. chore(deps): update dependency json2csv to ^5.0.7 for gatsby-transfor…

    …mer-csv (#34957)
    
    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    renovate[bot] and renovate-bot authored Mar 1, 2022
    Copy the full SHA
    574e04b View commit details
  8. fix(deps): update dependency eslint-plugin-react to ^7.29.2 (#34988)

    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    renovate[bot] and renovate-bot authored Mar 1, 2022
    Copy the full SHA
    78779ff View commit details
  9. chore(deps): update formatting & linting (#34985)

    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    renovate[bot] and renovate-bot authored Mar 1, 2022
    Copy the full SHA
    189fc8e View commit details
  10. fix(deps): update dependency urijs to ^1.19.8 for gatsby-remark-code-…

    …repls (#34979)
    
    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    renovate[bot] and renovate-bot authored Mar 1, 2022
    Copy the full SHA
    77c32b0 View commit details
  11. Copy the full SHA
    da2a1ba View commit details
  12. fix(deps): update starters and examples - gatsby (#34934)

    Co-authored-by: Renovate Bot <bot@renovateapp.com>
    renovate[bot] and renovate-bot authored Mar 1, 2022
    Copy the full SHA
    2cf474b View commit details
  13. Copy the full SHA
    f2bce35 View commit details
  14. chore: Lock file

    LekoArts committed Mar 1, 2022
    Copy the full SHA
    0d93383 View commit details
  15. chore(release): Publish

     - babel-plugin-remove-graphql-queries@4.9.0
     - babel-preset-gatsby-package@2.9.0
     - babel-preset-gatsby@2.9.0
     - create-gatsby@2.9.0
     - gatsby-cli@4.9.0
     - gatsby-codemods@3.9.0
     - gatsby-core-utils@3.9.0
     - gatsby-cypress@2.9.0
     - gatsby-design-tokens@4.9.0
     - gatsby-dev-cli@4.9.0
     - gatsby-graphiql-explorer@2.9.0
     - gatsby-legacy-polyfills@2.9.0
     - gatsby-link@4.9.0
     - gatsby-page-utils@2.9.0
     - gatsby-parcel-config@0.0.1
     - gatsby-plugin-benchmark-reporting@2.9.0
     - gatsby-plugin-canonical-urls@4.9.0
     - gatsby-plugin-catch-links@4.9.0
     - gatsby-plugin-coffeescript@4.9.0
     - gatsby-plugin-create-client-paths@4.9.0
     - gatsby-plugin-cxs@4.9.0
     - gatsby-plugin-emotion@7.9.0
     - gatsby-plugin-facebook-analytics@4.9.0
     - gatsby-plugin-feed@4.9.0
     - gatsby-plugin-flow@3.9.0
     - gatsby-plugin-fullstory@4.9.0
     - gatsby-plugin-gatsby-cloud@4.9.0
     - gatsby-plugin-google-analytics@4.9.0
     - gatsby-plugin-google-gtag@4.9.0
     - gatsby-plugin-google-tagmanager@4.9.0
     - gatsby-plugin-graphql-config@1.9.0
     - gatsby-plugin-image@2.9.0
     - gatsby-plugin-jss@4.9.0
     - gatsby-plugin-layout@3.9.0
     - gatsby-plugin-less@6.9.0
     - gatsby-plugin-lodash@5.9.0
     - gatsby-plugin-manifest@4.9.0
     - gatsby-plugin-mdx@3.9.0
     - gatsby-plugin-netlify-cms@6.9.0
     - gatsby-plugin-no-sourcemaps@4.9.0
     - gatsby-plugin-nprogress@4.9.0
     - gatsby-plugin-offline@5.9.0
     - gatsby-plugin-page-creator@4.9.0
     - gatsby-plugin-postcss@5.9.0
     - gatsby-plugin-preact@6.9.0
     - gatsby-plugin-preload-fonts@3.9.0
     - gatsby-plugin-react-css-modules@4.9.0
     - gatsby-plugin-react-helmet@5.9.0
     - gatsby-plugin-remove-trailing-slashes@4.9.0
     - gatsby-plugin-sass@5.9.0
     - gatsby-plugin-schema-snapshot@3.9.0
     - gatsby-plugin-sharp@4.9.0
     - gatsby-plugin-sitemap@5.9.0
     - gatsby-plugin-styled-components@5.9.0
     - gatsby-plugin-styled-jsx@5.9.0
     - gatsby-plugin-styletron@7.9.0
     - gatsby-plugin-stylus@4.9.0
     - gatsby-plugin-subfont@4.9.0
     - gatsby-plugin-twitter@4.9.0
     - gatsby-plugin-typescript@4.9.0
     - gatsby-plugin-typography@4.9.0
     - gatsby-plugin-utils@3.3.0
     - gatsby-react-router-scroll@5.9.0
     - gatsby-remark-autolink-headers@5.9.0
     - gatsby-remark-code-repls@6.9.0
     - gatsby-remark-copy-linked-files@5.9.0
     - gatsby-remark-custom-blocks@4.9.0
     - gatsby-remark-embed-snippet@7.9.0
     - gatsby-remark-graphviz@4.9.0
     - gatsby-remark-images-contentful@5.9.0
     - gatsby-remark-images@6.9.0
     - gatsby-remark-katex@6.9.0
     - gatsby-remark-prismjs@6.9.0
     - gatsby-remark-responsive-iframe@5.9.0
     - gatsby-remark-smartypants@5.9.0
     - gatsby-sharp@0.3.0
     - gatsby-source-contentful@7.7.0
     - gatsby-source-drupal@5.9.0
     - gatsby-source-faker@4.9.0
     - gatsby-source-filesystem@4.9.0
     - gatsby-source-graphql@4.9.0
     - gatsby-source-hacker-news@4.9.0
     - gatsby-source-lever@4.9.0
     - gatsby-source-medium@4.9.0
     - gatsby-source-mongodb@4.9.0
     - gatsby-source-npm-package-search@4.9.0
     - gatsby-source-shopify@6.9.0
     - gatsby-source-wikipedia@4.9.0
     - gatsby-source-wordpress@6.9.0
     - gatsby-telemetry@3.9.0
     - gatsby-transformer-asciidoc@3.9.0
     - gatsby-transformer-csv@4.9.0
     - gatsby-transformer-documentationjs@6.9.0
     - gatsby-transformer-excel@4.9.0
     - gatsby-transformer-hjson@4.9.0
     - gatsby-transformer-javascript-frontmatter@4.9.0
     - gatsby-transformer-javascript-static-exports@4.9.0
     - gatsby-transformer-json@4.9.0
     - gatsby-transformer-pdf@3.9.0
     - gatsby-transformer-react-docgen@7.9.0
     - gatsby-transformer-remark@5.9.0
     - gatsby-transformer-screenshot@4.9.0
     - gatsby-transformer-sharp@4.9.0
     - gatsby-transformer-sqip@4.9.0
     - gatsby-transformer-toml@4.9.0
     - gatsby-transformer-xml@4.9.0
     - gatsby-transformer-yaml@4.9.0
     - gatsby-worker@1.9.0
     - gatsby@4.9.0
    LekoArts committed Mar 1, 2022
    Copy the full SHA
    6b160cc View commit details
Showing 391 changed files with 8,722 additions and 8,154 deletions.
3 changes: 3 additions & 0 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
@@ -350,6 +350,9 @@ jobs:
- run: # Quick upgrade to the v2 (any version, we just need the real set version)
command: yarn policies set-version berry
working_directory: /tmp/e2e-tests/gatsby-pnp
- run: # TODO: remove pinned version
command: yarn set version 3.1.1
working_directory: /tmp/e2e-tests/gatsby-pnp
- run: # Explicitly set nodeLinker to avoid Yarn selecting node_modules due to the Yarn 1.x lockfile
command: yarn config set nodeLinker pnp
working_directory: /tmp/e2e-tests/gatsby-pnp
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/BUG_REPORT.yml
Original file line number Diff line number Diff line change
@@ -89,7 +89,7 @@ body:
- type: textarea
attributes:
label: Config Flags
description: Do you use any "flags" inside "gatsby-config.js"? If yes, please paste them here.
description: Do you use any "flags" inside "gatsby-config"? If yes, please paste them here.
placeholder: |
For example:
4 changes: 2 additions & 2 deletions .github/workflows/schedule-stale.yml
Original file line number Diff line number Diff line change
@@ -23,15 +23,15 @@ jobs:
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out [gatsby.dev/contribute](https://www.gatsbyjs.com/contributing/how-to-contribute/) for more information about opening PRs, triaging issues, and contributing!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out [gatsby.dev/contribute](https://www.gatsbyjs.com/contributing#how-to-contribute) for more information about opening PRs, triaging issues, and contributing!
Thanks for being a part of the Gatsby community! 💪💜
close-issue-message: |
Hey again!
It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.
Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m `HUMAN_EMOTION_SORRY`. Please feel free to comment on this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out [gatsby.dev/contribute](https://www.gatsbyjs.com/contributing/how-to-contribute/) for more information about opening PRs, triaging issues, and contributing!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out [gatsby.dev/contribute](https://www.gatsbyjs.com/contributing#how-to-contribute) for more information about opening PRs, triaging issues, and contributing!
Thanks again for being part of the Gatsby community! 💪💜
stale-issue-label: "stale?"
2 changes: 2 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -65,3 +65,5 @@ package-lock.json
!themes/gatsby-starter-notes-theme/package-lock.json
!themes/gatsby-starter-theme/package-lock.json
!themes/gatsby-starter-theme-workspace/package-lock.json

.parcel-cache
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
## How to Contribute
# Contributing to Gatsby

For information related to contributing to Gatsby, please check out the [How to Contribute](https://www.gatsbyjs.com/contributing/how-to-contribute/) section of the documentation at the Gatsby site.
For information related to contributing to Gatsby, please check out the [Contributing to Gatsby](https://www.gatsbyjs.com/contributing/) section of the documentation at the Gatsby site.
3 changes: 3 additions & 0 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# Governance

Please check out the [Governance Model](https://www.gatsbyjs.com/contributing/gatsby-governance-model/) page on the Gatsby site.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -64,7 +64,7 @@
<a href="https://gatsby.dev/discord">Discord</a>
</h2>

Gatsby is a modern web framework for blazing fast websites.
Gatsby helps professional developers efficiently create maintainable, highly-performant, content-rich websites.

- **Go Beyond Static Websites.** Get all the benefits of static websites with none of the
limitations. Gatsby sites are fully functional React apps, so you can create high-quality,
1 change: 0 additions & 1 deletion docs/contributing/blog-contributions.md
Original file line number Diff line number Diff line change
@@ -23,7 +23,6 @@ Things we’re looking for in Gatsby blog content:

- Information to help others overcome challenges you’ve faced while working with Gatsby
- Stories about how Gatsby helped you overcome different challenges on work and personal projects
- Gatsby case studies
- Showcasing a tool, fix, or other content you or someone else have contributed to Gatsby’s open source community
- Showcasing a tool, fix, or other content someone else has contributed to Gatsby’s open source community
- Clear and thoughtful explanations of technical details or complex concepts related to React, GraphQL, web and application development, open-source contribution, Gatsby core, and other Gatsby-adjacent subject matter
162 changes: 74 additions & 88 deletions docs/contributing/code-contributions.md
Original file line number Diff line number Diff line change
@@ -2,110 +2,96 @@
title: Code Contributions
---

The beauty of contributing to open source is that you can clone your favorite project, get it running locally, and test out experiments and changes in real time! Way to feel like a wizard.
The beauty of contributing to open source is that you can clone your favorite project, get it running locally, and test out experiments and changes in real time! You get the opportunity to participate in a community while feeling a wizard doing it. For instructions on contributing to the docs, visit the [docs contributions page](/contributing/docs-contributions/).

## Repo setup
Gatsby uses a "monorepo" pattern to manage its many dependencies and relies on [Lerna](https://lerna.js.org/) and [Yarn](https://yarnpkg.com/) to configure the repository for both active development and documentation infrastructure changes.

This page includes details specific to the Gatsby core and ecosystem codebase.
Yarn is a package manager for your code, similar to [npm](https://www.npmjs.com/). While npm is used to develop Gatsby sites with the CLI, contributing to the Gatsby repo requires Yarn for the following reason: we use Yarn's [workspaces](https://yarnpkg.com/lang/en/docs/workspaces/) feature that comes really handy for monorepos. It allows us to install dependencies from multiple `package.json` files in sub-folders, enabling a faster and lighter installation process.

To start setting up the Gatsby repo on your machine using git, Yarn and Gatsby-CLI, check out the page on [setting up your local dev environment](/contributing/setting-up-your-local-dev-environment/).
## Setting up your local dev environment

Alternatively, you can skip the local setup and [use an online dev environment](/contributing/using-an-online-dev-environment/).
### Install Node and Yarn

To contribute to the blog, check out the setup steps on the [blog contributions](/contributing/blog-contributions/) page. For instructions on contributing to the docs, visit the [docs contributions page](/contributing/docs-contributions/).
- Ensure you have the latest **LTS** version of Node installed (`>= 14.15.0`) by executing `node --version`
- [Install](https://yarnpkg.com/en/docs/install) the Yarn package manager.
- Ensure you have the version 1 of Yarn installed (`^1`) by executing `yarn --version`. The Gatsby monorepo does not yet support later versions of Yarn.

## Creating your own plugins and loaders
### Fork, clone, and branch the repository

If you create a loader or plugin, we would love for you to open source it and put it on npm. For more information on creating custom plugins, please see the documentation for [plugins](/docs/plugins/) and the [API specification](/docs/api-specification/).
- [Fork](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) the [official `gatsbyjs/gatsby` repository](https://github.com/gatsbyjs/gatsby).
- Clone your fork: `git clone https://github.com/<your-username>/gatsby.git`
- Set up repo and install dependencies: `yarn run bootstrap`
- Create a topic branch: `git checkout -b topics/new-feature-name`
- Run `yarn run watch` from the root of the repo to watch for changes to packages' source code and compile these changes on-the-fly as you work.
- Note that the watch command can be resource intensive. To limit it to the packages you're working on, add a scope flag, like `yarn run watch --scope={gatsby,gatsby-cli}`.
- To watch just one package such as `gatsby`, run `yarn run watch --scope=gatsby`.

## Contributing example sites
> **Note:** Optionally you can run `git clone --depth=1 https://github.com/<your-username>/gatsby.git` to do a shallow clone (smaller download size) rather than a deep clone, however this sometimes leads to problems when you want to reference older upstream branches.
Gatsby's policy is that "Using" example sites (like those in the [examples part of the repo](https://github.com/gatsbyjs/gatsby/tree/master/examples)) should only be around plugins that are maintained by the core team as it's hard to keep things up to date otherwise.
### Testing out changes in an example project

To contribute example sites, it is recommended to create your own GitHub repo and link to it from your source plugin, etc.

## Using Docker to set up test environments

With all of the possible Gatsby integrations, it might help to spin up a Docker container with the software application you need to test. This makes installation a breeze, so you can focus less on getting set up and more on the integration details that matter to you.

> Do you have a setup not listed here? Let us know by adding it to this file and opening a PR.
### Docker, WordPress and Gatsby

To install WordPress to use with Gatsby, this `docker-compose.yml` file will come in handy:

```yaml:title=docker-compose.yml
version: "2"
services:
db:
image: mysql:5.6
container_name: sessions_db
ports:
- "3306:3306"
volumes:
- "./.data/db:/var/lib/mysql"
restart: always
environment:
MYSQL_ROOT_PASSWORD: wordpress
MYSQL_DATABASE: wordpress
MYSQL_USER: wordpress
MYSQL_PASSWORD: wordpress
wordpress:
image: wordpress:latest
container_name: sessions_wordpress
depends_on:
- db
links:
- db
ports:
- "7000:80"
restart: always
environment:
WORDPRESS_DB_HOST: db:3306
WORDPRESS_DB_PASSWORD: wordpress
volumes:
- ./wp-content:/var/www/html/wp-content
- ./wp-app:/var/www/html
phpmyadmin:
image: phpmyadmin/phpmyadmin
container_name: sessions_phpmyadmin
environment:
- PMA_ARBITRARY=1
- PMA_HOST=sessions_db
- PMA_USER=wordpress
- PMA_PASSWORD=wordpress
restart: always
ports:
- 8080:80
volumes:
- /sessions
```

Use the above file contents when following the Docker WordPress install instructions: https://docs.docker.com/compose/wordpress/

Using Docker Compose, you can start and stop a WordPress instance and integrate it with the [Gatsby WordPress source plugin](/docs/sourcing-from-wordpress/).

## Development tools

### Debugging the build process
- Install [gatsby-dev-cli](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-dev-cli):
- Make sure you have the Gatsby Dev CLI installed with `gatsby-dev -v`
- If not, install globally: `yarn global add gatsby-dev-cli`
- Run `gatsby-dev --set-path-to-repo /path/to/my/forked/version/gatsby` to point `gatsby-dev-cli` to your fork
- Run `yarn install` in each of the sites you're testing.
- For each of your Gatsby test sites, run the `gatsby-dev` command inside the test site's directory to copy
the built files from your cloned copy of Gatsby. It'll watch for your changes
to Gatsby packages and copy them into the site. For more detailed instructions
see the [gatsby-dev-cli README](https://www.npmjs.com/package/gatsby-dev-cli) and check out the [gatsby-dev-cli demo video](https://www.youtube.com/watch?v=D0SwX1MSuas).
- To copy files from just one package such as `gatsby`, run `gatsby-dev --packages gatsby`
- Note: If you plan to modify packages that are exported from `gatsby` directly, you need to either add those manually to your test sites so that they are listed in `package.json` (e.g. `yarn add gatsby-link`), or specify them explicitly with `gatsby-dev --packages gatsby-link`).
- If you've recently run `gatsby-dev` your `node_modules` will be out of sync with current published packages. In order to undo this, you can remove the `node_modules` directory, revert any changes to `package.json` and lockfiles, and reinstall modules with `npm install` or `yarn install` . Alternatively, you can run:

Check [Debugging the build process](/docs/debugging-the-build-process/) page to learn how to debug Gatsby.
```shell
git checkout package.json; yarn --force
```

### Add tests

- Add tests and code for your changes.
- Begin by adding unit tests with Jest.
- If you want to test out this feature in a more real-world application you can also consider adding [integration tests](https://github.com/gatsbyjs/gatsby/tree/master/integration-tests) and [end-to-end tests](https://github.com/gatsbyjs/gatsby/tree/master/e2e-tests).
- If you're unsure on how to add tests or which types of test, ask in a comment in the pull request
- Once you're done, make sure all unit tests still pass: `yarn test`.
- To run tests for a single package you can run: `yarn jest <package-name>`.
- To run a single test file you can run: `yarn jest <file-path>`.
- Once you push your changes to GitHub, the CI will run tests in a controlled environment and might uncover failures on e.g. different type of machines (Linux vs. Windows)

If you're adding e2e tests and want to run them against local changes:

- In the root of the monorepo, run `yarn lerna run build --scope=<package-name>` where `package-name` is the directory containing the changes you're testing.
- Run `gatsby-dev` inside your specific e2e test directory, for example `e2e-tests/themes/development-runtime`.
- While the previous step is running, open a new terminal window and run `yarn test` in that same e2e test directory.

### Troubleshooting

At any point during the contributing process the Gatsby team would love to help! For help with a specific problem you can [open an Discussion on GitHub](https://github.com/gatsbyjs/gatsby/discussions/categories/help). Or drop in to [our Discord server](https://gatsby.dev/discord) for general community discussion and support.

## Official theme development
- When you went through the initial setup some time ago and now want to contribute something new, you should make sure to [sync your fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork) with the latest changes from the primary branch on [gatsbyjs/gatsby](https://github.com/gatsbyjs/gatsby). Otherwise, you might run into issues where files are not found as they were renamed, moved, or deleted.
- After syncing your fork, run `yarn run bootstrap` to compile all packages. When files or tests depend on the build output (files in `/dist` directories) they might fail otherwise.
- Make sure to run `yarn run watch` on the packages' source code you're changing.

This section is for official theme development. If you are looking
to build your own theme, see [building themes](/docs/themes/building-themes/).
## How to open a pull request

Themes live in their own [repo](https://github.com/gatsbyjs/themes). The themes themselves live in the `packages` directory and starters using them are in the `starters` directory. In order to work on a theme, find the starter that uses it and do the following:
If you've made all your changes, added tests, and want to contribute your changes to Gatsby, you can head over to the [How to open a pull request documentation](/contributing/how-to-open-a-pull-request) to learn more.

1. Run `yarn` in your terminal in the root of the repo.
2. Still in the repo root, run `yarn workspace <starter name> develop`.
## Other contributions

From there, you can make changes in the theme and see them reflected in the running site.
### Creating your own plugins

If you create a loader or plugin, we would love for you to open source it and put it on npm. For more information on creating custom plugins, please see the documentation for [plugins](/docs/plugins/) and the [API specification](/docs/api-specification/).

### Contributing example sites

Gatsby's policy is that "Using" example sites (like those in the [examples part of the repo](https://github.com/gatsbyjs/gatsby/tree/master/examples)) should only be around plugins that are maintained by the core team as it's hard to keep things up to date otherwise.

To contribute example sites, it is recommended to create your own GitHub repo and link to it from your source plugin, etc. You can also create a starter project and submit it to the [starter showcase](/starters/submissions).

## Debugging the build process

Check [Debugging the build process](/docs/debugging-the-build-process/) page to learn how to debug Gatsby.

## Feedback

At any point during the contributing process the Gatsby team would love to help! For help with a specific problem you can [open an issue on GitHub](/contributing/how-to-file-an-issue/). Or drop in to [our Discord server](https://gatsby.dev/discord) for general community discussion and support.
At any point during the contributing process the Gatsby team would love to help! For help with a specific problem you can [open an Discussion on GitHub](https://github.com/gatsbyjs/gatsby/discussions/categories/help). Or drop in to [our Discord server](https://gatsby.dev/discord) for general community discussion and support.
5 changes: 1 addition & 4 deletions docs/contributing/code-of-conduct.md
Original file line number Diff line number Diff line change
@@ -44,7 +44,4 @@ When faced with repeated bad faith comments or harassment after an earnest attem

## Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4.

- homepage: https://contributor-covenant.org
- version: https://contributor-covenant.org/version/1/4/
This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org), [version 1.4](https://contributor-covenant.org/version/1/4/).
23 changes: 0 additions & 23 deletions docs/contributing/community-contributions.md

This file was deleted.

Loading