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

chore: Add direct support for React 19 #1474

Merged
merged 57 commits into from
Jul 23, 2024
Merged

Conversation

gabrielmfern
Copy link
Collaborator

@gabrielmfern gabrielmfern commented May 21, 2024

This PR changes all of our react and react-dom peer dependencies so that they support both all 18.0.0 and 19.0.0, specifically it changes them to ^18.0 || ^19.0. It also updates the React on the demo to be React 19 making sure that everything works there. I have also tested using yalc to make sure that it still works with React 18, and it does just fine.

One trade I had to make was that Next was proving to cause issues if it was on canary while running for a project that used React 19. The easiest solution for now was to use React 18 with Next 14 for now. This has a trade-off of the email export test failing because of different React versions across the workspace. The best fix for this can only come out of this POC branch.

@gabrielmfern gabrielmfern self-assigned this May 21, 2024
Copy link

vercel bot commented May 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-email ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 23, 2024 7:38pm
react-email-demo ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 23, 2024 7:38pm

@gabrielmfern gabrielmfern marked this pull request as draft June 3, 2024 16:39
@gabrielmfern gabrielmfern changed the title chore: Use React 19 betas for all packages chore: Use React 19 release candidate for all packages Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant