npm ERR! notarget No matching version found for statuses@^2.0.0 when npm install
See original GitHub issueDescribe the bug
Running npm install msw --save-dev
on Windows 10 produces the following error:
npm ERR! code ETARGET
npm ERR! notarget No matching version found for statuses@^2.0.0.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'msw'
npm ERR! notarget
Environment
nodejs: v14.16.0
npm: 6.14.11
To Reproduce
Steps to reproduce the behavior:
- Run
npm install msw --save-dev
- See error
Expected behavior
msw
is successfully installed
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Npm Error - No matching version found for - Stack Overflow
Try removing package-lock.json and running npm install && npm update , it'll install the latest version and clear all errors.
Read more >Can't install with NPM (No matching version found for @nlpjs ...
So I guess that is a new bug. Describe the bug. When I try to install library takes this error: $ npm i...
Read more >No matching version found for [Error LoopBack Solved]
npm WARN config cache-min This option has been deprecated in favor of '--prefer-offline'. npm ERR ! code ETARGET npm ERR ! notarget No...
Read more >Npm "No matching version found" - Nexus Repository Manager
Once again, I am getting an error when I attempt install an npm package with NXRM npm-group that is configured as registry in...
Read more >How to fix npm ERR! code ETARGET issue - Nathan Sebhastian
The error ETARGET means that npm can't find a package version that matches your requirements as defined in the package.json file. In the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like you have a custom NPM registry configured. I suspect that to be a culprit in some way.
I may suggest setting the default registry and trying to install MSW:
We need to take the custom registry out to effectively triage if it’s the reason.
The
statuses
package is correctly specified as MSW’s dependency, including its range version that’s published to NPM. The issue is likely on your side with the custom registry you’re using. Check how it works, any sorts of whitelists and permissions. I’m afraid I don’t see an issue on the library’s side to fix.@kettanaito I ran
npm config list
and below is the response. Can you help double check this for me?A little more background on my project. It is in React/Typescript, and I use Visual Studio for development.
Thank you for your help!