* refactor(@angular-devkit/build-angular): mute internal reporters when
other reporters are configured
internal Karma reporters should suppress output when user-defined
reporters are configured to prevent extrananeous error reporting for
failed tests
* refactor(@angular-devkit/build-angular): mute internal reporters when
other reporters are configured
internal Karma reporters should suppress output when user-defined
reporters are configured to prevent extrananeous error reporting for
failed tests
New rules to deal with templates using a .template extension. Apply the template only
to those files, then remove the .template suffix.
Also added a new rename() rule that takes a matcher and a renamer. Nothing big there.
Also added a new composeFileOperator() that compose operators one after the other.
1. update the return type of 'validateOptionsWithSchema' to make it
conform the signature of engineHost.registerOptionsTransform
2. fix minor naming issue
Currently, there is no mechanism in the Angular tooling to forcefully
output colors regardless of detected terminal capabilities. This commit
adds an override via an environment variable: `FORCE_COLOR`. The
behavior in this commit is the same as the behavior in a commonly used
module, `supports-color` (https://github.com/chalk/supports-color#info).
This is especially useful when piping output from the Angular CLI, which
would automatically and irreversibly disable colors before this commit.
Supports for new lines and hexa was useful for doc and descriptions (including
schematics and builder declarations). Adding the other numerical constants was
easy enough. This fully completes JSON5 support.
And receives in its constructor the enginehost and registry. This simplifies the creation
of the NodeWorkflow, or later on the Google3Workflow etc, since all the duplicate logic
is now in a single base class.
This is yak shaving for internal stuff.
Before we only allowed tsconfig files (with includes added). This is necessary
for the lint fixing for schematics to target specific files.
Also added a feature that look for the tslint.json file if no tslint.json
file or configuration object was passed. Skipping the first argument to the
task constructor will look for the tslint closest to EVERY files being
linted.
Like the interpolation and the pipe character. The default behaviour is kept.
We will need to use those to work around some limiations of the google3 file system which
does not accept "@".
* The `loader-utils` package is actively used in the `@angular-devkit/build_angular` package, and should therefore also list `loader-utils` as dependency. It might work for most package managers that do flatten the node modules, but if not (e.g. pnpm) this will fail *correctly*.
Fixing an issue when event reporter is executed before coverage reporter, which was causing the test command to pass even though unit testing coverage thresholds were not met.
