You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to install a package that doesn't exist, then an Error at https://github.com/npm/npm-pick-manifest/blob/main/lib/index.js#L213 throws an exception where it cannot convert undefined or null to an object, causing the actual npm install error to be hidden away. I was able to figure out what the error actually was by modifying the source, but I'm guessing this is a deeper level issue than just slapping in a || {} and calling it a day.
Expected Behavior
The error saying the package or version doesn't exist to properly throw rather than an internal error
Steps To Reproduce
run npm install this-package-does-not-exist-at-all (or any other package that doesn't exist. For me, it was validate-any@1.3.2)
Environment
npm: 9.2.0
Node: 18.6.0
OS: Windows 11
platform: custom build pc (x86)
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
When attempting to install a package that doesn't exist, then an Error at https://github.com/npm/npm-pick-manifest/blob/main/lib/index.js#L213 throws an exception where it cannot convert undefined or null to an object, causing the actual npm install error to be hidden away. I was able to figure out what the error actually was by modifying the source, but I'm guessing this is a deeper level issue than just slapping in a || {} and calling it a day.
Expected Behavior
The error saying the package or version doesn't exist to properly throw rather than an internal error
Steps To Reproduce
Environment
The text was updated successfully, but these errors were encountered: