Private package hosted on npm not installing after npm cache clean.

[oberoivarun]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

After npm cache clean i cannot install my own private package (Hosted in npm registry using private modules). I have to increase the package version and publish again. Then i can install it.

####Npm should:
Check the cache if the package is available. If not, then it should check the registry and download the package.

How can the CLI team reproduce the problem?

Publish a private package, do npm cache clean and then try install the package.

supporting information:

• npm -v prints: 3.10.10
• node -v prints: 6.10.1
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: Windows 10, 64bit
• Network issues:
  • Geographic location where npm was run: Delhi, India
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
  • I use a normal internet connection. Everything else works fine. Speed is good.

npm debug log

1094 verbose stack Error: Error extracting C:\Users\varun\AppData\Roaming\npm-cache\@notanerddev\slack-services\1.0.37\package.tgz archive: ENOENT: no such file or directory, open 'C:\Users\varun\AppData\Roaming\npm-cache\@notanerddev\slack-services\1.0.37\package.tgz'
1094 verbose stack     at ReadStream.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\fetch-package-metadata.js:309:10)
1094 verbose stack     at emitOne (events.js:96:13)
1094 verbose stack     at ReadStream.emit (events.js:188:7)
1094 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:190:14
1094 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:241:16
1094 verbose stack     at FSReqWrap.oncomplete (fs.js:123:15)
1095 verbose cwd C:\Users\varun\Desktop\Code\slack\leader
1096 error Windows_NT 10.0.14393
1097 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
1098 error node v6.10.1
1099 error npm  v3.10.10
1100 error code EREADFILE
1101 error Error extracting C:\Users\varun\AppData\Roaming\npm-cache\@notanerddev\slack-services\1.0.37\package.tgz archive: ENOENT: no such file or directory, open 'C:\Users\varun\AppData\Roaming\npm-cache\@notanerddev\slack-services\1.0.37\package.tgz'
1102 error If you need help, you may report this error at:
1102 error     <https://github.com/npm/npm/issues>
1103 verbose exit [ 1, true ]

[npm-robot]

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.