-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Request] Bundle yarn or specific version in package.json #15
Comments
I think the current lockfile was generated with Yarn classic (v1), not Berry (v2/v3). |
ya |
It's not really possible to "bundle" a package-manager with a repo. Corepack will adress this but it's still in an experimental stage the requires opt-in so it's not really feasible for real use as you can't expect developers to have it enabled. The established "solution" OSS is afaik to document the package-manager used under the |
|
Why do something like this? Every package manager should work, no? And if another package manager changes the |
In some situation package url will different with the same package manifest. |
I stand corrected, however that's a "feature" of Yarn Berry that also requires the PnP feature of Yarn Berry to be utilised. |
Noop. It's a feature of yarn. And needn't pnp. PnP is for actually zero install. But specific the yarn version or bundle the yarn is what I said Which just need |
Seems my yarn 3 break the lock file when import the project
The text was updated successfully, but these errors were encountered: