Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support Gatsby v5 #203

Merged
merged 3 commits into from Nov 30, 2022
Merged

feat: support Gatsby v5 #203

merged 3 commits into from Nov 30, 2022

Conversation

ericapisani
Copy link
Contributor

@ericapisani ericapisani commented Nov 29, 2022

These changes are needed for Gatsby v5 support.

As Gatsby v4 continues to be supported (although in maintenance), it is included as a valid peer dependency, and node 14 is still the minimum version.

Migration guide from Gatsby: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v4-to-v5/

Fixes #195

Similar to changes done in PR #196 , but I wanted to include an .nvmrc as part of the changes and retain Gatsby v4 as a peer dependency since this is still supported by the Gatsby team

Test site incorporating these changes can be found here: https://ep-gatsby-v5.netlify.app/

  • The site linked above is a Gatsby v5 site, but looks the same as our v4 demo site

@ericapisani ericapisani added the type: feature code contributing to the implementation of a feature and/or user facing functionality label Nov 29, 2022
@ericapisani ericapisani self-assigned this Nov 29, 2022
@ericapisani ericapisani requested a review from a team November 29, 2022 17:01
@ascorbic
Copy link
Member

Is there a reason we need to change the minimum node version here? Could we allow odler versions so we can support older versions of Gatsby with the same plugin?

@ericapisani
Copy link
Contributor Author

We can update this to support older versions of node - when I initially opened this PR I hadn't seen what Gatsby does when an incompatible node version is used in v5 and was trying to be as safe as possible here, but based on Gatsby's very clear warning when someone is using <18 and Gatsby v5, we should be able to safely do this

@ericapisani ericapisani changed the title feat!: support Gatsby v5 feat: support Gatsby v5 Nov 30, 2022
Copy link
Member

@ascorbic ascorbic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@kodiakhq kodiakhq bot merged commit 5bda14f into main Nov 30, 2022
@kodiakhq kodiakhq bot deleted the ep/gatsby-v5-updates branch November 30, 2022 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for Gatsby V5
2 participants