-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[BUG] npm install fails on scoped package override with cryptic "Invalid comparator" error #5955
Comments
This may well be related to #5843 but I'm guessing it is distinct in that this one has nothing to do with file paths. |
It seems that this issue is quite fresh, because I started to get it only few days ago too. What is the latest version without this issue, it would be very helpful because it literally stops me from building my project now :( |
Here's a simple reproduction. I used different versions of react and react-dom to force a ERESOLVE. react-keyed-flatten-children has a devDependnecy on react
And the full stack trace from the debug log.
npm 8 installs the package fine. |
Same here. NPM 8 works fine. I added a reproduction here: #5843 (comment) |
FYI, #5843 was fixed in v9.3.0 and v9.3.0 has fixed this issue for us as well. |
For me, with v9.3.0 and v9.3.1,
... instead of the I tried
... where note that |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
We have a package override in our project that's working OK in NPM 8 (after some workarounds for #5007):
Upgrading npm to 9.1.1 or 9.2.0 makes
npm install
fail in this project, with:and in the debug logfile:
Expected Behavior
I expect
npm install
to succeed with NPM 9 like it does with NPM 8 (or else output a more informative error message, if there is something wrong with the package override that NPM 8 was not revealing).Steps To Reproduce
I would extract minimal steps to reproduce this, except, I put in that work in #5007 and that's been totally ignored for half year. I'll happily put in the work here if there's a hint that someone cares for it. :)
Environment
The text was updated successfully, but these errors were encountered: