Node.js 全局安装NPM包时行为不一致

我正试图在Ubuntu（12.04）上安装NPM软件包。我已经通过安装了Node.js和NPM

我正在尝试将部署到我的服务器。我已从GitHub克隆了应用程序，然后尝试以根用户身份安装应用程序依赖项：

root@dev:/web/my-application# npm install -g
npm http GET https://registry.npmjs.org/mongoose/2.5.11
npm http GET https://registry.npmjs.org/express/2.5.0
npm http GET https://registry.npmjs.org/ejs/0.6.1
npm http GET https://registry.npmjs.org/config/0.4.11
npm http GET https://registry.npmjs.org/async/0.1.18
npm http GET https://registry.npmjs.org/socket.io/0.9.2
npm http 304 https://registry.npmjs.org/ejs/0.6.1
npm http 304 https://registry.npmjs.org/async/0.1.18
npm http 304 https://registry.npmjs.org/mongoose/2.5.11
npm http 304 https://registry.npmjs.org/express/2.5.0
npm http 304 https://registry.npmjs.org/config/0.4.11
npm http 304 https://registry.npmjs.org/socket.io/0.9.2
npm http GET https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/connect
npm http GET https://registry.npmjs.org/mkdirp/0.0.7
npm http GET https://registry.npmjs.org/qs
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/redis/0.6.7
npm http GET https://registry.npmjs.org/socket.io-client/0.9.2
npm http GET https://registry.npmjs.org/yaml
npm http GET https://registry.npmjs.org/vows
npm http GET https://registry.npmjs.org/coffee-script
npm http GET https://registry.npmjs.org/hooks/0.2.0
npm http GET https://registry.npmjs.org/mongodb/0.9.9-5
npm http 304 https://registry.npmjs.org/mime
npm http 304 https://registry.npmjs.org/connect
npm http 304 https://registry.npmjs.org/mkdirp/0.0.7
npm http 304 https://registry.npmjs.org/qs
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/redis/0.6.7
npm http 304 https://registry.npmjs.org/socket.io-client/0.9.2
npm http 304 https://registry.npmjs.org/vows
npm http 304 https://registry.npmjs.org/yaml
npm http 304 https://registry.npmjs.org/coffee-script
npm http 304 https://registry.npmjs.org/hooks/0.2.0
npm http 304 https://registry.npmjs.org/mongodb/0.9.9-5
npm http GET https://registry.npmjs.org/eyes

> mongodb@0.9.9-5 install /usr/lib/node_modules/node-uptime/node_modules/mongoose/node_modules/mongodb
> node install.js

npm http 304 https://registry.npmjs.org/eyes
================================================================================
=                                                                              =
=  To install with C++ bson parser do <npm install mongodb --mongodb:native>   =
=                                                                              =
================================================================================
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/xmlhttprequest/1.2.2
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.2.2
npm http 304 https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/zeparser/0.0.5
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/commander

> ws@0.4.16 install /usr/lib/node_modules/node-uptime/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> node install.js

================================================================================
=                                                                              =
=  To install WS with blazing fast native extensions, use                      =
=       <npm install ws --ws:native>                                           =
=                                                                              =
================================================================================
node-uptime@1.2.0 /usr/lib/node_modules/node-uptime
├── async@0.1.18
├── ejs@0.6.1
├── express@2.5.0 (mkdirp@0.0.7, mime@1.2.5, qs@0.5.0, connect@1.7.3)
├── mongoose@2.5.11 (hooks@0.2.0, mongodb@0.9.9-5)
├── config@0.4.11 (yaml@0.2.3, coffee-script@1.3.3, vows@0.5.13)
└── socket.io@0.9.2 (policyfile@0.0.4, redis@0.6.7, socket.io-client@0.9.2)

据我所知（如果我错了，请纠正我），在全局安装包时，NPM尊重

NODE\u PATH

环境变量。有趣的是，如果您查看上面的软件包安装输出，您可以看到NPM将依赖软件包全局安装到

/usr/lib/node_modules

中。如果我仔细检查

NODE\u PATH

环境变量，结果表明

NODE\u PATH

变量的设置不同：

root@dev:/web/my-application# echo $NODE_PATH
/usr/lib/nodejs:/usr/share/javascript

有一件事需要澄清：我不知道如何设置

NODE\u PATH

变量，我自己没有设置它，我有一种感觉，当我安装NODE和NPM时，它随Ubuntu软件包一起出现

然后我决定显式设置

节点路径

变量，并仔细检查依赖项：

