-
Notifications
You must be signed in to change notification settings - Fork 86
Site Deploy Fails Using Yarn 2 PnP #169
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
Comments
Any updates on this? |
I had the same issue. I "fixed" it too by setting |
Just adding "berry" as a keyword here. Should be addressed asap. |
I've been doing some research on this but haven't had much luck on finding a solution. I did find this issue on Yarn 2's repo that seems to be what we're running into here: yarnpkg/berry#1467 Is there a way for me to locally test this sort of thing? It's a pretty specific issue and I'm not really sure how to get started with it, and I don't see any tests that relate to |
Is Yarn v2 or v3 used here? |
This is something we may address in the future, but for now see https://docs.netlify.com/configure-builds/manage-dependencies/#yarn where it shows you how to configure yarn to set a yarnpath in conjunction with nodelinker. cc: @kitop |
Describe the bug
I recently activated Yarn PnP on my site. However, this is causing the
validateNextUsage
to fail. Switching back to the traditionalnode_modules
fixes the issue.To Reproduce
Expected behavior
Site deploys properly.
Versions
The text was updated successfully, but these errors were encountered: