Skip to main content
Fixed the weird syntax highlighting (as a result, the diff looks more extensive than it really is - use view "Side-by-side Markdown" to compare), etc.
Source Link
Peter Mortensen
  • 31.4k
  • 22
  • 110
  • 134

If you're using a VPNVPN it will fail. In my case it said:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for loader-utils@^2.0.4.
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! A complete log of this run can be found in: ...
npm ERR! code ETARGET
npm ERR! notarget No matching version found for loader-utils@^2.0.4.
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! A complete log of this run can be found in: ...

Needless to say, I tried everything until I started doubting my life, career and everything in between, and then gave the "it's a network issue" try with 0 confidence.

And it worked.

If you're using a VPN it will fail. In my case it said:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for loader-utils@^2.0.4.
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! A complete log of this run can be found in: ...

Needless to say I tried everything until I started doubting my life, career and everything in between, and then gave the "it's a network issue" try with 0 confidence.

And it worked.

If you're using a VPN it will fail. In my case it said:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for loader-utils@^2.0.4.
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! A complete log of this run can be found in: ...

Needless to say, I tried everything until I started doubting my life, career and everything in between, and then gave the "it's a network issue" try with 0 confidence.

And it worked.

Source Link
Marghen
  • 716
  • 6
  • 14

If you're using a VPN it will fail. In my case it said:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for loader-utils@^2.0.4.
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! A complete log of this run can be found in: ...

Needless to say I tried everything until I started doubting my life, career and everything in between, and then gave the "it's a network issue" try with 0 confidence.

And it worked.