* remove gitter, its just full of spam, github issues /
discussion can fill that gap
* remove travis build, doesn't seem to be active now
* remove dependencies badge, its dead
Fixes N/A
This adds a random number to the end of the
default karma_webpack directory. This will
prevent projects running multiple instances
of karma webpack in parallel from stepping
on one another.
Fixes#465
karma loads all plugins with 'karma-' automatically, including 'plugins' property in config leads to cryptic error messages when attempting to run karma.
* Do not let karma watch files
This prevents specs from running twice every time a file changes, because the webpack already triggers a rerun when recompiled.
Thanks to this comment: https://github.com/webpack/karma-webpack/issues/44#issuecomment-133619802
* Removed array wrapping and default options
* Removed extra colon
The prior solution of pushing all content to the to the webpack server broke down for globs and watching. Karma really desires files and also prefers one to one mapping of said files and trying to fight that was not fruitful.
Instead opted to move all entry points back to the normal Karma serving routes and any auxiliary resources through the middleware.
This also removes much of the complexity and potential overhead relating to tracking individual file changes as Karma does not seem to do incremental testing and a filelist refresh will ensure that the rebuild occurs.
Fixes#1
Implements a fairly large rework of how tests execute to fully support MutliCompilers:
1. Uses webpack-dev-server to host all content.
2. Move all watch behavior to webpack-dev-server
3. Outputs each config build to separate path
4. Wraps mocha tests in bdd suite noting the config name
This introduces a breaking change as the ‘webpack’ framework must now be declared in order to properly populate the test file list.
- add installation instructions
- mention sourcemaps
- separate optional options from the recommended configuration
- update the example tests to use the new defaults in example dir
