Content
You are here:
Added by Kiffin Gish almost 8 years ago
Tried to install latest dev branch and get the following error. Can someone please tell me what is going wrong?
$ npm install
npm ERR! Linux 4.4.0-62-generic
npm ERR! argv "/home/kiffin/.nvm/versions/node/v6.9.1/bin/node" "/home/kiffin/.nvm/versions/node/v6.9.1/bin/npm" "install"
npm ERR! node v6.9.1
npm ERR! npm v4.1.2
npm ERR! code ENOTSUP
npm ERR! notsup Unsupported engine for openproject@0.1.0: wanted: {"node":"6.9.1","npm":"4.0.0"} (current: {"node":"6.9.1","npm":"4.1.2"})
npm ERR! notsup Not compatible with your version of node/npm: openproject@0.1.0
npm ERR! notsup Not compatible with your version of node/npm: openproject@0.1.0
npm ERR! notsup Required: {"node":"6.9.1","npm":"4.0.0"}
npm ERR! notsup Actual: {"npm":"4.1.2","node":"6.9.1"}
npm ERR! Please include the following file with any support request:
npm ERR! /home/kiffin/projects/openproject/npm-debug.log
Replies (7)
The
npmrequirement on the dev requires specifically4.0.0, thus your 4.1.2 doesn’t match. That seems to be a mistake, I’ll push a fix./edit https://github.com/opf/openproject/commit/418cd5ec96dee947339e72cd9cbc1b49d274b30e
Okay that helps, however…
$ cd frontend && npm install ... npm ERR! notsup Unsupported engine for karma@0.12.37: wanted: {"node":">=0.8 <=0.12 || >=1 <=2"} (current: {"node":"6.2.0","npm":"4.1.2"}) npm ERR! notsup Not compatible with your version of node/npm: karma@0.12.37 npm ERR! notsup Not compatible with your version of node/npm: karma@0.12.37 npm ERR! notsup Required: {"node":">=0.8 <=0.12 || >=1 <=2"} npm ERR! notsup Actual: {"npm":"4.1.2","node":"6.2.0"}Hi Kiffin,
it seems that karma doesn’t like our node engine requirements. I’ve suggested a PR to update it: https://github.com/opf/openproject/pull/5179
Best,
Oliver
Okay thanks. I’m a bit blocked mow, so what’s the workaround until they fix it?
I’m working on getting the branch mergeable. For now you can just work on the core at the
housekeeping/karmabranch.Let me know if that resolves your issues
Best,
Oliver
The issue should be fixed on dev now.
I can verify that everything works again, thanks.