2015-09-30 67 views
0

我们使用Codeship进行持续集成和Modulus来托管我们的项目。代码运行正常,直到上周,现在我收到以下错误。NPM错误:找不到模块'我们现在还没有'

→ modulus deploy -p 'project_name' 
Welcome to Modulus 
You are logged in as user_name 
Selecting project_name 

Compressing project... 
5.7 MB written 
Uploading project... 
Upload progress [===================] 100% 
Deploying Project... 
Starting build. 
Creating directories for build environment. 
Downloading source. 
Executing build. 
Package found: /package.json 
Installing node 0.10.25 
Installing npm 3.3.4 
Installing packages from /package.json 

module.js:340 
    throw err; 
     ^
Error: Cannot find module 'are-we-there-yet' 
    at Function.Module._resolveFilename (module.js:338:15) 
    at Function.Module._load (module.js:280:25) 
    at Module.require (module.js:364:17) 
    at require (module.js:380:17) 
    at Object.<anonymous> (/mnt/home/.nvm/v0.10.25/lib/node_modules/npm/node_modules/npmlog/log.js:2:16) 
    at Module._compile (module.js:456:26) 
    at Object.Module._extensions..js (module.js:474:10) 
    at Module.load (module.js:356:32) 
    at Function.Module._load (module.js:312:12) 
    at Module.require (module.js:364:17) 
npm install failed, trying again 

这里是的package.json文件

{ 
    "name": "project-name", 
    "version": "0.0.1-77", 
    "description": "", 
    "main": "index.js", 
    "scripts": { 
    "test": "echo \"Error: no test specified\" && exit 1", 
    "start": "node index.js" 
    }, 
    "engines": { 
    "node": "0.10.25", 
    "npm": "2.x.x" 
    }, 
    "author": "author_name", 
    "license": "ISC", 
    "dependencies": { 
    "express": "3.5.1", 
    "underscore": "^1.6.0", 
    "handlebars": "^3.0.3", 
    "rendr": "1.0.3", 
    "rendr-handlebars": "0.2.0", 
    "request": "~2.30.0", 
    "config": "^0.4.35" 
    }, 
    "devDependencies": { 
    "grunt": "^0.4.4", 
    "grunt-browserify": "^1.2.12", 
    "grunt-contrib-concat": "^0.5.0", 
    "grunt-contrib-handlebars": "^0.8.0", 
    "grunt-contrib-less": "^0.11.0", 
    "grunt-contrib-watch": "^0.6.1", 
    "nodemon": "^1.0.17" 
    } 
} 

Note- The project was working perfectly fine a week back. Now I'm facing this issue.

+0

可能重复的[NPM不工作,总是得到这个错误 - >错误:无法找到模块'我们在那里'](http://stackoverflow.com/questions/31025048/npm-doesnt-work -get-always-this-error-error-can-find-module-are-we-ther) – Claies

+0

@Claies这是一周前的工作。完全相同的代码,适用于本地机器。 – Pankaj

+0

好的,但你是否在另一个问题上尝试了答案?它基本上说,NPM内部有一个丢失的文件,这可能是由于许多原因造成的,而且它在一周前运行的事实与丢失的文件*现在*无关。 – Claies

回答

1

我有modulus.io同样的问题。上周工作。今天失败。我通过在我的packages.json中明确指定npm版本来修复它。

"engines": { 
    "node": "0.10.22", 
    "npm": "1.3.14" 
} 

我觉得你的情况2.x.x是无效的,因为日志输出显示模使用3.3.4反正。

- jonathan

0

这仍然是一个积极的问题Modulus。我发现通过一些艰难的教训,你肯定需要确保你正在为组件版本做出有意识的决定。从节点和npm版本到package.json中的所有内容。如果你指定最新版本,你最终会遇到错误,当你最不想要的时候。

例子。在package.json中:

"engines": { 
"node": "0.10.18", 
"npm": "1.3.8" 
}, 

我还建议如果需要,选择性地定期升级组件。

相关问题