Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dependency 'mocha' out of date #38

Closed
katanacrimson opened this issue Feb 23, 2013 · 4 comments
Closed

dependency 'mocha' out of date #38

katanacrimson opened this issue Feb 23, 2013 · 4 comments

Comments

@katanacrimson
Copy link
Contributor

Mocha dependency is badly out of date and needs updated desperately.

npm WARN engine mocha@0.8.1: wanted: {"node":">= 0.4.x < 0.7.0"} (current: {"node":"v0.8.19","npm":"1.2.10"})
npm WARN unmet dependency /home/katana/repos/rumble/node_modules/twit/node_modules/mocha requires commander@'0.3.2' but will load
npm WARN unmet dependency /home/katana/repos/rumble/node_modules/commander,
npm WARN unmet dependency which is version 1.1.1
npm WARN engine commander@0.3.2: wanted: {"node":">= 0.4.x < 0.7.0"} (current: {"node":"v0.8.19","npm":"1.2.10"})
:katana@serenity ~/
$ npm info mocha version
npm http GET https://registry.npmjs.org/mocha
npm http 200 https://registry.npmjs.org/mocha
1.8.1

:katana@serenity ~/
$ npm info mocha dependencies

{ commander: '0.6.1',
  growl: '1.7.x',
  jade: '0.26.3',
  diff: '1.0.2',
  debug: '*',
  mkdirp: '0.3.3',
  ms: '0.3.0' }
@katanacrimson
Copy link
Contributor Author

This appears caused by 0c3b8bd, where previously the version requirement was >= 0.8.1, whereas now it is specifically 0.8.1 which has dependencies (package commander@0.3.2) that declare themselves incompatible with node 0.8.

@ttezel
Copy link
Owner

ttezel commented Mar 1, 2013

I updated mocha to version 1.8.1. If problems occur, feel free to reopen this issue.

@ttezel ttezel closed this as completed Mar 1, 2013
@katanacrimson
Copy link
Contributor Author

btw, shouldn't mocha be a devDependency entry?

@ttezel
Copy link
Owner

ttezel commented Mar 5, 2013

You're right. I updated the package.json and published twit v1.1.5 with the fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants