visionmedia/mocha — Issue #291: Mocha isn't running when installed locally...
Author: balupton
Created: 2012-02-26 07:28:57+00:00
State: open

For some strange reason, mocha is deciding not to run when installed locally anymore... I have no clue why this is, and it only seems to happen on my iMac (works fine on my macbook).

Here's the log:

```
$ npm install mocha@0.13
npm http GET https://registry.npmjs.org/mocha
npm http 304 https://registry.npmjs.org/mocha
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/growl
npm http GET https://registry.npmjs.org/jade/0.20.3
npm http GET https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/growl
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/jade/0.20.3
npm http 304 https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/mkdirp
mocha@0.13.0 ./node_modules/mocha
├── growl@1.5.0
├── debug@0.5.0
├── commander@0.5.2
└── jade@0.20.3
$ npm install -g mocha@0.13
npm http GET https://registry.npmjs.org/mocha
npm http 304 https://registry.npmjs.org/mocha
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/growl
npm http GET https://registry.npmjs.org/jade/0.20.3
npm http GET https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/jade/0.20.3
npm http 304 https://registry.npmjs.org/growl
npm http 304 https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/mkdirp
/Users/balupton/.nvm/v0.6.11/bin/mocha -> /Users/balupton/.nvm/v0.6.11/lib/node_modules/mocha/bin/mocha
/Users/balupton/.nvm/v0.6.11/bin/_mocha -> /Users/balupton/.nvm/v0.6.11/lib/node_modules/mocha/bin/_mocha
growl@1.5.0 /Users/balupton/.nvm/v0.6.11/lib/node_modules/mocha/node_modules/growl
debug@0.5.0 /Users/balupton/.nvm/v0.6.11/lib/node_modules/mocha/node_modules/debug
commander@0.5.2 /Users/balupton/.nvm/v0.6.11/lib/node_modules/mocha/node_modules/commander
mkdirp@0.3.0 /Users/balupton/.nvm/v0.6.11/lib/node_modules/mocha/node_modules/jade/node_modules/mkdirp
jade@0.20.3 /Users/balupton/.nvm/v0.6.11/lib/node_modules/mocha/node_modules/jade
mocha@0.13.0 /Users/balupton/.nvm/v0.6.11/lib/node_modules/mocha
$ node ./node_modules/mocha/bin/mocha --reporter spec --ui bdd --ignore-leaks --growl
$ ./node_modules/mocha/bin/mocha --reporter spec --ui bdd --ignore-leaks --growl
$ mocha --reporter spec --ui bdd --ignore-leaks --growl

versionCompare
✓ should detect 1.1.0 < 1.2.0 is true
✓ should detect 1.2.0 > 1.1.0 is true
✓ should detect 1.2.0 == 1.2.0 is true
✓ should detect 1.2.0 <= 1.2.0 is true
✓ should detect 1.2.0 >= 1.2.0 is true
✓ should detect 1.2.0 < 1.2.1 is true
✓ should detect 1.2.0 < 1.3.0 is true
✓ should detect 1.1.0 >= 1.2.0 is false
✓ should detect 1.2.0 <= 1.1.0 is false
✓ should detect 1.2.0 <> 1.2.0 is false
✓ should detect 1.2.0 > 1.2.0 is false
✓ should detect 1.2.0 < 1.2.0 is false
✓ should detect 1.2.0 >= 1.2.1 is false
✓ should detect 1.2.0 >= 1.3.0 is false

packageCompare
◦ should run as expected: c^C$
$ node --version
v0.6.11
$ npm --version
1.1.1
```

Ran against the repository: https://github.com/balupton/bal-util.npm