mochajs / mocha-core Goto Github PK

Is this repo stall or have this been integrated into mocga 3.x?

This should be based on the current "spec" reporter.

Create a new repo for this.

We're also going to want to hammer out how the plugin API should interact with multiple reporters.

The default runner (for now) should probably be a "serial" runner.

Create a new repo for this.

Currently you're expected to get a function from any given (non-bundled) plugin, and pass that into mocha.use(). But if we're bundling plugins for the browser, they can attach themselves to a global namespace (ostensibly window.mocha). I think this is reasonable.

I'm trying to implement but it's currently broken; see wip branch

Need a cli. make mocha-cli repo.

@Munter @boneskull @dasilvacontin @hollomancer @ScottFreeCode

I looked at the source and just found a tons of issues

• outdated deps. E.g. lodash doesn't have a 'all' or 'pipe' function anymore. Stampit is on v. 3.x now.
• kefir is outdated, and kefir stream etc doesn't match latest kefir
• the build process is a total mess. Can't even build it on a windows computer
• duplicate export in utils.js folder.
• tests for prev commits still exist in test folder
• missing tests
• couldn't get anything of this running at all
• memory issues and memory leaks.

and a lot more.

If this going to be fixed, and when will we expect to see a Mocha running? And why use Stampit and Kefir? Stampit eating a lot of memory.

the options API is for plugin authors (and mocha-core itself) to define what options are available on the CLI, programmatically or otherwise