gatsbyjs/gatsby issues and pull requests

#37904 - fix(deps): update dependency chalk to v5

Pull Request - State: closed - Opened by renovate[bot] over 1 year ago - 1 comment
Labels: topic: automation

#37904 - fix(deps): update dependency chalk to v5

Pull Request - State: closed - Opened by renovate[bot] over 1 year ago - 1 comment
Labels: topic: automation

#37902 - chore(deps): update dependency slash to v5 for babel-preset-gatsby

Pull Request - State: closed - Opened by renovate[bot] over 1 year ago - 1 comment
Labels: topic: automation

#37902 - chore(deps): update dependency slash to v5 for babel-preset-gatsby

Pull Request - State: closed - Opened by renovate[bot] over 1 year ago - 1 comment
Labels: topic: automation

#37893 - chore(deps): update dependency @types/fs-extra to v11

Pull Request - State: closed - Opened by renovate[bot] over 1 year ago - 1 comment
Labels: topic: automation

#37893 - chore(deps): update dependency @types/fs-extra to v11

Pull Request - State: closed - Opened by renovate[bot] over 1 year ago - 1 comment
Labels: topic: automation

#37891 - chore(deps): update dependency @testing-library/react to v14

Pull Request - State: closed - Opened by renovate[bot] over 1 year ago - 1 comment
Labels: topic: automation

#37891 - chore(deps): update dependency @testing-library/react to v14

Pull Request - State: closed - Opened by renovate[bot] over 1 year ago - 1 comment
Labels: topic: automation

#37769 - chore(docs): Release Notes for 5.8

Pull Request - State: closed - Opened by gatsbybot over 1 year ago
Labels: type: documentation

#37765 - Issue with automatic port forwarding in GitHub code spaces after upgrading to Gatsby 5

Issue - State: open - Opened by schettn over 1 year ago - 2 comments
Labels: type: bug, status: triage needed

#37765 - Issue with automatic port forwarding in GitHub code spaces after upgrading to Gatsby 5

Issue - State: open - Opened by schettn over 1 year ago - 2 comments
Labels: type: bug, status: triage needed

#37765 - Issue with automatic port forwarding in GitHub code spaces after upgrading to Gatsby 5

Issue - State: open - Opened by schettn over 1 year ago - 2 comments
Labels: type: bug, status: triage needed

#37765 - Issue with automatic port forwarding in GitHub code spaces after upgrading to Gatsby 5

Issue - State: open - Opened by schettn over 1 year ago - 2 comments
Labels: type: bug, status: triage needed

#37751 - Menu Links randomly disappear in develop and / or build

Issue - State: closed - Opened by maweo over 1 year ago - 5 comments
Labels: type: bug, status: needs reproduction, topic: source-wordpress, topic: source-plugins

#37751 - Menu Links randomly disappear in develop and / or build

Issue - State: closed - Opened by maweo over 1 year ago - 5 comments
Labels: type: bug, status: needs reproduction, topic: source-wordpress, topic: source-plugins

#37751 - Menu Links randomly disappear in develop and / or build

Issue - State: closed - Opened by maweo over 1 year ago - 5 comments
Labels: type: bug, status: needs reproduction, topic: source-wordpress, topic: source-plugins

#37729 - Gatsby-source-wordpress: ERROR #11321 after upgrading WPGraphQL to 1.14.0

Issue - State: closed - Opened by Haldaug over 1 year ago - 16 comments
Labels: type: bug, topic: source-wordpress

#37724 - feat(gatsby-core-utils): Add isHttpUrl function

Pull Request - State: closed - Opened by xSyki over 1 year ago - 19 comments
Labels: topic: core

#37722 - [email protected] - No license specified

Issue - State: closed - Opened by xSyki over 1 year ago - 5 comments
Labels: help wanted, stale?, good first issue, type: feature or enhancement, topic: plugins

#37719 - Pages scroll past top margin zero when <Link> is clicked

Issue - State: closed - Opened by rogerf76 over 1 year ago - 6 comments
Labels: type: bug, stale?, status: needs reproduction

#37717 - Page-data not escaping brackets for splat routes

Issue - State: open - Opened by affemaen over 1 year ago - 2 comments
Labels: type: bug, help wanted, status: confirmed

#37706 - Incremental build not working with React.lazy loaded component when a gatsby-config file exists

Issue - State: closed - Opened by joiglifberg over 1 year ago - 6 comments
Labels: type: bug, status: confirmed

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 4 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 2 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 3 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 2 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 2 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 2 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 2 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 6 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37701 - Regression: Gatsby Head API after 5.4.1 no longer working when gatsby-browser and gatsby-ssr with redux are used

