angular-cn/packages/bazel/test/ng_package/example
Alex Eagle 689f351092 build: expose flatModuleOutFile option on ng_module (#22814)
This lets projects like Material change ng_package "bundle index" files to non-conflicting paths

Currently packages like @angular/core ship with the generated metadata
in a path like 'core.js' which overwrites one of the inputs.

Angular material puts the generated file in a path like 'index.js'

Either way these files generated by ng_module rules have the potential
to collide with inputs given by the user, which results in an error.

Instead, give users the freedom to choose a different non-conflicting name.

Also this refactors the ng_package rule, removing the redundant
secondary_entry_points attribute.

Instead, we assume that any ng_module in the deps with a module_name
attribute is a secondary entry point.

PR Close #22814
2018-03-20 13:28:57 -07:00
..
secondary build: expose flatModuleOutFile option on ng_module (#22814) 2018-03-20 13:28:57 -07:00
BUILD.bazel build: expose flatModuleOutFile option on ng_module (#22814) 2018-03-20 13:28:57 -07:00
index.ts fix(bazel): ng_package includes transitive .d.ts and flatModuleMetadata (#22499) 2018-02-28 13:29:56 -08:00
mymodule.ts fix(bazel): ng_package includes transitive .d.ts and flatModuleMetadata (#22499) 2018-02-28 13:29:56 -08:00
package.json feat(bazel): ng_package adds package.json props (#22499) 2018-02-28 13:29:56 -08:00
some-file.txt feat(bazel): ng_package adds package.json props (#22499) 2018-02-28 13:29:56 -08:00