-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[turbopack] NextJS monorepo issue with pnpm workspace #2783
Comments
This looks resolved with Next.js 13.4 |
It’s actually upgrading to 13.4 which made it start for me.
Tried clearing all .cache files and doing a npm reinstall.
But agree maybe I’m facing a separate issue.
Comma,
Jacob Ford
Designer <http://jacobford.com>About <http://nocomment.llc>Town
Sent from my Underwood Portable 4-Bank
…On May 10, 2023 at 5:40:53 PM, Maia Teegarden ***@***.***> wrote:
This looks resolved with Next.js 13.4
—
Reply to this email directly, view it on GitHub
<#2783 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASV3DRKSM4TBDK3MF5SIHDXFQDOLANCNFSM6AAAAAASGYVRCU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Still facing the issue with
Running |
Hi @maltesa! To confirm, can you do the following in your project: cat node_modules/next/package.json
cat node_modules/next/dist/server/node-polyfill-fetch.js I just want to ensure that the next package is in fact 13.4.*, which definitely has a |
Here it comes:
and
Update. Just to make sure. This is the error I get:
|
This problem occurs when the module does not exist in node_modules directly under the workspace. npm, yarn, or pnpm will place modules in node_modules in the "workspace root", but will not search the workspace's ancestor directories when turbo mode is enabled. I don't know if it is a Turbopack or next-swc issue, but there is a problem with module resolution algorism. |
I have the same issue on my turbo monorepo with : Here is my dev command in my apps folder :
Here is my global dev command :
|
Also running into this issue with |
interestingly, "next/dist/server/node-polyfill.fetch.d.ts " exists but is an empty file. do we know if this is intended? (next 13.4.3) |
Sorry folks, I thought this was fixed with 13.4.0, but it looks definitely fixed with 13.4.4 now. |
Still having this issue when trying to run "next dev --turbo" with pnpm. I'm using
|
Me too in
|
Same issue here |
What version of Turbopack are you using?
next@13.0.4
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
Hello,
I have tried to test turbopack with monorepo structure with PNPM workspace but I encounter this issue :
Error: Cannot find module 'next/dist/server/node-polyfill-fetch'
Without workspace, the project is bundled correctly.
I already try lot of things like :
pnpm install --shamefully-hoist
node-linker:hoisted
But nothing work correctly.
I noticed that the same problem exist with yarn workspace.
Expected Behavior
NextJs app should be bundled correctly with turbopack.
To Reproduce
I made a example in Github repo : https://github.com/Alexandredc/next-turbopack-monorepo-issue
Reproduction Repo
https://github.com/Alexandredc/next-turbopack-monorepo-issue
WEB-1044
The text was updated successfully, but these errors were encountered: