* 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*.
This reverts commit 47f937e28f0a9d82997bd29630a8b3b92f44c0f5.
This commit had a few issues detected by the NativeScript project. It is
likely that they would have affected more users (and libraries) and so
it is safer to revert now and investigate later. Will likely be fixed in
6.2 by refactoring this whole plugin properly.
update the CircleCi and Travis configurations
update ng test and ng e2e command flags for version 6
use headless chrome instead of chrome
add guidance on ChromeDriver
closes#10677
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.
If there is a package.json we should also verify that it has a main or fesm field
to see if webpack would actually resolve it properly. Otherwise use the JavaScript
resolution.
This is a temporary fix and still has obvious limitations and issues. Namely, this
code is never run if there is only one path mapping, but that falls outside the
scope of this fix. Also, some people might have valid packages but want to resolve
to the JS file itself (which is what TypeScript does by default). These should be
fixed with a refactoring of the path plugin.
Fixes https://github.com/nativescript/nativescript-dev-webpack/issues/607
This should clean up the code a bit.
Note: at first I added the no-useless-cast rule, but after getting frustrated
with it (as it has many false positive), I decided to remove the rule but some
useless casts were removed so I let those in the PR.
With fixes; new now handles the parent initialize, visitor_spec now errors on
rejection, and nothing in the writeI18nOutFile() function was async so removed
the promise there entirely.
Testing the size of a simple app is now done directly in the large specs inside devkit/build-angular.
The Angular.io test was very out of date, and Angular.io now keeps track of its bundle size much better than we ever did.