root@dev:/web/my-application# export NODE_PATH=/usr/lib/node_modules
root@dev:/web/my-application# npm list
npm WARN mongoose 2.5.11 Unmet dependency in /web/my-application
npm WARN active-x-obfuscator 0.0.1 Unmet dependency in /web/my-application/node_modules/socket.io/node_modules/socket.io-client
npm WARN uglify-js 1.2.5 Unmet dependency in /web/my-application/node_modules/socket.io/node_modules/socket.io-client
npm WARN ws 0.4.x Unmet dependency in /web/my-application/node_modules/socket.io/node_modules/socket.io-client
npm WARN xmlhttprequest 1.2.2 Unmet dependency in /web/my-application/node_modules/socket.io/node_modules/socket.io-client
node-uptime@1.2.0 /web/my-application
├── async@0.1.18 
├─┬ config@0.4.11 
│ ├── coffee-script@1.3.3 
│ ├─┬ vows@0.5.13 
│ │ └── eyes@0.1.7 
│ └── yaml@0.2.3 
├── ejs@0.6.1 
├─┬ express@2.5.0 
│ ├── connect@1.7.3 
│ ├── mime@1.2.5 
│ ├── mkdirp@0.0.7 
│ └── qs@0.5.0 
├── UNMET DEPENDENCY mongoose 2.5.11
└─┬ socket.io@0.9.2 
  ├── policyfile@0.0.4 
  ├── redis@0.6.7 
  └─┬ socket.io-client@0.9.2 
    ├── UNMET DEPENDENCY active-x-obfuscator 0.0.1
    ├── UNMET DEPENDENCY uglify-js 1.2.5
    ├── UNMET DEPENDENCY ws 0.4.x
    └── UNMET DEPENDENCY xmlhttprequest 1.2.2

仍然没有成功，但是当我尝试使用node运行应用程序时，它成功初始化并运行：

root@dev:/web/my-application# node app.js 
Monitor origin started
   info  - socket.io started
Express server listening on port 8082 in development mode
Mongoose: pings.ensureIndex({ timestamp: -1 }) {}  
Mongoose: checkevents.ensureIndex({ timestamp: -1, check: 1 }) {}  
Mongoose: checkhourlystats.ensureIndex({ timestamp: -1, check: 1 }) { unique: true }  
Mongoose: checkdailystats.ensureIndex({ timestamp: -1, check: 1 }) { unique: true }  
Mongoose: checkmonthlystats.ensureIndex({ timestamp: -1, check: 1 }) { unique: true }  
Mongoose: checks.find({ '$where': 'function () {\n if (this.isPaused) return false;\n if (!this.firstTested) return true;\n var delay = (this.lastTested.getTime() - this.firstTested.getTime()) % this.interval;\n return (Date.now() - this.lastTested.getTime() + delay) >= (this.interval || 60000);\n}' }) { fields: { qos: 0 }, safe: true }  
Mongoose: taghourlystats.ensureIndex({ timestamp: -1, name: 1 }) { unique: true }  
Mongoose: tagdailystats.ensureIndex({ timestamp: -1, name: 1 }) { unique: true }  
Mongoose: tagmonthlystats.ensureIndex({ timestamp: -1, name: 1 }) { unique: true }  
Mongoose: tags.ensureIndex({ name: 1 }) { unique: true }

这看起来从现在开始就可以了，但是我肯定不会以root用户身份运行应用程序，所以我需要在以专用用户身份运行应用程序时识别全局NPM包

我感觉NPM在安装软件包时有一些不一致的行为。在全局安装时，它会成功运行，但之后检索失败

---

我能做些什么，还有，一个人的

节点路径

环境变量看起来如何？，

你必须只使用

npm install-d

，而不使用

-g

。对于每个包，包的要求都是本地的（因此，当您依赖于

a

时，您有

node\u模块\a

；当

a

依赖于

b

时，您有

node\u模块\b

）

---

有关更多详细信息，请参阅。

对于我来说，可以使用以下命令解决此问题-

---

npm安装-dkanso@0.3.4--注册表

清除缓存对我有效

npm cache clean

---

我认为这应该是公认的答案，因为它解决了我的问题。只需进入模块的文件夹并在其中安装依赖项。很抱歉，我花了一些时间才回到stackoverflow。确认并接受了答案。谢谢pentaur。这一定是npm中的一个bug，传入默认注册表肯定不会影响安装方式。很抱歉，我不打算投票表决这个答案，因为它不能解释为什么我的上述尝试没有成功。

npm cache clean