-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add Yarn PnP support? #16
Comments
Sorry, I have no intention of supporting Yarn PnP. It's up to Yarn to support how the ecosystem works, not the other way around. I'd recommend opening an issue on https://github.com/yarnpkg/berry. |
Facing this problem in vercel/vercel#4910. A solution via upgrading this package would be ideal, but if yarn 2 support is not planned, I guess that the community will need to find a workaround. Does anyone have any examples? Perhaps, there exists a package like |
This package already supports PnP, it's using |
@merceyz my knowledge of the topic is quite modest, so what you’re saying may well be true. What are your thoughts on vercel/vercel#4910 (reply in thread)? This is what points the investigation towards this issue. |
Lets take that in yarnpkg/berry#2031, no need to bother Sindre with this |
Yarn v2 is moving away from node_modules to use Plug'n'Play instead. If I understand this all correctly, it would be very helpful if this package supported PnP-based resolution in addition to the traditional node_modules approach, since many other packages rely on this package for resolution as an alternative to
require.resolve
. For reference:Yarn Plug'n'Play
Thanks for all of your amazing open source work!
The text was updated successfully, but these errors were encountered: