using node 0.10.36 commitizen is brokenSee original GitHub issue
When im using node 0.10.36, I cant use commitizen. I get the following error:
/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! @email@example.com commit:
npm ERR! Exit status 8
npm ERR! Failed at the @firstname.lastname@example.org 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 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`
- Created 7 years ago
- Comments:12 (12 by maintainers)
Top GitHub Comments
@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 We should probably add the engines and engineStrict fields to package.json so that it wont install on 0.10