Package incompatibility with React 19
Unanswered
Birman posted this in #help-forum
BirmanOP
Hi, I may not be the first one but I need help with this. I'm working on a very important project that is based on Next 13 but I was asked to upgrade to version 15, however I have problems with the packages since Next 15 installs React 19 RC by default. My question is, should I downgrade to React 18 with Next 15 or what would be the best solution?
10 Replies
Asiatic Lion
same situation here i am doing a next 15 project some of the packages have no stable version in react 19 so i also have this confusion for example react-pdf/renderer is not working in next 15 ,
Milkfish
When installing a package
Add
--legacy-peer-deps
Add
--legacy-peer-deps
Green Kingfisher
Same!
Giant panda
Yeah that fixed, but the question is:
Why on earth is Next using an RC? IMHO is careless and unprofessional
Why on earth is Next using an RC? IMHO is careless and unprofessional
BirmanOP
Sure, but this project is for an important company, where sensitive data is involved. Do you think that using that flag will make it work normally or will I have failures in production?
Milkfish
It depends on the package you're trying to install.
But that's just a way of telling npm to ignore the dependency or version conflicts.
But that's just a way of telling npm to ignore the dependency or version conflicts.
Milkfish
I take it back
Just downgrade to react 18
My app almost crashed cause of dependency conflicts
Just downgrade to react 18
My app almost crashed cause of dependency conflicts
They waited for like 4 months before they pulled the trigger on using react RC channel, they couldnt just sit there and wait forever. That being said, react 19 is suppose to go stable before EOY, either use next 14 or override the deps till it does. If you are concerned use next14, you arent missing much by not being on next15.
For big enterprise or corporate projects I would always suggest giving a major version 3-6 months prior to using it anyways.
3 months at minimum