-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
ERR_PNPM_INVALID_OVERRIDE_SELECTOR Cannot parse the "//" selector in the override on windows #4130
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
back to version |
Confirming - Linux, Windows Node: Error:
Stacktrace (found at local Windows machine while debugging):
|
@TemaSM but this was never supported: You can specify only a direct parent package of a dependency and you should use a |
@dennislan what would the "//" selector mean in the overrides? pnpm did not support such syntax. In the past it was just ignored. Here are some examples of override keys: https://pnpm.io/package_json#pnpmoverrides {
"pnpm": {
"overrides": {
"foo": "^1.0.0",
"quux": "npm:@myorg/quux@^1.0.0",
"bar@^2.1.0": "3.0.0",
"qar@1>zoo": "2"
}
}
} |
@zkochan my project's package.json doesn't contain any overrides. Btw, downgrading to pnpm "resolutions": {
"react-dev-utils/chalk/ansi-styles": "https://github.com/codercodingthecode/ansi-styles"
}, |
Is this a |
Nope, my project's package.json |
ok, pnpm reads this field as well. It reads either |
Thanks, removed this obsolete for my project |
I am having similar issue with "minimist ": "1.2.6" having in resolutions field. Error message |
I have the same issue, but it look like is
This is my package.json "resolutions": {
"sass-loader/webpack": "^5.0.0",
} This is my Environment configuration
|
This issue is still relevant, I have this other error
My setup:
|
The issue in all examples is the wrong syntax, but it should be possible to support both yarn and pnpm by setting different values to This still returns an error in pnpm
The problem is that according to the docs
which makes no sense to me and doesn't work unless npm can detect that My suggestion for the core team is to disable the merging of those settings For everyone else, there are two options:
|
pnpm version: 6.24.0
Code to reproduce the issue:
windows command line execute the
pnpm install
Expected behavior:
install packages
Actual behavior:
show error `ERR_PNPM_INVALID_OVERRIDE_SELECTOR Cannot parse the "//" selector in the override'
Additional information:
node -v
prints: 14.18.1The text was updated successfully, but these errors were encountered: