[BUG] <title> report 'no matching version found' error during second npm install #7138
Closed
2 tasks done
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 9.x
work is associated with a specific npm 9 release
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
the package.json content of my project:
the package.json content of package "B":
However, A1@4.9.5-r6 is non-existent and I accidentally added it.
The package-lock.json file in my project does not contain information about A@4.9.5-r6.
Information about other packages exists, that is "A": "file:./deps/A1@4.9.5-r3.tgz'、"commander": "^9.3.0"、"fs-extra": "^10.1.0"、"json5": "^2.2.3"、"source-map": "0.7.4".
Operation commands and symptoms:
When I run the npm install command for the first time, no error is reported. A1@4.9.5-r3.tgz is successfully installed, but A1@4.9.5-r6 is not successfully installed.
When I run the npm install command for the second time, the following error information is displayed: error notarget No matching version found for A1@4.9.5-r6.
Expected Behavior
When I run npm install for the first time, the error message "error notarget No match version found'A1@4.9.5-r6'" is displayed.
More importantly, I want to know why no error is reported when npm install is executed for the first time, and the error is reported for the second time.
Steps To Reproduce
Environment
'
strict-ssl=false
package-lock=true
'
; copy and paste output from `npm config ls` here
The text was updated successfully, but these errors were encountered: