Christopher Hiller

This looks like a breaking change to me unless you feel this is _actually_ a "bug fix" and not just a "revision of intent" 😜

> > ...that being said, if using spawnChild(), there's really nowhere else for the error to go. > > Could you show the exact situation you are talking about here?...

Just wanted to plug [Wallaby](https://wallabyjs.com) for running tests in "watch" mode (or even as you type). I've been a user for years and I haven't found anything better.

Yeah. As TJ said, the problem is even if we were to make everything "node-able", it may require too much boilerplate to be useful. However... @glenjamin thanks for the heads-up...

I've added a proof-of-concept to 3cdd4a04c48193cceac6af7db72af06d380014a9

anyway, it would need a bit of work, but I think we can easily generalize it for all interfaces. there is no support here for Growl, `mocha.opts` or various other...

@glenjamin it kind of just needs to happen. Mocha should have a core programmatic API. A nice side-effect of that is node-able tests. The environment in which it runs will...

well, `const {describe, it} = window` too, I suppose. this is so fundamental to mocha's architecture that mocha [exports the global object](https://github.com/mochajs/mocha/blob/master/browser-entry.js#L187) when bundled.

the `mocha` executable will continue to use globals; that will likely never change. what we can (and should) shoot for is the ability to easily run mocha tests via `node`...

likely so!