-
Notifications
You must be signed in to change notification settings - Fork 55
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 support for Yarn 3 #62
Comments
Is this issue fixed since I am also getting same type of error? |
@epomatti @alagiribuddhar I had the same error, and the clue to resolve it is to add pythonia to webpack externals in case when we create a bundle. I bet in your use-cases |
if anyone comes across this in the future and is using Yarn PnP, you can resolve this error by telling yarn to unplug the package at install time package.json "dependenciesMeta": {
"[email protected]": {
"unplugged": true
}
} that will force yarn to install the package to an actual FS location, rather than resolve it virtually from within the cached zip file (which this package doesn't support yet) |
@KrzysztofZawisla I think there is a similar problem with pnpm, would you be able to point me in the right direction to investigate? Update: solution is the same as this issue: ldapjs/node-ldapjs#967 |
Getting this error when running latest yarn versions:
The text was updated successfully, but these errors were encountered: