-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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] Yarn PnP installs #2369
Comments
Any updates? This would be pretty awesome, but I assume it's a huge undertaking. |
Yarn 4 is great, I don't know why vercel doesn't want to implement the PnP resolution. It'll help us a lot in the CI build time and the only package that's not supported right now in my repo is turbo |
Closing as a duplicate of vercel/next.js#42651 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which project is this feature idea for?
Turbopack
(note: I saw #693, and specifically #693 (comment), but that issue was about Turborepo, not Turbopack. I checked with @sokra who confirmed that the goal is for Turbopack to eventually support everything Webpack supports, hence this issue specifically about Turbopack)
Describe the feature you'd like to request
Turbopack isn't compatible with Yarn PnP installs, unlike both Webpack and Esbuild. There are two reasons for this:
Reproduction
Describe the solution you'd like
Two options:
Implement the zip fs logic within Turbopack, and make it take into account the
.pnp.data.json
data file as per specAllow Node plugins to handle specific file loading and resolution (like Webpack plugins; but then it'd be slower than necessary, and wouldn't be supported natively as it currently is in other bundlers)
Describe alternatives you've considered
In the meantime users can workaround this problem by reverting to the node-modules linker, but they don't get the PnP benefits anymore (fast installs, ghost dependency protection, semantic erroring, ...), which is often a blocker.
The text was updated successfully, but these errors were encountered: