--watch fails on Windows #480

ShaneCourtrille opened this Issue Jun 28, 2012 · 7 comments


None yet
5 participants

mocha --watch

results in:

var b = process.binding('signal_watcher');
Error: No such module
at process.startup.processSignalHandlers.process.on.process.addListener (node.js:468:27)
at Object. (C:\Users\ShaneC\AppData\Roaming\npm\node_modules\mocha\bin_mocha:242:1
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.runMain (module.js:487:10)
at process.startup.processNextTick.process._tickCallback (node.js:244:9)

Windows 7 64bit


tj commented Jun 28, 2012

node issue

tj closed this Jun 28, 2012

node issue?

I've the same problem with node 0.8.4 and mocha 1.3.0. Is there any solution running mocha with --watch on windows?


Thank you, but changing the source of mocha is not a solution for us. Is this the only way?

As I've said it is a workaround, maybe later the problem will be solved in node for windows. What is the problem with modifying/customizing master branch version for your needs?

The other way is to use nodemon to run mocha as node module. Mocha has JS API. The problem with this solution is output - there won't be colors. But it will handle code exceptions/erros without need to rerun mocha in console.

The other way is to try tool called testem from this branch https://github.com/Raynos/testem - it has embedded filewatcher,

vbedegi commented Aug 12, 2012

You can also try wocha (which is basically a filesystem watcher + mocha executer)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment