Version 1.0.0

[zinserjan]

This project began for me as a prototype with the goal to provide a way to run tests compiled by webpack easily. Just to see if this works I hacked this together and it works pretty well so far - apart from a few issues.

In the last months I thought a lot about some solutions for the outstanding issues and I think it's time to get started.

Tasks

The following needs to be done before shipping 1.0.0:

Infrastructure

• drop nodejs 0.12 support - Done in drop nodejs 0.12 & 5 support, add nodejs 6 #72
• add flow support - Done in flow setup #75
• add code coverage - Done in code coverage via codecov.io #74

Internals

• use async/await instead of callback hell - Done in support new language features #76, Core refactoring #78
• refactor/split code into 2 parts: CLI & API (Cannot run mocha-webpack from code #65) - Done in Core refactoring #78, export factory function to use mocha-webpack programmatically #88
• replace dynamic entry creation with a static entry file - Done in Core refactoring #78
• replace the "glob-like" file resolution with glob (Finds files, but says "0 passing" tests #48) - Done in Core refactoring #78
• respect defined file extensions in resolve.extensions for directory entries (Finds files, but says "0 passing" tests #48) - Done in use resolve.extensions in webpack config for directory entries #81
• support multiple entry files/patterns/directories (Support multiple entry files/patterns/directories #45, How to exclude "node_modules" #44) - Done in support multiple entry files/patterns/directories #79
• fix: adding / deleting test entry files in watch mode does not trigger a rebuild - Done in support adding/deleting test entry files in watch mode #93
• include source-map-support by default - Done in include source-map-support by default #82
• write to and read from memory (Write to and read from memory #25) - Done in in-memory filesystem for webpack assets #83, Improve affected module detection #86
• support custom reporters with relative file paths (Incompatible with unpublished thrid-party reporter #58) - Done in support custom reporter for mocha #87

User feedback

• ensure order of tasks (compile, test) -> latest log is the relevant one - Done in abort running mocha tests when webpack starts to compile #94
• pretty status logging (Pass CLI options to webpack #60) - Done in Pretty status logging #97
• format webpack errors (strip useless information, make errors more meaningful) - Done in Pretty webpack build errors / warnings #99
• provide some kind of verbose mode with useful logging
• growl should also notify about webpack build status (especially errors)

Validation

• warn when a multi compiler config is given (not supported) (Getting "Invariant Violation: webpackConfig must be a plain object" #56)
• warn and give hint when --compilers option is passed in ( --compilers js:babel-core/register cause argv parse error #23)
• warn when CommonsChunkPlugin is used (does not work with node)

Docs

• write docs & provide examples - Done in documentation #105

[zinserjan]

Just published the first beta release 1.0.0-beta.0.

You can install it with npm install mocha-webpack@next.

Edit: Published 1.0.0-beta.1 to fix an issue with glob path resolution.

[martynchamberlin]

Looking forward to getting this new version on NPM!

[gruckus-gruckus]

any eta on version 1 being published?

[zinserjan]

Just released 1.0.0