Is PPR during dev mode working for you on release candidate?
Unanswered
Short-eared Owl posted this in #help-forum
Short-eared OwlOP
Using next@rc, react@rc, react-dom@rc (next 15, react 19 release candidates)
A question as simple as that.
I am quite confident that I'm not breaking any rules and I'm implementing PPR properly, with static pages, then using
If I remove
If I build, my project seems to run fine. However, in dev mode, all hot module reloads and page navigations to pages that contain dynamic components trigger these errors, in which I have to refresh the page manually in order to avoid, each time.
A question as simple as that.
I am quite confident that I'm not breaking any rules and I'm implementing PPR properly, with static pages, then using
cookies() inside of Suspense wrapped RSC's, which have unstable_noStore() thrown in to them for extra measure. However, I always get errors like the following:Error: Dynamic server usage: Route /collection couldn't be rendered statically because it used unstable_noStore(). See more info here: https://nextjs.org/docs/messages/dynamic-server-errorIf I remove
noStore, I get errors related to cookies(). Essentially, in dev mode, it appears to me that it does not consider ppr: true or ppr: 'incremental' in next.config.experimental.If I build, my project seems to run fine. However, in dev mode, all hot module reloads and page navigations to pages that contain dynamic components trigger these errors, in which I have to refresh the page manually in order to avoid, each time.