-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
React 19 Support #2618
Comments
Adding support for React 19 might be a lot of work, it's also still unclear, looking at the migration guide, if I could still support older React versions with the same @nivo version. The 19 still being a RC at the moment, I think it's not really pressing, and I'd probably need to upgrade gatsby, storybook... as well, which seems like a huge project. Finally, I was migrating tests from It will take time to get there and this should be split in sub-projects, I don't have the bandwidth to handle everything at once. |
Will follow this thread, we are a company that are about to replace our current chart solution. I understand that time estimation is super hard, but do you think this will take years or months after React 19 release? |
React has an issue where they link some libraries and respective PRs how those libraries upgraded to react 19. imho, the starting point would be to run various provided by React 19 codemods which should do the heavy lifting:
|
@o-alexandrov, thank you for sharing, this could help. |
Latest major version of Next.js (version 15) uses React 19 RC, so it's not going to be possible to use Nivo with it |
Man.. this is no good.. |
I was upgrading to Next 15 and by effect React 19, and ended up being blocked by this issue as well. |
I'm about to use Nivo but also like to upgrade to Next 15 / React 19 the next few weeks. Is there a work-around for the moment? |
Is your feature request related to a problem? Please describe.
@nivo/core
(and possibly other packages) have a strict React dependency range that restricts React 19--legacy-peer-deps
flag or--force
for every installation which is not ideal.Describe the solution you'd like
The text was updated successfully, but these errors were encountered: