Webpack-cli: Sub depencency probably removed. Install fails.

[JonWallsten]

I'm trying to update webpack-cli from 2.0.9 -> 2.0.10.
PS C:\Users\me\repo\web-app-angular> npm install webpack webpack-cli
npm ERR! code E404
npm ERR! 404 Not Found: @sindresorhus/is@^0.7.0

npm i @sindresorhus/is
npm ERR! code E404
npm ERR! 404 Not Found: @sindresorhus/is@latest

Can someone else check if it's actually missing or if "it doesn't work on my machine"

[evenstensberg]

Can you print the entire stack trace which is not (if) confidential?

[dhruvdutt]

Can you print full error log or maybe link the repo? It is unclear from this what is happening.

[JonWallsten]

Sure, hang on!

[montogeek]

Post your package.json as well please

[evenstensberg]

Not needed, stack trace is enough

[montogeek]

2.0.9 does not exists, neither 2.0.10.
But they will later today https://github.com/webpack/webpack-cli/issues/310

[JonWallsten]

It's just the git tags missing, not the packages I assume?

[dhruvdutt]

GitHub tags don't matter. The latest version (2.0.10) is published on npm registry 4 days ago. That's the source from where npm/yarn picks up packages.

[JonWallsten]

I am however stuck on this now:

fetchMetadata: sill resolveWithNewModule [email protected] checking installable status

Something is fishy

Our network is probably shaky. If it works for you guys it's definitely just a problem here. So if someone can confirm that it works, they can close this.

[dhruvdutt]

It would be very convenient to debug if you can make a small zip with minimal things or list steps to reproduce this issue.

[JonWallsten]

It doesn't work for my colleague either. So I guess it's our network and/or artifactory. I've tried against both registry.npmjs.org with proxy and our internal artifactory without proxy. I have installed a lot of other modules. Might be a coincident that it was this package that fails. I'll let you guys now as soon as I get home so I can try it outside of the company network.

[dhruvdutt]

You can try switching to mirrors of npm registry and see which works for you.
You can ping the mirrors to check and switch to it inside your npm config.

[JonWallsten]

Edit:
2.0.10

npm install [email protected]
[..................] \ fetchMetadata: sill resolveWithNewModule [email protected] checking installable status

2.0.9

npm install [email protected]
npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info.
npm WARN deprecated [email protected]: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\style-loader-e5910acc\lib\addStyles.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\style-loader-e5910acc\lib\addStyleUrl.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\style-loader-e5910acc\lib\urls.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\tslint-eslint-rules-273e3fcd\dist\readme\fetch.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\cross-spawn-1ffcdd71\lib\util\escapeArgument.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\cross-spawn-1ffcdd71\lib\util\escapeCommand.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\tslint-eslint-rules-273e3fcd\dist\readme\index.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\cross-spawn-1ffcdd71\lib\util\hasEmptyArgumentBug.js
'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\cross-spawn-1ffcdd71\lib\util\readShebang.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\tslint-eslint-rules-273e3fcd\dist\readme\rules.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\cross-spawn-1ffcdd71\lib\util\resolveCommand.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\ajv-keywords-630285a4\keywords\dot\_formatLimit.jst'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\ajv-keywords-630285a4\keywords\dot\patternRequired.j
st'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\ajv-keywords-630285a4\keywords\dot\switch.jst'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\me\repo\web-app-angular\node_modules\.staging\acorn-ac4fa0ad\src\bin\acorn.js'
npm ERR! code E404
npm ERR! 404 Object Not Found: @ngtools/[email protected]

[dhruvdutt]

Make sure you're using public mirrors. Use the ones listed in the official npm docs and not any other private ones which might need authorization.

Double check which is currently active npm config get registry.

You can always do ping registry.npmjs.org or ping skimdb.npmjs.com to check which responds for your network.

If all of this doesn't work then most likely there's some issue specific to your network which might be blocking it. Can you confirm if this is only happening with webpack-cli or all npm packages?

[JonWallsten]

It's seems rather random. I'll go ahead and close this. It's obviously our network. Probably a coincidence that it pointed to webpack-cli.

[JonWallsten]

@ev1stensberg
FYI: after removing package-lock.json I got stuck on a different package. And after a while I finally got an error message:

npm ERR! Error while executing:
npm ERR! C:\Users\jway52\AppData\Local\Programs\Git\cmd\git.EXE ls-remote -h -t ssh://[email protected]/ev1stensberg/generator.git
npm ERR!
npm ERR! ssh: connect to host github.com port 22: Connection timed out
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128 

And with yarn:
error An unexpected error occurred: "https://github.com/ev1stensberg/generator: connect ETIMEDOUT 192.30.253.112:443".

[JonWallsten]

So I guess the upgrade to 2.0.10 was the issue after all:
https://github.com/webpack/webpack-cli/commit/514a695be2fcd0b5502f48ab7694293de3c148c5
Is it possible to add the this without messing up for us behind corp firewalls?
`"yeoman-generator": "github:ev1stensberg/generator#Feature-getArgument"´

[dhruvdutt]

@JonWallsten I'm not sure if this would help but can you add --verbose flag while installing webpack-cli and show the output?

Seems like this issue is happening only when behind a proxy, and we might need to publish the fork on npm separately or remove the fork entirely. Related issue #161

[JonWallsten]

I actually solved it a few moments ago.
The proxy I added in the _global git config_ didn't help. Not the proxy in the _.npmrc_ file either.
What did work however was to add _http_proxy_ and _https_proxy_ as system variables on my local machine. I guess running _git_ through _npm_ happens to slip in between proxy settings.

[dhruvdutt]

Interesting. What did you set in http_proxy and https_proxy system variables?

Also, can you please close this issue for now? We're already discussing the proxy and fork issue at #161.

[JonWallsten]

Our corporate proxy servers. I'm just baffled it didn't work with both .npmrc and git config already using them. They are also set under my LAN settings. Still I had to set as system variables. Seems a bit redundant!

[lgallindo]

I'm getting a similar error today (error that wasn't there last week), how can I check the availability of a package@version in a mirror by hand (without npm) to check if the error is in my end somehow?

[evenstensberg]

Could you link the stack trace you're getting?

[lgallindo]

Ok, I'm on Windows 8.1, just reinstalled the latest nodejs from the official site.

C:\>npm --version
5.6.0
C:\>npm ls
C:\
`-- (empty)
c:\npm view connect
npm ERR! code E404
npm ERR! 404 Not Found: connect
npm ERR! 404
npm ERR! 404  'connect' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)

npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\******\AppData\Roaming\npm-cache\_logs\2018-05-07T18_40_26_578Z-debug.log

This happens for any package, and also for the "install" command. At first I was trying to install webpack-cli.

[evenstensberg]

I don't think this is related to webpack-cli. We don't have a dependency named connect, how does your package.json look?