npm install gives error

[GaneshShetty951]

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'bluebird',
1 verbose cli '--save' ]
2 info using npm@3.10.3
3 info using node@v6.7.0
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData bluebird
8 silly fetchNamedPackageData bluebird
9 silly mapToRegistry name bluebird
10 silly mapToRegistry using default registry
11 silly mapToRegistry registry https://registry.npmjs.org/
12 silly mapToRegistry data Result {
12 silly mapToRegistry raw: 'bluebird',
12 silly mapToRegistry scope: null,
12 silly mapToRegistry escapedName: 'bluebird',
12 silly mapToRegistry name: 'bluebird',
12 silly mapToRegistry rawSpec: '',
12 silly mapToRegistry spec: 'latest',
12 silly mapToRegistry type: 'tag' }
13 silly mapToRegistry uri https://registry.npmjs.org/bluebird
14 verbose request uri https://registry.npmjs.org/bluebird
15 verbose request no auth needed
16 info attempt registry request try #1 at 7:09:54 PM
17 verbose request id c420c7efbbd5c9c5
18 http request GET https://registry.npmjs.org/bluebird
19 info retry will retry, error on last attempt: Error: unable to verify the first certificate
20 info attempt registry request try #2 at 7:10:05 PM
21 http request GET https://registry.npmjs.org/bluebird
22 info retry will retry, error on last attempt: Error: unable to verify the first certificate
23 info attempt registry request try #3 at 7:11:06 PM
24 http request GET https://registry.npmjs.org/bluebird
25 silly fetchPackageMetaData Error: unable to verify the first certificate
25 silly fetchPackageMetaData at Error (native)
25 silly fetchPackageMetaData at TLSSocket. (_tls_wrap.js:1060:38)
25 silly fetchPackageMetaData at emitNone (events.js:86:13)
25 silly fetchPackageMetaData at TLSSocket.emit (events.js:185:7)
25 silly fetchPackageMetaData at TLSSocket._finishInit (_tls_wrap.js:584:8)
25 silly fetchPackageMetaData at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:416:38)
25 silly fetchPackageMetaData error for bluebird { Error: unable to verify the first certificate
25 silly fetchPackageMetaData at Error (native)
25 silly fetchPackageMetaData at TLSSocket. (_tls_wrap.js:1060:38)
25 silly fetchPackageMetaData at emitNone (events.js:86:13)
25 silly fetchPackageMetaData at TLSSocket.emit (events.js:185:7)
25 silly fetchPackageMetaData at TLSSocket._finishInit (_tls_wrap.js:584:8)
25 silly fetchPackageMetaData at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:416:38) code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE' }
26 silly rollbackFailedOptional Starting
27 silly rollbackFailedOptional Finishing
28 silly runTopLevelLifecycles Starting
29 silly runTopLevelLifecycles Finishing
30 silly install printInstalled
31 verbose stack Error: unable to verify the first certificate
31 verbose stack at Error (native)
31 verbose stack at TLSSocket. (_tls_wrap.js:1060:38)
31 verbose stack at emitNone (events.js:86:13)
31 verbose stack at TLSSocket.emit (events.js:185:7)
31 verbose stack at TLSSocket._finishInit (_tls_wrap.js:584:8)
31 verbose stack at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:416:38)
32 verbose cwd C:\Users\Ganesh Shetty\Desktop\ionic-projects-demo-master
33 error Windows_NT 10.0.14393
34 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "bluebird" "--save"
35 error node v6.7.0
36 error npm v3.10.3
37 error code UNABLE_TO_VERIFY_LEAF_SIGNATURE
38 error unable to verify the first certificate
39 error If you need help, you may report this error at:
39 error https://github.com/npm/npm/issues
40 verbose exit [ 1, true ]

[GaneshShetty951]

[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.