Can I upgrade to React 19 while still using withUrqlClient from next-urql and the Pages router?
#3732
Replies: 1 comment 11 replies
-
|
Having the same issue. URQL looks like a blocker for upgrading in this case. Could you assist, please? @JoviDeCroock |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, they introduced the issue in 1.6.0 but I cannot contact them. Do you know anyone inside? 😞 @JoviDeCroock |
Beta Was this translation helpful? Give feedback.
-
|
@RomanFausek: Just for context, I'm also the original author of |
Beta Was this translation helpful? Give feedback.
-
|
@kitten Thanks for the info! I noticed you’re the top contributor, so I thought I'd give it a shot—my bad! 🙌 @JoviDeCroock Would it make sense to expand the Next.js (Pages Router) documentation to cover fetching on SSR and hydrating without |
Beta Was this translation helpful? Give feedback.
-
|
We bumped it to support React 19 to help out some users that were caught off guard using Next.js when it prebundled React 19 before its official release. But generally it shouldn't be used past R18 as @kitten is suggesting. The library is still marked |
Beta Was this translation helpful? Give feedback.
-
|
We spent some (actually a lot) time and got rid of it as you suggested. I plan to contribute to your docs to help out others. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working on a fairly large repo and don't have a good enough reason to migrate from the Pages router to the App router. I'm on React 18.2 and I'm looking to upgrade to React 19 + NextJS 15.
I'm facing issues running my setup because
next-urql(which was archived almost 5 years ago) has a dependency on an older version ofreact-ssr-prepass, which isn't compatible with React 19.Beta Was this translation helpful? Give feedback.
All reactions