angular/packages/bazel
Paul Gschwendtner c7d37f74cf build: expose locales as package export for ES module resolution (#43431)
As part of v13, all APF packages use the `exports` field which defines
the public entry-points/mappings for a package. so-called package exports.

The `ng_package` rule creates all the necessary mappings/sub-path exports
for the entry-points of `@angular/common`. Though, since the locale files are
generated separately and are not an actual entry-point, we need to expose these
files publicly so that they can be imported/resolved by consumers.

PR Close #43431
2021-10-01 18:28:44 +00:00
..
docs refactor(bazel): remove old Angular CLI schematics and builder (#41575) 2021-04-13 13:01:59 -07:00
src refactor: switch packages away from deep cross-package imports (#43431) 2021-10-01 18:28:43 +00:00
test build: expose locales as package export for ES module resolution (#43431) 2021-10-01 18:28:44 +00:00
third_party/github.com/bazelbuild/bazel/src/main/protobuf build: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0 (#39182) 2020-10-08 11:54:59 -07:00
BUILD.bazel feat(bazel): create transition for enabling partial compilation (#43431) 2021-10-01 18:28:42 +00:00
index.bzl refactor(bazel): move ng_module.bzl file into sub-directory for consistent structure (#43431) 2021-10-01 18:28:42 +00:00
package.json feat(bazel): implement partial compilation APF v13 for ng_package rule (#43431) 2021-10-01 18:28:42 +00:00