Gatsby 5.16.1, node 24, deps updates and cleanups - #1992
Draft
fturmel wants to merge 16 commits into
Draft
Conversation
…ify` automatically
✅ Deploy Preview for codingtrain ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A bit of modernizing and patching deps. It's unfortunate that Gatsby is abandonware at this point, but at least they are supporting the active Node LTS.
Deps updates
React 19 andmost deps upgraded to latestgatsby-plugin-mdxCleanups
./src/styles/pagestosrc/pagesso they are colocated with their component files just like the rest of the projectgatsby-plugin-netlify. Since Gatsby 5.12,gatsby-adapter-netlifyis automatically configured during deployment. Havinggatsby-adapter-netlifyin our package.json deps will help speed up deployments a bit. https://docs.netlify.com/build/frameworks/framework-setup-guides/gatsby/#netlify-integrationHopefully nothing broke in the process. Everything looked good locally.
EDIT: Build failures were related to previous build caches being incompatible. If merged, we will most likely need to manually clear the Netlify cache for the main branch.
EDIT 2: There were hydration errors in the console with React 19 production builds, I'm not sure that Gatsby's compatibility claims were completely accurate. We should stay on 18.