angular/packages/bazel/src
Paul Gschwendtner 954b8e53a2 refactor(bazel): ng_module action description should include compile mode (#32955)
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
2019-10-02 13:21:40 -07:00
..
api-extractor feat(bazel): update to the latest @microsoft/api-extractor (#32185) 2019-08-30 13:55:32 -04:00
builders build: update to nodejs rules 0.37.1 (#32151) 2019-09-25 11:29:12 -07:00
ng_package fix(bazel): ng_package(data) should support non-text files (#32721) 2019-09-17 15:58:42 -07:00
ngc-wrapped refactor(ivy): remove the tsc passthrough option (#32219) 2019-08-20 16:41:08 -07:00
schematics build: update to nodejs rules 0.37.1 (#32151) 2019-09-25 11:29:12 -07:00
BUILD.bazel build: update to rules_nodejs 0.32.2 (#31325) 2019-07-01 14:16:42 -07:00
esm5.bzl build: convert entry_point to label (#30627) 2019-06-11 00:03:11 +00:00
external.bzl build(bazel): remove deprecated rules_nodejs NodeModuleInfo provider (#31325) 2019-07-01 14:16:42 -07:00
modify_tsconfig.js fix(bazel): do not throw error when writing tsickle externs (#27200) 2018-12-04 14:01:24 -08:00
ng_module.bzl refactor(bazel): ng_module action description should include compile mode (#32955) 2019-10-02 13:21:40 -07:00
ng_rollup_bundle.bzl build: update rules_nodejs and clean up bazel warnings (#30370) 2019-05-14 10:08:45 -07:00