angular-cn/packages/service-worker/config/BUILD.bazel

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

exports_files(["package.json"])

load("//tools:defaults.bzl", "ng_module")

ng_module(
    name = "config",
    srcs = glob([
        "*.ts",
        "src/**/*.ts",
    ]),
    module_name = "@angular/service-worker/config",
    deps = ["//packages/core"],
)
test: migrate remaining public-api tests to Bazel (#22639) We now create npm packages to cover all the public api assertions in tools/public_api_guard. We no longer depend on ts-api-guardian from npm - it is now stale since the repository was archived. There is no longer a gulp task to enforce or accept the public API, this is in CircleCI as part of running all bazel test targets. PR Close #22639 2018-03-07 14:26:11 -05:00			`package(default_visibility = ["//visibility:public"])`

feat(bazel): change ng_package rule to APF v6 (#22782) Angular Package Format v6 stops bundling files in the esm5 and esm2015 directories, now that Webpack 4 can tree-shake per-file. Adds some missing files like package.json to make packages closer to what we publish today. Refactor ng_package to be a type of npm_package and re-use the packaging action from that rule. PR Close #22782 2018-03-13 14:00:53 -04:00			`exports_files(["package.json"])`

test: migrate remaining public-api tests to Bazel (#22639) We now create npm packages to cover all the public api assertions in tools/public_api_guard. We no longer depend on ts-api-guardian from npm - it is now stale since the repository was archived. There is no longer a gulp task to enforce or accept the public API, this is in CircleCI as part of running all bazel test targets. PR Close #22639 2018-03-07 14:26:11 -05:00			`load("//tools:defaults.bzl", "ng_module")`

			`ng_module(`
			`name = "config",`
			`srcs = glob([`
			`"*.ts",`
			`"src/*/.ts",`
			`]),`
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-15 21:04:34 -04:00			`module_name = "@angular/service-worker/config",`
test: migrate remaining public-api tests to Bazel (#22639) We now create npm packages to cover all the public api assertions in tools/public_api_guard. We no longer depend on ts-api-guardian from npm - it is now stale since the repository was archived. There is no longer a gulp task to enforce or accept the public API, this is in CircleCI as part of running all bazel test targets. PR Close #22639 2018-03-07 14:26:11 -05:00			`deps = ["//packages/core"],`
			`)`