angular-cn/dev-infra/bazel/BUILD.bazel

package(default_visibility = ["//visibility:public"])

filegroup(
    name = "files",
    srcs = [
        "BUILD.bazel",
        "expand_template.bzl",
        "//dev-infra/bazel/browsers:files",
        "//dev-infra/bazel/remote-execution:files",
    ],
)
refactor(dev-infra): ng_rollup_bundle rule should leverage `@bazel/rollup` (#37623) Refactors the `ng_rollup_bundle` rule to a macro that relies on the `@bazel/rollup` package. This means that the rule no longer deals with custom ESM5 flavour output, but rather only builds prodmode ES2015 output. This matches the common build output in Angular projects, and optimizations done in CLI where ES2015 is the default optimization input. The motiviation for this change is: * Not duplicating rollup Bazel rules. Instead leveraging the official rollup rule. * Not dealing with a third TS output flavor in Bazel.The ESM5 flavour has the potential of slowing down local development (as it requires compilation replaying) * Updating the rule to be aligned with current CLI optimizations. This also _fixes_ a bug that surfaced in the old rollup bundle rule. Code that is unused, is not removed properly. The new rule fixes this by setting the `toplevel` flag. This instructs terser to remove unused definitions at top-level. This matches the optimization applied in CLI projects. Notably the CLI doesn't need this flag, as code is always wrapped by Webpack. Hence, the unused code eliding runs by default. PR Close #37623 2020-06-17 10:37:36 +02:00			`package(default_visibility = ["//visibility:public"])`
fix(dev-infra): include `bazel` utility files in npm package (#37891) We recently added a new folder for common bazel utilities to `dev-infra`. The `ng_rollup_bundle` rule relies on an utility that is provided by this `bazel/` folder. Unfortunately though it looks like this folder is currently not included in the NPM package, so that the `ng_rollup_bundle` rule does not work as expected. This commit fixes that by including the bazel utilities in the NPM package. PR Close #37891 2020-07-02 14:45:23 +02:00
			`filegroup(`
			`name = "files",`
			`srcs = [`
fix(dev-infra): add missing BUILD file to dev-infra/bazel:files (#38026) * Without this BUILD file we were seeing errors about the reference to expand_template.bzl in ng_rollup_bundle.bzl because dev-infra/bazel was not considered a package. PR Close #38026 2020-07-14 13:06:21 -07:00			`"BUILD.bazel",`
fix(dev-infra): include `bazel` utility files in npm package (#37891) We recently added a new folder for common bazel utilities to `dev-infra`. The `ng_rollup_bundle` rule relies on an utility that is provided by this `bazel/` folder. Unfortunately though it looks like this folder is currently not included in the NPM package, so that the `ng_rollup_bundle` rule does not work as expected. This commit fixes that by including the bazel utilities in the NPM package. PR Close #37891 2020-07-02 14:45:23 +02:00			`"expand_template.bzl",`
refactor(dev-infra): move shared browser bazel setup into dedicated bazel folder (#42268) This change moves the `dev-infra/browsers` folder into `dev-infra/bazel`. The browser folder is providing custom configuration for Bazel, so it should live within the `bazel` folder for a more well-structured `dev-infra` folder. PR Close #42268 2021-05-24 16:17:27 +02:00			`"//dev-infra/bazel/browsers:files",`
feat(dev-infra): create shared platform for remote execution (#41767) Introduces a shared Bazel platform for remote execution builds using Google cloud. Previously we used `bazel_toolchains` for providing the platform w/ additional CPP and Java toolchains `bazel_toolchains` no longer provides default toolchains with the latest version, but provides a tool (linux and windows only) for generating toolchain/platforms, which then need to be checked into the repository. This is quite inconvenient and cumbersome (especially with no macOS support), so we just provide our own platform and CPP toolchain within `//dev-infra`. This is more simple than all the effort we'd need to make the toolchain generation tool work (while it would also increase the amount of checked-in sources significantly; with more unused toolchains for CPP or Java) PR Close #41767 2021-04-22 16:34:36 +02:00			`"//dev-infra/bazel/remote-execution:files",`
fix(dev-infra): include `bazel` utility files in npm package (#37891) We recently added a new folder for common bazel utilities to `dev-infra`. The `ng_rollup_bundle` rule relies on an utility that is provided by this `bazel/` folder. Unfortunately though it looks like this folder is currently not included in the NPM package, so that the `ng_rollup_bundle` rule does not work as expected. This commit fixes that by including the bazel utilities in the NPM package. PR Close #37891 2020-07-02 14:45:23 +02:00			`],`
			`)`