0

We use Codeship for continuous integration and Modulus for hosting our projects. Code was running properly until last week, now I'm getting the following error.

    → 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

Here is the package.json file

{
  "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.

4

2 回答 2

1

我对modules.io有同样的问题。上周工作。今天失败了。我通过在我的packages.json.

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

我认为在您的情况下2.x.x无效，因为日志输出显示模数仍然使用3.3.4。

——乔纳森

于 2015-10-02T07:32:01.327 回答
0

这仍然是 Modulus 上的一个活跃问题。我通过一些艰苦的课程发现，你肯定需要确保你对组件版本做出有意识的决定。从 node 和 npm 版本一直到 package.json 中的东西。如果您指定最新版本，您将在最不想要的时候出现错误。

例子。在 package.json 中：

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

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

于 2015-10-18T06:38:27.163 回答