Before, a single instance of yargs was accumulating options, so commands parsed later would have options from prior commands. That's because all yargs options are global by default. Now, a new instance of yargs is required before each command is parsed, so global options aren't accumulated.
fixes#1567
According to [the Browserslist docs](https://github.com/browserslist/browserslist#queries),
the file should be named `browserslist`. The previous name had a missing
"s" in the middle.
I do not know how `browserslist` is integrated in Nx and the Angular
CLI, but it is possible that the configuration file was being ignored
entirely due to this naming error. When the `browserslist` CLI does not
find a configuration file, it uses a sensible default configuration, so
it would not be obvious that the configuration file was ignored.
* fix(testing): disable collectCoverage by default
Disabling collectCoverage by default as this causes issues with latest version of Jest
Temp fix#1531
* Adding back code coverage reporters
* feat(nx): add migration to update collectCoverage to false in jest.config.js
Added new migration script to update jest.config.js collectCoverage property to false
* refactor(nx): move migrations to @nrwl/jest
Move the collectCoverage migration to the jest package
* chore: refactor to use AST utils
Angular CLI 8.1.x is required in order to use the --allow-dirty option.
This also covers the additional build dependencies added when generating
libraries.
Move addUpdateTask util function to @nrwl/workspace to run updates from @nrwl/angular migrations
Run update migration to latest version for NgRx if installed
The schematics for React and Angular still refer to Angular CLI power-ups.
This also links the generated schematic for an Angular or React application
to their framework-specific pages.
