954b8e53a2
Similarly to `ts_library` compilation actions, the `ng_module` compile action should include the current compile mode in the action description. This makes it consistent with `ts_library` targets and also avoids confusion when both output flavors are requested. Currently when both output flavors are requested (e.g. in the `ng_package` rule), both devmode and prodmode compilations have the same action name. This is confusing and looks like the given target is built *twice* due to a bug (which is obviously not the case though) PR Close #32955 |
||
|---|---|---|
| .. | ||
| docs | ||
| src | ||
| test | ||
| third_party/github.com/bazelbuild/bazel/src/main/protobuf | ||
| BUILD.bazel | ||
| index.bzl | ||
| package.bzl | ||
| package.json | ||