b7138c1ec5
The dev-infra package currently uses rollup for packaging. This has been done initially as a way to workaround manifest paths being used in the AMD JavaScript output. The actual solution to this problem is setting module names that match the `package.json` name. This ensures that the package can be consumed correctly in Bazel, and through NPM. This allows us to get rid of the rollup bundling, and we don't need to hard-code which dependencies should be external or included. Additionally, tools that are part of `dev-infra` can now specify their external dependencies simply in the `package.json`. To reduce version duplication, and out-of-sync versions, a new genrule has been created that syncs the versions with the top-level project `package.json`. PR Close #35647
41 lines
933 B
Python
41 lines
933 B
Python
package(default_visibility = ["//visibility:public"])
|
|
|
|
load("@npm_bazel_typescript//:index.bzl", "ts_config")
|
|
load("//tools:defaults.bzl", "nodejs_binary")
|
|
|
|
exports_files([
|
|
"tsconfig.json",
|
|
"jasmine-seed-generator.js",
|
|
])
|
|
|
|
ts_config(
|
|
name = "tsconfig-test",
|
|
src = "tsconfig-test.json",
|
|
deps = ["tsconfig.json"],
|
|
)
|
|
|
|
nodejs_binary(
|
|
name = "inline-package-json-deps",
|
|
entry_point = "inline-package-json-deps.js",
|
|
)
|
|
|
|
platform(
|
|
name = "rbe_ubuntu1604-angular",
|
|
parents = ["@rbe_ubuntu1604_angular//config:platform"],
|
|
remote_execution_properties = """
|
|
{PARENT_REMOTE_EXECUTION_PROPERTIES}
|
|
properties: {
|
|
name: "dockerAddCapabilities"
|
|
value: "SYS_ADMIN"
|
|
}
|
|
properties: {
|
|
name: "dockerNetwork"
|
|
value: "standard"
|
|
}
|
|
properties: {
|
|
name: "Pool"
|
|
value: "default"
|
|
}
|
|
""",
|
|
)
|