Added --no-coverage flag to skyux watch

[Blackbaud-SteveBrush]

How to test:

• Type skyux watch --no-coverage <-- instrument loader will not mangle the source files

Addresses issue #643

[codecov-io]

Codecov Report

Merging #157 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #157   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          34     34           
  Lines         696    711   +15     
  Branches       85     89    +4     
=====================================
+ Hits          696    711   +15

Flag	Coverage Δ
#builder	100% <100%> (ø)	⬆️
#runtime	100% <ø> (ø)	⬆️

Impacted Files	Coverage Δ
config/karma/shared.karma.conf.js	100% <ø> (ø)	⬆️
index.js	100% <100%> (ø)	⬆️
cli/test.js	100% <100%> (ø)	⬆️
config/webpack/test.webpack.config.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 07f0e70...4f0d828. Read the comment docs.

[Blackbaud-BobbyEarl]

A few questions:

Any thoughts on putting argv as the second argument to the getWebpackConfig() method?

Wondering if we could simplify it a bit so that --no-coverage flag is simply passed through? Then in getWebpackConfig you could always push the coverage rule, unless argv['no-coverage'] exists. Might be better than passing around the string versions of a boolean and changing what's the default in each method.

[Blackbaud-BobbyEarl]

We'll still need to add documentation around this option as well.

[blackbaud-johnly]

I created blackbaud/skyux2#723 to document this option. Thanks @Blackbaud-BobbyEarl