fix(@angular-devkit/build-angular): several fixes for commonjs warnings #18081
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix(@angular-devkit/build-angular): match allowed dependencies against the package name
With this change we add the functionality to also match an allowed dependency against a package name. The package name is retrieved from the rawRequest.
Previously, users needed to add the request path which in some case might be a deep import. Ex:
zone.js/dist/zone-error
. With this change adding the package name examplezone.js
will suffice.Closes: #18058
fix(@angular-devkit/build-angular): show warning when using non global locale data
When using the
localize
option directly importing locale data from@angular/common
is not needed because the Angular CLI will automatically include locale data. When not using thelocalize
option, most likely users meant to import the global variant of the local data.See: https://angular.io/guide/i18n#import-global-variants-of-the-locale-data