（Win7的），我作爲管理員 我做在C的目錄中打開命令窗口：\程序文件（x86）\的NodeJS 我導航通過CD C命令窗口：\程序文件（x86）\的NodeJS
我跑命令 NPM安裝連接
響應： [絕密]> NPM -g安裝連接 NPM ERR！ Windows_NT 6.1.7601 npm ERR！ argv「[redacted] \ node_modules \ npm \ bin \ npm-cli.js」「-g」「install」「connect」 npm ERR！節點v0.12.7 npm ERR！ npm v2.11.3 npm ERR！代碼ETIMEDOUT npm ERR！ errno ETIMEDOUT npm ERR！系統調用連接
npm ERR! network connect ETIMEDOUT
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR! [redacted]\npm-debug.log
我跑 NPM配置編輯 我改變了屬性行，以消除在每個這些行的開始時的分號。
同樣，我跑 NPM -g安裝連接
相同的結果。日誌文件有這個：
0 info it worked if it ends with ok
1 verbose cli [ ' [redacted]\\\\node.exe',
1 verbose cli ' [redacted]\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli '-g',
1 verbose cli 'install',
1 verbose cli 'connect' ]
2 info using [email protected]
3 info using [email protected]
4 verbose install initial load of [redacted]\package.json
5 verbose readDependencies loading dependencies from [redacted]\package.json
6 silly cache add args [ 'connect', null ]
7 verbose cache add spec connect
8 silly cache add parsed spec { raw: 'connect',
8 silly cache add scope: null,
8 silly cache add name: 'connect',
8 silly cache add rawSpec: '',
8 silly cache add spec: '*',
8 silly cache add type: 'range' }
9 silly addNamed [email protected]*
10 verbose addNamed "*" is a valid semver range for connect
11 silly addNameRange { name: 'connect', range: '*', hasData: false }
12 silly mapToRegistry name connect
13 silly mapToRegistry using default registry
14 silly mapToRegistry registry ht tps://registry.npmjs.org/
15 silly mapToRegistry uri ht tps://registry.npmjs.org/connect
16 verbose addNameRange registry:ht tps://registry.npmjs.org/connect not in flight; fetching
17 verbose request uri https://registry.npmjs.org/connect
18 verbose request no auth needed
19 info attempt registry request try #1 at 12:36:52 PM
20 verbose request id 3524fc7ca91c73dc
21 http request GET https://registry.npmjs.org/connect
22 info retry will retry, error on last attempt: Error: connect ETIMEDOUT
23 info attempt registry request try #2 at 12:37:26 PM
24 http request GET https://registry.npmjs.org/connect
25 info retry will retry, error on last attempt: Error: connect ETIMEDOUT
26 info attempt registry request try #3 at 12:38:50 PM
27 http request GET https://registry.npmjs.org/connect
28 verbose stack Error: connect ETIMEDOUT
28 verbose stack at exports._errnoException (util.js:746:11)
28 verbose stack at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)
29 verbose cwd [redacted]
30 error Windows_NT 6.1.7601
31 error argv "[redacted]\\node_modules\\npm\\bin\\npm-cli.js" "-g" "install" "connect"
32 error node v0.12.7
33 error npm v2.11.3
34 error code ETIMEDOUT
35 error errno ETIMEDOUT
36 error syscall connect
37 error network connect ETIMEDOUT
37 error network This is most likely not a problem with npm itself
37 error network and is related to network connectivity.
37 error network In most cases you are behind a proxy or have bad network settings.
37 error network
37 error network If you are behind a proxy, please make sure that the
37 error network 'proxy' config is set properly. See: 'npm help config'
38 verbose exit [ 1, true ]
我想我只會使用IIS Express。這數百文件做的事簡單就是超越我。
來源
2015-07-23 16:56:54
sef
啊哈，我陷入了困境。謝謝。 – Architek1 2013-03-12 02:24:08
它在package.json中添加explcit依賴項後運行，並在實際下載連接包到本地時運行npm update。 感謝您的提示 – rahul 2014-01-29 01:26:36
如果您使用Express，它建立在Connect之上，那麼您應該使用Express來啓動服務器。如果您直接使用Connect，那麼Express用於什麼目的？第二臺服務器？ – 2014-01-29 01:30:32