build: remove module id references for components in release output #17625
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.
Currently when building the libary with Gulp, we manually inline
resources and remove the
moduleId
properties. This is actuallywhy #13883 never came up until Bazel was a thing.
Since we now release with Bazel and rely on the official resource
inlining from
@angular/compiler-cli
we no longer have control toomit the
moduleId
properties. Technically since resources areinlined, the
moduleId
is unnecessary and can cause unexpectedbehavior. So this could be considered a bug in compiler-cli.
Possible fix: angular/angular#33621.
For now though, since it's unlikely that this is fixed upstream
in RC phase, we manually patch the NGC resource inlining transform
to also remove the
moduleId
property.Keeping
moduleId
can cause errors in the UMD bundles like: