错误:找不到模块“连接”

看来,这个简单的应用程序无法find'connect'模块后,我只是把它安装在文件目录中。

 var connect = require ('connect'); connect.createServer(function(res, req, next) { res.simpleBody("Connect you son of a beeeeetch"); }).listen(8000); express@3.1.0 node_modules/express ├── methods@0.0.1 ├── fresh@0.1.0 ├── range-parser@0.0.4 ├── cookie-signature@0.0.1 ├── buffer-crc32@0.1.1 ├── cookie@0.0.5 ├── debug@0.7.2 ├── commander@0.6.1 ├── mkdirp@0.3.3 ├── send@0.1.0 (mime@1.2.6) └── connect@2.7.2 (pause@0.0.1, bytes@0.1.0, formidable@1.0.11, qs@0.5.1) Dzs-Mac-Attax-2:PlsWrk Dz$ node test.js module.js:340 throw err; ^ Error: Cannot find module 'connect' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:362:17) at require (module.js:378:17) at Object.<anonymous> (/Users/Dz/Documents/NodeTests/PlsWrk/test.js:1:77) at Module._compile (module.js:449:26) at Object.Module._extensions..js (module.js:467:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.runMain (module.js:492:10) 

       

网上收集的解决方案 "错误:找不到模块“连接”"

Express在内部使用Connect作为其node_modules依赖项之一。

如果你想在你的应用中使用Connect,你需要将它添加到你的package.json并运行npm update

按照devise,每个节点模块都有自己的私有内部依赖关系。

如果你想使用任何,你的应用程序将需要安装它们。

这意味着您的应用程序可以使用不同版本的模块,并且每个模块可以在内部再次使用不同的版本而不会发生冲突。

Connect是Express使用的可扩展的HTTP服务器框架。 特别是Express使用它提供对会话和cookie处理的支持。 源代码在https://github.com/senchalabs/connect&#x7684; github上可用。

一般来说,当一个节点应用程序“无法find”的时候,首先要去https://npmjs.org/package/npm-search并search找不到的东西&#x3002; 没有使用npm,在节点生态系统中很难相处。

在这种情况下,npmsearch会find连接,如果你去https://npmjs.org/package/connect你会发现连接模块的安装说明&#x3002;

在这种情况下 :

 npm install connect npm -g install connect 

为每个用户安装连接模块。

您可能需要成为root用户,或者使用sudo在大多数unix发行版上执行此操作。

或者,你可以添加连接依赖项到你的项目的package.json文件 – 我的看起来像这样:

 "express": "3.x" , "connect": "2.x" 

我还必须使用npm来安装模块buffer-crc32,方法,debugging,新鲜,范围parsing器,cookie签名和cookie来获得工作快速项目。

黑客节点快乐:)

连接模块没有安装或部分安装,所以先安装,然后再尝试启动服务器

  npm install connect 

因为你没有安装它。 你有express安装,不能connect

我有同样的问题。 节点安装到C:\Program Files (x86)\nodejs 。 最初我试图从这个目录安装并运行JavaScript文件,这造成了许多权限问题。

如果你已经把你的服务器放在那个目录下,试着将它移动到另一个目录(可能在Documents ),在你的Node命令提示符下导航,然后再次运行。

这对我来说是非常有用的。

(Win7)我有一个命令窗口以pipe理员身份打开我在C:\ Program Files(x86)\ NodeJS下创build一个目录我通过cd C:\ Program Files(x86)\ NodeJS浏览命令窗口

我运行命令npm install connect

响应:[编辑]> 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 

我跑npmconfiguration编辑我改变了属性线,以消除每个行的开始分号。

我再次运行npm -g install connect

同样的结果。 日志文件有这样的:

 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 npm@2.11.3 3 info using node@v0.12.7 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 connect@* 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。 这几百个文件做一些简单的事情就超越了我。

对于express-http-proxy,我有同样的问题,解决方法是用npm安装包。 起初我全球安装(-g),它的工作原理。 在另一个安装中,我不得不使用“–save-dev”。

 $ gulp module.js:338 throw err; ^ Error: Cannot find module 'express-http-proxy' at Function.Module._resolveFilename (module.js:336:15) at Function.Module._load (module.js:278:25) at Module.require (module.js:365:17) at require (module.js:384:17) at Object.<anonymous> (/var/opt/jet/workspace/node-js-project/lib/authorization-to-context-header.js:1:75) at Module._compile (module.js:460:26) at Object.Module._extensions..js (module.js:478:10) at Module.load (module.js:355:32) at Function.Module._load (module.js:310:12) at Module.require (module.js:365:17) at require (module.js:384:17) 

安装包

 $ npm install express-http-proxy -g express-http-proxy@0.6.0 /opt/jet/nodejs/node-js/lib/node_modules/express-http-proxy âââ type-is@1.6.6 (media-typer@0.3.0, mime-types@2.1.4) âââ raw-body@1.3.4 (bytes@1.0.0, iconv-lite@0.4.8) 

或者如果“-g”不够用

 $ npm install express-http-proxy --save-dev 

吞咽工作

 $ gulp [16:49:17] Using gulpfile /var/opt/workspace/node-js-project/gulpfile.js [16:49:17] Starting 'dev'... [16:49:17] Starting 'clean'... [16:49:17] Finished 'dev' after 9.18 ms [16:49:17] Starting 'default'... [16:49:17] Finished 'default' after 10 μs [16:49:17] Finished 'clean' after 11 ms [16:49:17] Starting 'build'... [16:49:17] Starting 'clean'... [16:49:17] Finished 'clean' after 2.13 ms [16:49:17] Starting 'styles'... [16:49:17] Finished 'styles' after 813 ms ...