Cz-cli: using node 0.10.36 commitizen is broken
When im using node 0.10.36, I cant use commitizen. I get the following error:
`git-cz
/sw/git-repo/apps/haakon-env/repos/translations/node_modules/commitizen/dist/commitizen/adapter.js:173
var parsed = _path2.default.parse(inboundAdapterPath);
^
TypeError: Object #
npm ERR! Darwin 14.5.0
npm ERR! argv "node" "/Users/jesseoconnor/.nvm/v0.10.36/bin/npm" "run" "commit"
npm ERR! node v0.10.36
npm ERR! npm v2.14.18
npm ERR! code ELIFECYCLE
npm ERR! @meltwater/[email protected] commit: git-cz
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the @meltwater/[email protected] commit script 'git-cz'.
npm ERR! This is most likely a problem with the @meltwater/translations package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! git-cz
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs @meltwater/translations
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls @meltwater/translations
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /sw/git-repo/apps/haakon-env/repos/translations/npm-debug.log
Jesses-MacBook-Pro:translations jesseoconnor$ npm --version
2.14.18
Jesses-MacBook-Pro:translations jesseoconnor$ node --version
v0.10.36`
jessekoconnor
All 12 comments
Hi @jessekoconnor Thanks for reporting this. Unfortunately we do not support Node 0.10. We currently test for version 0.12.* to 5.*. Currently 0.10 and 6.0 are unsupported. I think we probably could be more specific about support either in our package.json or in the README.md.
jimthedev
on 10 May 2016
@jimthedev We should probably add the engines and engineStrict fields to package.json so that it wont install on 0.10
LinusU
on 13 May 2016
@LinusU I agree. Want to PR?
jimthedev
on 13 May 2016
Will do 馃憤
LinusU
on 14 May 2016
229
LinusU
on 14 May 2016
@LinusU Awesome. Can you change your commit message to conform with conventional-changelog? Thanks. 馃憤
jimthedev
on 16 May 2016
@jimthedev I'll fix it right away, would have been great to have #182 now ;)
LinusU
on 17 May 2016
@LinusU, I know, I would like it as well. :)
Unfortunately in the last month my wife's father passed away, I have a new job, a one year old daughter and my cars transmission just died so am a bit preoccupied with other things. Would be happy to take PRs but to be honest I will need help w/merging and publishing even. I will try to get something out but this is very low on my list at the moment. Thanks for the patience and let me know if you'd like to take anything over.
Cheers.
jimthedev
on 17 May 2016
@jimthedev I'm very sorry to hear that, I would be very happy to help out! I use commitizen at work every day so I have a very high interest in keeping it working as smooth as possible. I'm linusu at npm and you can see my username here on github.
Hope that everything works out for the better for you, best of luck!
LinusU
on 17 May 2016
@LinusU Added you to the team + npm. I think if you sign into Appveyor with your github account then you should also have admin access there for windows tests.
jimthedev
on 17 May 2016
Thanks man
LinusU
on 17 May 2016
10 is no longer supported and @LinusU added the engines tag so I am closing this. Thanks!
jimthedev
on 18 Aug 2016
Related issues
ktwbc
路
5Comments
athewsey
路
4Comments
emcniece
路
3Comments
boxsnake
路
3Comments
fendy-g
路
7Comments
Most helpful comment
@LinusU Added you to the team + npm. I think if you sign into Appveyor with your github account then you should also have admin access there for windows tests.