Issue - State: open - Opened by princefishthrower over 1 year ago - 4 comments
Labels: type: bug, status: confirmed, topic: core, topic: frontend

#37673 - gatsby-plugin-image and opacity 0

Issue - State: closed - Opened by ile over 1 year ago - 18 comments
Labels: type: bug, stale?, status: needs reproduction

#37498 - fix(gatsby-react-router-scroll): fix issues with anchor links

Pull Request - State: closed - Opened by sapiensfio almost 2 years ago - 2 comments
Labels: topic: frontend

#37432 - Gatsby fails to load when browser is refreshed

Issue - State: closed - Opened by sproctor almost 2 years ago - 8 comments
Labels: type: bug, stale?, status: needs reproduction

#37342 - Allow passing more options to sharp

Pull Request - State: closed - Opened by Cynocracy almost 2 years ago
Labels: status: triage needed

#37242 - Fresh Gatsby 5.2 install, throwing NPM WARN flags for `react-server-dom-webpack`

Issue - State: closed - Opened by lewis-elborn almost 2 years ago - 6 comments
Labels: type: bug

#37242 - Fresh Gatsby 5.2 install, throwing NPM WARN flags for `react-server-dom-webpack`

Issue - State: closed - Opened by lewis-elborn almost 2 years ago - 6 comments
Labels: type: bug

#37242 - Fresh Gatsby 5.2 install, throwing NPM WARN flags for `react-server-dom-webpack`

Issue - State: closed - Opened by lewis-elborn almost 2 years ago - 6 comments
Labels: type: bug

#37242 - Fresh Gatsby 5.2 install, throwing NPM WARN flags for `react-server-dom-webpack`

Issue - State: closed - Opened by lewis-elborn almost 2 years ago - 6 comments
Labels: type: bug

#37242 - Fresh Gatsby 5.2 install, throwing NPM WARN flags for `react-server-dom-webpack`

Issue - State: closed - Opened by lewis-elborn almost 2 years ago - 6 comments
Labels: type: bug

#37242 - Fresh Gatsby 5.2 install, throwing NPM WARN flags for `react-server-dom-webpack`

Issue - State: closed - Opened by lewis-elborn almost 2 years ago - 6 comments
Labels: type: bug

#37204 - chore: remove tracedSVG (#37093) (#37137)

Pull Request - State: closed - Opened by gatsbybot almost 2 years ago
Labels: type: cherry

#37177 - fix(gatsby-plugin-sharp): Pass `failOn` to all pipelines

Pull Request - State: closed - Opened by LekoArts almost 2 years ago - 14 comments
Labels: topic: media

#37177 - fix(gatsby-plugin-sharp): Pass `failOn` to all pipelines

Pull Request - State: closed - Opened by LekoArts almost 2 years ago - 14 comments
Labels: topic: media

#37177 - fix(gatsby-plugin-sharp): Pass `failOn` to all pipelines

Pull Request - State: closed - Opened by LekoArts almost 2 years ago - 14 comments
Labels: topic: media

#37010 - Gatsby 5 Build Fails - FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

Issue - State: closed - Opened by labnol almost 2 years ago - 10 comments
Labels: type: bug

#36993 - fix(gatsby-plugin-google-gtag): correct script to match google's current

Pull Request - State: closed - Opened by benomatis almost 2 years ago - 5 comments
Labels: topic: plugins-analytics

#36982 - Text content does not match server-rendered HTML.

Issue - State: closed - Opened by MotaZor94 almost 2 years ago - 8 comments
Labels: type: bug, status: needs reproduction

#36962 - cannot access metadata: tags information from gatsby-source-contentful plugin

Issue - State: closed - Opened by MakaBaca about 2 years ago - 10 comments
Labels: type: bug, status: needs reproduction, topic: source-contentful

#36956 - SSR issue with React.useId() in React 18 - mismatch between SSR and client versions.

Issue - State: open - Opened by ShaunDychko about 2 years ago - 9 comments
Labels: type: bug, status: confirmed

#36899 - Heap memory usage increase during development builds after upgrading to v4.24.5

Issue - State: open - Opened by skatingincentralpark about 2 years ago - 39 comments
Labels: type: bug, status: confirmed, topic: webpack/babel

#36899 - Heap memory usage increase during development builds after upgrading to v4.24.5

Issue - State: open - Opened by skatingincentralpark about 2 years ago - 38 comments
Labels: type: bug, status: confirmed, topic: webpack/babel