next.js: Turbopack doesn't support yarn PnP
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
Operating System:
Platform: linux
Arch: x64
Version: #1 SMP PREEMPT_DYNAMIC Wed Oct 26 15:55:21 UTC 2022
Binaries:
Node: 18.1.0
npm: 8.8.0
Yarn: 3.2.4
pnpm: 7.14.2
Relevant packages:
next: 13.0.3-canary.1
eslint-config-next: 13.0.2
react: 18.2.0
react-dom: 18.2.0
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
Describe the Bug
When creating new next app with yarn create next-app --experimental-app and enabling turbopack, it will result in several warnings and error:
warning - [other]
Could not resolve React Refresh runtime
React Refresh will be disabled.
To enable React Refresh, install the `react-refresh` and `@next/react-refresh-utils` modules.
warning - [other]
Could not resolve React Refresh runtime
React Refresh will be disabled.
To enable React Refresh, install the `react-refresh` and `@next/react-refresh-utils` modules.
warning - [other]
Could not resolve React Refresh runtime
React Refresh will be disabled.
To enable React Refresh, install the `react-refresh` and `@next/react-refresh-utils` modules.
error -
[rendering]
[root of the dev server]/
Error during SSR Rendering
Error: Cannot find module 'next/dist/server/node-polyfill-fetch'
at <unknown> (.next/server/app/chunks/ssr/_4b5bba.js:83:15)
at <unknown> (.next/server/app/chunks/ssr/_4b5bba.js:86:3)
at [project-with-next]/app/entry (ecmascript, ssr) (.next/server/app/chunks/ssr/_4b5bba.js:313:3)
at <unknown> (.next/server/app/chunks/ssr/_4b5bba.js:692:21)
at runModuleExecutionHooks (.next/server/app/chunks/ssr/_4b5bba.js:730:5)
at instantiateModule (.next/server/app/chunks/ssr/_4b5bba.js:691:5)
at instantiateRuntimeModule (.next/server/app/chunks/ssr/_4b5bba.js:1276:12)
at <unknown> (.next/server/app/chunks/ssr/_4b5bba.js:331:1)
at <unknown> (.next/server/app/chunks/ssr/_4b5bba.js:1327:39)
at <anonymous>
at Object.registerChunk [as push] (.next/server/app/chunks/ssr/_4b5bba.js:1327:25)
at Object.<anonymous> (.next/server/app/chunks/rsc/app_layout.tsx_layout-entry.tsx_with-client-chunks.js:1:41)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Module._load (node:internal/modules/cjs/loader:827:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object.<anonymous> (.next/server/app/index.js:12:1)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Module._load (node:internal/modules/cjs/loader:827:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at <unknown> (node:internal/main/run_main_module:17:47)
[resolve]
[next]/entry/fallback.tsx
Error resolving esm request
unable to resolve module "react" with subpath "/jsx-runtime"
Error resolving esm request
unable to resolve module "react-dom" with subpath "/client"
[next]/overlay/internal/ErrorBoundary.tsx
Error resolving esm request
unable to resolve module "react"
Error resolving esm request
unable to resolve module "react" with subpath "/jsx-runtime"
[next]/overlay/internal/ReactDevOverlay.tsx
Error resolving esm request
unable to resolve module "react"
Error resolving esm request
unable to resolve module "react" with subpath "/jsx-runtime"
... [24 more paths] are hidden, run with --show-all to show all
Expected Behavior
It should display default nextjs page after project creation
Link to reproduction
To Reproduce
- Run
yarn create next-app --experimental-app - edit package.json to
"dev": "next dev --turbo", - Run it with
yarn dev
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 17
- Comments: 17 (7 by maintainers)
The Trubo brand has done an amazing job of pushing monorepo tooling forward. Similarly PnP has been a big life improvement for managing a large monorepo. I believe lack of support for PnP would be a big miss for the Turbo brand as great monorepo compatible tooling.
Part of the Turbo philosophy is “never doing the same work twice”. I believe Yarn Zero-installs operates under the same philosophy.
I understand that PnP is less popular then traditional node_modules, but a Turbo Pack + PnP combo would be a big quality of life improvement for large projects. I understand you have a lot more people to answer to then just us PnP folk, but I urge the team to reconsider support. Is it possible @arcanis existing work could be used to make PnP happen?
Thanks for all the hard work the teams does!
I already implemented the PnP resolution for Rust as a crate, in https://github.com/arcanis/pnp-rust. I’m very open to merge any change necessary to make it easier to use on your side.
Hello, is there any update for pnp support for turbo pack ?
Any news?
Error: Cannot find module 'next/dist/server/node-polyfill-fetch'… when trying to load an app with Turbopack.Here’s a reproduction with
See screenshots in https://github.com/belgattitude/artist/pull/4
I found that in
standalone/node_modules/nextpoints to.pnpm/next@12.../next/dist/server/next-server.js. That file exists but none of its imports are present. This file is created right after I runpnpm exec next build, if I delete it then I can start my standalone server.I am seeing this too in a
pnpmmonorepo