Can't deploy my project (PRR enabled)

[Vette1123]

Page to Investigate

https://vercel.com/

Steps to Reproduce

I'm trying to delpoy my project, but i'm getting this weird error.

Error: Invariant: PPR lambda isn't streaming

[leerob]

Are you using an experimental feature like Partial Prerendering? Can you share your code?

[steven-tey]

@Vette1123 can you try upgrading next to the latest canary to see if you're still facing this issue?

[Vette1123]

Hello @leerob , thanks for answering.

The issue happened when i enabled PPR in my next.config.js

Deployment is successful when i removed that, i was practising the next.js 14 example here: https://github.com/Vette1123/next-14-dashboard

How can i enable PPR in deployed version?

[jayair]

Same, here's my repo: https://github.com/jayair/nextjs-learn/tree/735db5968ec66bdc3d39407bef585a65c920639c

I'm trying out PPR with next@canary.

[jayair]

Looks like a false alarm. The next couple of deployments seemed fine!

[Gawdfrey]

I am getting the same error trying to deploy my next app on vercel. On version 14.0.3-canary.8, PPR is enabled.
Not able to share repo, so unsure how helpful this is, sorry!

[abiddraws]

I had this error , that got resolved when I removed the line export const dynamic = "force-dynamic"; from my code.

[jahirfiquitiva]

hey @leerob , I'm facing the very same issue: Error: Invariant: PPR lambda isn't streaming

Here's my repo: jahirfiquitiva/jahir.dev#68

I'm not sure what is causing it and the Vercel deployment logs don't mention it either. 😕

I'd be grateful if you could please help me out 🙌

[abiddraws]

Try after removing this dynamic property revalidate from all your code

[jahirfiquitiva]

@abiddraws I tried and it still failed
jahirfiquitiva/jahir.dev@f6a11e7

[zaynelovecraft]

This is happening to me also, any one figure out how to fix this?

[lourd]

I just ran into this issue as well. Latest canary, 14.2.0-canary.6. Code is here lourd/descioli.com#45. Tried redeploying; got the same error.

[jahirfiquitiva]

What worked for me was removing export const dynamicParams = false
Give it a try!

[lourd]

Thanks for the suggestion! I tried it, removing dynamicParams altogether, and it did successfully deploy. But now when loading the pages that have PPR the server-side function crashes with an error like this:

Error: Expected the resume to render <u> in this slot but instead it rendered <d>. The tree doesn't match so React will fallback to client rendering.

This is the same error I have when doing next start locally, with or without dynamicParams. The only issue I can find that references this type of error is vercel/next.js#60620

[lourd]

Strangely re-adding dynamicParams=false the application now successfully deployed 🤔 but still crashes on the routes with PPR

[me-imfhd]

I am also facing the same issue, i am using nextjs 14 experimental ppr to true, is this getting fixed anytime soon?