Open richtera opened 3 months ago
Once you modify the polyfill it gets further but I have problems with my /404 routing so I will push a fix for that.
Added a branch "patched" into my repo which patches nextjs and fixes the routing issues to deploy the whole thing on cloudflare to make sure all the pieces work together.
hey @richtera - have you had any luck with the next team on this? facing a similar issue
No they didn't agree it was their issue. You're welcome to use my patch. Maybe if you ping them separately?
Link to the code that reproduces this issue
https://github.com/richtera/wownar
To Reproduce
The same thing happens with yarn pages:build which is why I posted an issue there first https://github.com/cloudflare/next-on-pages/issues/791
Current vs. Expected behavior
Currently is errors out because the polyfill for process doesn't have version on it. Rewriting the polyfill as
https://github.com/vercel/next.js/blob/2966b85bccf0d2593e04dd3aa0ac474f53715d2f/packages/next/src/server/web/sandbox/context.ts#L130
makes builds pass. I can't tell when this started or anything about that however. This is just a fresh nextjs project I got from elsewhere https://github.com/neynarxyz/farcaster-examples/tree/main/wownar and the bug is inside of next.js
Provide environment information
Which area(s) are affected? (Select all that apply)
Not sure, Developer Experience
Which stage(s) are affected? (Select all that apply)
next build (local)
Additional context
Since the code in canary is still missing "version" I am not sure if makes sense to attempt a canary build.