Open jb-thery opened 1 year ago
I also encountered this issue, but in my case it occurred only when the dynamic route included spaces (or possibly other unusual characters, it had both).
The error payload was a follows
- router evaluation failed: no message received from javascript stream
[500] error (12ms): error during Next.js routing for /artforge/testing/file/8cefdc9676dc7d0d/images/DALL·E 2023-05-18 15.44.08 - A relaxed oxen sitting on a sofa in the style of monet.png
Caused by:
- router evaluation failed: no message received from javascript stream
Debug info:
- Execution of get_from_source failed
- Execution of resolve_source_request failed
- Execution of NextRouterContentSource::get failed
- error during Next.js routing for /artforge/testing/file/8cefdc9676dc7d0d/images/DALL·E 2023-05-18 15.44.08 - A relaxed oxen sitting on a sofa in the style of monet.png
- router evaluation failed: no message received from javascript stream
once I removed the --turbo flag from next dev, it worked as expected
I had a similar problem in PNPM monorepo which was resolved with adding an undocumented --root path/to/root
flag discussed here: https://github.com/vercel/turbo/issues/4763#issuecomment-1531880273.
However, this resulted in a wall of errors related to SSR, seems like it's caused by still resolving the package root as the project root and trying to load stuff from node_modules/.pnpm
which doesn't exist:
var nodePreGyp = __turbopack_require__("[project]/node_modules/.pnpm/@mapbox+node-pre-gyp@1.0.10/node_modules/@mapbox/node-pre-gyp/lib/node-pre-gyp.js (ecmascript, rsc)");
same erro here using tubro
I was having this issue as well. Once I removed --turbo
from next dev
it worked just fine.
Verify canary release
Provide environment information
Which area(s) of Next.js are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue or a replay of the bug
https://github.com/jb-thery/turbo-repo-next-turbo-pack-issue
To Reproduce
Create a basic turbo repo with pnpm
Add --turbo ti nex dev script in web app directory
Describe the Bug
I have this issue when i add --turbo flag on dev server script :
or
Expected Behavior
Use turbo pack dev server
Which browser are you using? (if relevant)
Chrome
How are you deploying your application? (if relevant)
Vercel