NPM proxy repository isn't resolving an artifact(?)

[Timothy Astle]

I've followed the steps here, and everything is working fine.  My .npmrc has the correct registry set and I can install all sorts of packages, except one.

I tried to install node-inspector to debug something.  Below is what I'm seeing.

tastle@TASTLEWS /d/work/OSCAR-js_16.0 (16.0)
$ npm install -g node-inspector
npm WARN optional dep failed, continuing default-b...@1.0.2
|


> w...@0.4.32 install C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

/
C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws>node "c:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.targets(146,5): error MSB6006: "CL.exe" exited with code -1073741515. [C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws\build\bufferutil.vcxproj]le\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws\build\bufferutil.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(297,5): warning MSB8003: Could not find WindowsSDKDir variable from the registry.  TargetFrameworkVersion or PlatformToolset may be set to an invalid version number. [C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws\build\validation.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.targets(146,5): error MSB6006: "CL.exe" exited with code -1073741515. [C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws\build\validation.vcxproj]
npm WARN engine xmlbu...@2.2.1: wanted: {"node":"0.8.x || 0.10.x"} (current: {"node":"0.12.0","npm":"2.5.1"})
npm ERR! fetch failed http://nexus.caris.priv/nexus/content/groups/npm-all/nan/-/nan-1.7.0.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404


> v8-pr...@5.2.4 install C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\v8-profiler
> node-pre-gyp install --fallback-to-build

[v8-profiler] Success: "C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\v8-profiler\build\profiler\v5.2.4\node-v14-win32-x64\profiler.node" is installed via remote
npm ERR! fetch failed http://nexus.caris.priv/nexus/content/groups/npm-all/nan/-/nan-1.7.0.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm ERR! fetch failed http://nexus.caris.priv/nexus/content/groups/npm-all/nan/-/nan-1.7.0.tgz
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "node-inspector"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1

npm ERR! fetch failed with status code 404
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     d:\work\OSCAR-js_16.0\npm-debug.log

If I remove the registry mapping, it installs.

$ npm install -g node-inspector
npm WARN optional dep failed, continuing default-b...@1.0.2
|


> w...@0.4.32 install C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

/
C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws>node "c:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(297,5): warning MSB8003: Could not find WindowsSDKDir variable from the registry.  TargetFrameworkVersion or PlatformToolset may be set to an invalid version number. [C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws\build\bufferutil.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.targets(146,5): error MSB6006: "CL.exe" exited with code -1073741515. [C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws\build\bufferutil.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(297,5): warning MSB8003: Could not find WindowsSDKDir variable from the registry.  TargetFrameworkVersion or PlatformToolset may be set to an invalid version number. [C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws\build\validation.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.targets(146,5): error MSB6006: "CL.exe" exited with code -1073741515. [C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\ws\build\validation.vcxproj]
npm WARN engine xmlbu...@2.2.1: wanted: {"node":"0.8.x || 0.10.x"} (current: {"node":"0.12.0","npm":"2.5.1"})
/
> v8-pr...@5.2.4 install C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\v8-profiler
> node-pre-gyp install --fallback-to-build

[v8-profiler] Success: "C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\v8-profiler\build\profiler\v5.2.4\node-v14-win32-x64\profiler.node" is installed via remote

> v8-d...@0.4.2 install C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\v8-debug
> node-pre-gyp install --fallback-to-build

[v8-debug] Success: "C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\node_modules\v8-debug\build\debug\v0.4.2\node-v14-win32-x64\debug.node" is installed via remote
C:\Users\tastle\AppData\Roaming\npm\node-inspector -> C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\bin\inspector.js
C:\Users\tastle\AppData\Roaming\npm\node-debug -> C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector\bin\node-debug.js
node-in...@0.9.2 C:\Users\tastle\AppData\Roaming\npm\node_modules\node-inspector
├── wh...@1.0.9
├── as...@0.9.0
├── de...@1.0.4 (m...@0.6.2)
├── sem...@3.0.1
├── strong-...@0.1.1 (trun...@1.0.4)
├── r...@0.5.5 (strip-jso...@0.1.3, deep-...@0.2.11, i...@1.3.3, mini...@0.0.10)
├── ya...@1.3.3
├── serve-...@2.2.0 (m...@0.7.0, fr...@0.2.4, pars...@1.3.0, et...@1.5.1)
├── gl...@4.5.3 (inhe...@2.0.1, infl...@1.0.4, on...@1.3.1, mini...@2.0.4)
├── exp...@4.12.3 (merge-de...@1.0.0, met...@1.1.1, fr...@0.2.4, range-...@1.0.2, utils...@1.0.0, cookie-s...@1.0.6, escap...@1.0.1, coo...@0.1.2, conten...@1.0.1, va...@1.0.0, pars...@1.3.0, finalh...@0.3.4, serve-...@1.9.2, content-d...@0.5.0, path-to...@0.1.3, de...@1.0.0, q...@2.4.1, de...@2.1.3, on-fi...@2.2.0, et...@1.5.1, se...@0.12.2, proxy-addr@1.0.
7, typ...@1.6.1, acc...@1.2.5)
├── w...@0.4.32 (comm...@2.1.0, opt...@0.0.6, tiny...@0.0.1, n...@1.0.0)
├── biased...@0.2.4 (ope...@1.4.1, mini...@1.1.0, x-defaul...@0.3.0, browser-...@0.4.4)
├── v8-pr...@5.2.4 (n...@1.5.3)
└── v8-d...@0.4.2 (n...@1.7.0)

Is this a problem with Nexus v. 2.11.1.-01?  I peeked at the 2.11.2 release notes and nothing stuck me that could be related.

Cheers,

--

Tim Astle

[Rich Seddon]

I'll need to see your logs.

Can you attach a support bundle and send it to sup...@sonatype.com?  You can create this under "administration/support tools/support zip" in the UI.

Regards,

Rich

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/551D5BEE.7070404%40caris.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

[Timothy Astle]

Rich gave me a tip to sort out my problem.  He recommended that I clear my npmjs proxy's cache.

"To clear the cache right click on the npmjs repository and run "expire cache"."

Thanks!

Tim