Kibana Source Installation gives error on npm install

I am trying to write a plugin for Kibana 5.4.2 . I forked and cloned the source code by git clone and having an error when I run npm start. I also installed the latest node. But still the same. Following are the content in npm-debug.log file.

Thanks in advance

10005 silly mapToRegistry uri https://registry.npmjs.org/kind-of
10006 silly cache add parsed spec Result {
10006 silly cache add raw: 'is-number@^3.0.0',
10006 silly cache add scope: null,
10006 silly cache add escapedName: 'is-number',
10006 silly cache add name: 'is-number',
10006 silly cache add rawSpec: '^3.0.0',
10006 silly cache add spec: '>=3.0.0 <4.0.0',
10006 silly cache add type: 'range' }
10007 silly addNamed is-number@>=3.0.0 <4.0.0
10008 verbose addNamed ">=3.0.0 <4.0.0" is a valid semver range for is-number
10009 silly addNameRange { name: 'is-number', range: '>=3.0.0 <4.0.0', hasData: false }

19911 error argv "D:\kibana-11-30\kibana\node.exe" "D:\kibana-11-30\kibana\node_modules\npm\bin\npm-cli.js" "install"
19912 error node v6.11.1
19913 error npm v3.10.10
19914 error code EACCES
19915 error errno EACCES
19916 error syscall connect
19917 error Error: connect EACCES 151.101.140.162:443
19917 error at Object.exports._errnoException (util.js:1018:11)
19917 error at exports._exceptionWithHostPort (util.js:1041:20)
19917 error at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)
19917 error { Error: connect EACCES 151.101.140.162:443
19917 error at Object.exports._errnoException (util.js:1018:11)
19917 error at exports._exceptionWithHostPort (util.js:1041:20)
19917 error at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)
19917 error code: 'EACCES',
19917 error errno: 'EACCES',
19917 error syscall: 'connect',
19917 error address: '151.101.140.162',
19917 error port: 443,
19917 error parent: 'postcss-modules-extract-imports' }
19918 error Please try running this command again as root/Administrator.
19919 verbose exit [ 1, true ]

Hello, can you try running npm install again?
It could be that the npm registry was having trouble with connectivity.

still having error.
how can i upload npm-debug.log file here?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.