We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There's two way to specify pnpm version in package.json:
{ "packageManager": "pnpm@6.23.1", "engines": { "pnpm": ">=6" }, }
It should prefer packageManager field because it is more precise (this field does not support semver).
The text was updated successfully, but these errors were encountered:
TBH, I would be happy to deprecate the engines.pnpm field but I think it is too strict to only allow exact versions in the packageManager field.
engines.pnpm
packageManager
Sorry, something went wrong.
I think engines.pnpm is okay since yarn also supports it IIRC (engines.yarn?)
engines.yarn
Successfully merging a pull request may close this issue.
There's two way to specify pnpm version in package.json:
It should prefer packageManager field because it is more precise (this field does not support semver).
The text was updated successfully, but these errors were encountered: