NES/npm-debug.log at master · sripat/NES · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files (x86)\\nodejs\\\\node.exe',
1 verbose cli   'C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'install',
1 verbose cli   '-g',
1 verbose cli   'nodemon' ]
2 info using npm@1.4.21
3 info using node@v0.10.30
4 verbose node symlink C:\Program Files (x86)\nodejs\\node.exe
5 verbose cache add [ 'nodemon', null ]
6 verbose cache add name=undefined spec="nodemon" args=["nodemon",null]
7 verbose parsed url { protocol: null,
7 verbose parsed url   slashes: null,
7 verbose parsed url   auth: null,
7 verbose parsed url   host: null,
7 verbose parsed url   port: null,
7 verbose parsed url   hostname: null,
7 verbose parsed url   hash: null,
7 verbose parsed url   search: null,
7 verbose parsed url   query: null,
7 verbose parsed url   pathname: 'nodemon',
7 verbose parsed url   path: 'nodemon',
7 verbose parsed url   href: 'nodemon' }
8 silly lockFile 1625b929-nodemon nodemon
9 verbose lock nodemon C:\Users\sripat\AppData\Roaming\npm-cache\1625b929-nodemon.lock
10 silly lockFile 1625b929-nodemon nodemon
11 silly lockFile 1625b929-nodemon nodemon
12 verbose addNamed [ 'nodemon', '' ]
13 verbose addNamed [ null, '*' ]
14 silly lockFile 4f5e51c6-nodemon nodemon@
15 verbose lock nodemon@ C:\Users\sripat\AppData\Roaming\npm-cache\4f5e51c6-nodemon.lock
16 silly addNameRange { name: 'nodemon', range: '*', hasData: false }
17 verbose request where is /nodemon
18 verbose request registry https://registry.npmjs.org/
19 verbose request id 5e8b085e394b8570
20 verbose url raw /nodemon
21 verbose url resolving [ 'https://registry.npmjs.org/', './nodemon' ]
22 verbose url resolved https://registry.npmjs.org/nodemon
23 verbose request where is https://registry.npmjs.org/nodemon
24 info trying registry request attempt 1 at 17:56:48
25 http GET https://registry.npmjs.org/nodemon
26 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND
27 info trying registry request attempt 2 at 17:57:11
28 http GET https://registry.npmjs.org/nodemon
29 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND
30 info trying registry request attempt 3 at 17:58:23
31 http GET https://registry.npmjs.org/nodemon
32 silly lockFile 4f5e51c6-nodemon nodemon@
33 silly lockFile 4f5e51c6-nodemon nodemon@
34 error network connect ETIMEDOUT
34 error network This is most likely not a problem with npm itself
34 error network and is related to network connectivity.
34 error network In most cases you are behind a proxy or have bad network settings.
34 error network
34 error network If you are behind a proxy, please make sure that the
34 error network 'proxy' config is set properly.  See: 'npm help config'
35 error System Windows_NT 6.2.9200
36 error command "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "nodemon"
37 error cwd C:\Users\sripat\express_example
38 error node -v v0.10.30
39 error npm -v 1.4.21
40 error syscall connect
41 error code ETIMEDOUT
42 error errno ETIMEDOUT
43 verbose exit [ 1, true ]