2019-05-22 20:28:42 -04:00
|
|
|
workspace(
|
|
|
|
name = "angular",
|
|
|
|
managed_directories = {"@npm": ["node_modules"]},
|
|
|
|
)
|
2017-09-25 15:40:22 -04:00
|
|
|
|
2018-12-05 15:16:14 -05:00
|
|
|
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
|
2018-12-01 19:08:15 -05:00
|
|
|
|
2018-10-22 17:26:52 -04:00
|
|
|
# Uncomment for local bazel rules development
|
|
|
|
#local_repository(
|
|
|
|
# name = "build_bazel_rules_nodejs",
|
|
|
|
# path = "../rules_nodejs",
|
|
|
|
#)
|
|
|
|
#local_repository(
|
2019-02-08 17:01:51 -05:00
|
|
|
# name = "npm_bazel_typescript",
|
2018-10-22 17:26:52 -04:00
|
|
|
# path = "../rules_typescript",
|
|
|
|
#)
|
|
|
|
|
2019-02-04 18:53:32 -05:00
|
|
|
# Fetch rules_nodejs so we can install our npm dependencies
|
|
|
|
http_archive(
|
|
|
|
name = "build_bazel_rules_nodejs",
|
2019-06-25 16:11:54 -04:00
|
|
|
sha256 = "e04a82a72146bfbca2d0575947daa60fda1878c8d3a3afe868a8ec39a6b968bb",
|
|
|
|
urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/0.31.1/rules_nodejs-0.31.1.tar.gz"],
|
2018-06-25 14:22:23 -04:00
|
|
|
)
|
|
|
|
|
2019-02-04 18:53:32 -05:00
|
|
|
# Check the bazel version and download npm dependencies
|
2019-03-14 22:35:00 -04:00
|
|
|
load("@build_bazel_rules_nodejs//:defs.bzl", "check_bazel_version", "check_rules_nodejs_version", "node_repositories", "yarn_install")
|
2018-05-10 16:12:30 -04:00
|
|
|
|
2019-05-22 20:28:42 -04:00
|
|
|
# Bazel version must be at least the following version because:
|
|
|
|
# - 0.26.0 managed_directories feature added which is required for nodejs rules 0.30.0
|
2019-06-12 21:18:26 -04:00
|
|
|
# - 0.27.0 has a fix for managed_directories after `rm -rf node_modules`
|
2019-02-26 07:30:44 -05:00
|
|
|
check_bazel_version(
|
|
|
|
message = """
|
2018-12-01 19:08:15 -05:00
|
|
|
You no longer need to install Bazel on your machine.
|
|
|
|
Angular has a dependency on the @bazel/bazel package which supplies it.
|
|
|
|
Try running `yarn bazel` instead.
|
|
|
|
(If you did run that, check that you've got a fresh `yarn install`)
|
2018-08-05 22:10:07 -04:00
|
|
|
|
2019-01-16 04:19:01 -05:00
|
|
|
""",
|
2019-06-12 21:18:26 -04:00
|
|
|
minimum_bazel_version = "0.27.0",
|
2019-01-16 04:19:01 -05:00
|
|
|
)
|
2018-09-24 16:58:23 -04:00
|
|
|
|
2019-05-22 20:28:42 -04:00
|
|
|
# The NodeJS rules version must be at least the following version because:
|
2019-02-20 12:54:42 -05:00
|
|
|
# - 0.15.2 Re-introduced the prod_only attribute on yarn_install
|
|
|
|
# - 0.15.3 Includes a fix for the `jasmine_node_test` rule ignoring target tags
|
|
|
|
# - 0.16.8 Supports npm installed bazel workspaces
|
2019-02-27 17:38:45 -05:00
|
|
|
# - 0.26.0 Fix for data files in yarn_install and npm_install
|
2019-04-23 13:50:55 -04:00
|
|
|
# - 0.27.12 Adds NodeModuleSources provider for transtive npm deps support
|
2019-05-22 20:28:42 -04:00
|
|
|
# - 0.30.0 yarn_install now uses symlinked node_modules with new managed directories Bazel 0.26.0 feature
|
2019-06-07 12:28:41 -04:00
|
|
|
# - 0.31.1 entry_point attribute of nodejs_binary & rollup_bundle is now a label
|
2019-06-25 16:11:54 -04:00
|
|
|
check_rules_nodejs_version(minimum_version_string = "0.31.1")
|
2019-02-20 12:54:42 -05:00
|
|
|
|
2019-02-04 18:53:32 -05:00
|
|
|
# Setup the Node.js toolchain
|
2018-05-11 02:35:21 -04:00
|
|
|
node_repositories(
|
2019-06-17 13:17:19 -04:00
|
|
|
node_repositories = {
|
|
|
|
"10.16.0-darwin_amd64": ("node-v10.16.0-darwin-x64.tar.gz", "node-v10.16.0-darwin-x64", "6c009df1b724026d84ae9a838c5b382662e30f6c5563a0995532f2bece39fa9c"),
|
|
|
|
"10.16.0-linux_amd64": ("node-v10.16.0-linux-x64.tar.xz", "node-v10.16.0-linux-x64", "1827f5b99084740234de0c506f4dd2202a696ed60f76059696747c34339b9d48"),
|
|
|
|
"10.16.0-windows_amd64": ("node-v10.16.0-win-x64.zip", "node-v10.16.0-win-x64", "aa22cb357f0fb54ccbc06b19b60e37eefea5d7dd9940912675d3ed988bf9a059"),
|
|
|
|
},
|
|
|
|
node_version = "10.16.0",
|
2018-09-11 21:11:32 -04:00
|
|
|
package_json = ["//:package.json"],
|
2019-03-20 16:39:33 -04:00
|
|
|
# yarn 1.13.0 under Bazel has a regression on Windows that causes build errors on rebuilds:
|
|
|
|
# ```
|
|
|
|
# ERROR: Source forest creation failed: C:/.../fyuc5c3n/execroot/angular/external (Directory not empty)
|
|
|
|
# ```
|
|
|
|
# See https://github.com/angular/angular/pull/29431 for more information.
|
|
|
|
# It possible that versions of yarn past 1.13.0 do not have this issue, however, before
|
|
|
|
# advancing this version we need to test manually on Windows that the above error does not
|
|
|
|
# happen as the issue is not caught by CI.
|
2019-03-20 15:55:31 -04:00
|
|
|
yarn_version = "1.12.1",
|
2018-05-11 02:35:21 -04:00
|
|
|
)
|
2018-05-10 16:12:30 -04:00
|
|
|
|
2019-02-20 12:54:42 -05:00
|
|
|
yarn_install(
|
|
|
|
name = "npm",
|
2019-06-25 16:11:54 -04:00
|
|
|
data = [
|
|
|
|
"//:tools/npm/@angular_bazel/index.js",
|
|
|
|
"//:tools/npm/@angular_bazel/package.json",
|
|
|
|
"//:tools/postinstall-patches.js",
|
|
|
|
"//:tools/yarn/check-yarn.js",
|
|
|
|
],
|
2019-02-20 12:54:42 -05:00
|
|
|
package_json = "//:package.json",
|
2019-06-25 16:11:54 -04:00
|
|
|
# Don't install devDependencies, they are large and not used under Bazel
|
|
|
|
prod_only = True,
|
|
|
|
# Temporarily disable node_modules symlinking until the fix for
|
|
|
|
# https://github.com/bazelbuild/bazel/issues/8487 makes it into a
|
|
|
|
# future Bazel release
|
|
|
|
symlink_node_modules = False,
|
2019-06-07 16:38:06 -04:00
|
|
|
yarn_lock = "//:yarn.lock",
|
2019-02-20 12:54:42 -05:00
|
|
|
)
|
2019-02-04 18:53:32 -05:00
|
|
|
|
2019-02-20 12:54:42 -05:00
|
|
|
# Install all bazel dependencies of the @npm npm packages
|
|
|
|
load("@npm//:install_bazel_dependencies.bzl", "install_bazel_dependencies")
|
2018-10-04 16:14:14 -04:00
|
|
|
|
2019-02-04 18:53:32 -05:00
|
|
|
install_bazel_dependencies()
|
|
|
|
|
|
|
|
# Load angular dependencies
|
|
|
|
load("//packages/bazel:package.bzl", "rules_angular_dev_dependencies")
|
|
|
|
|
|
|
|
rules_angular_dev_dependencies()
|
|
|
|
|
|
|
|
# Load karma dependencies
|
2019-02-08 17:01:51 -05:00
|
|
|
load("@npm_bazel_karma//:package.bzl", "rules_karma_dependencies")
|
2019-02-04 18:53:32 -05:00
|
|
|
|
|
|
|
rules_karma_dependencies()
|
|
|
|
|
|
|
|
# Setup the rules_webtesting toolchain
|
2019-02-13 12:33:48 -05:00
|
|
|
load("@io_bazel_rules_webtesting//web:repositories.bzl", "web_test_repositories")
|
2018-05-10 16:12:30 -04:00
|
|
|
|
|
|
|
web_test_repositories()
|
2018-09-24 16:58:23 -04:00
|
|
|
|
2019-02-13 12:33:48 -05:00
|
|
|
# Temporary work-around for https://github.com/angular/angular/issues/28681
|
|
|
|
# TODO(gregmagolan): go back to @io_bazel_rules_webtesting browser_repositories
|
2019-05-15 23:01:50 -04:00
|
|
|
load("//:browser_repositories.bzl", "browser_repositories")
|
2019-02-13 12:33:48 -05:00
|
|
|
|
|
|
|
browser_repositories()
|
2018-05-10 16:12:30 -04:00
|
|
|
|
2019-02-04 18:53:32 -05:00
|
|
|
# Setup the rules_typescript tooolchain
|
2019-02-20 12:54:42 -05:00
|
|
|
load("@npm_bazel_typescript//:index.bzl", "ts_setup_workspace")
|
2018-05-10 16:12:30 -04:00
|
|
|
|
|
|
|
ts_setup_workspace()
|
|
|
|
|
2019-02-04 18:53:32 -05:00
|
|
|
# Setup the rules_sass toolchain
|
2018-04-25 12:23:20 -04:00
|
|
|
load("@io_bazel_rules_sass//sass:sass_repositories.bzl", "sass_repositories")
|
2018-09-24 16:58:23 -04:00
|
|
|
|
2018-04-25 12:23:20 -04:00
|
|
|
sass_repositories()
|
|
|
|
|
2019-02-04 18:53:32 -05:00
|
|
|
# Setup the skydoc toolchain
|
2018-04-25 12:23:20 -04:00
|
|
|
load("@io_bazel_skydoc//skylark:skylark.bzl", "skydoc_repositories")
|
2018-09-24 16:58:23 -04:00
|
|
|
|
2018-04-25 12:23:20 -04:00
|
|
|
skydoc_repositories()
|
2019-03-15 13:45:20 -04:00
|
|
|
|
|
|
|
load("@bazel_toolchains//rules:environments.bzl", "clang_env")
|
|
|
|
load("@bazel_toolchains//rules:rbe_repo.bzl", "rbe_autoconfig")
|
|
|
|
|
|
|
|
rbe_autoconfig(
|
|
|
|
name = "rbe_ubuntu1604_angular",
|
2019-06-25 04:07:01 -04:00
|
|
|
# Need to specify a base container digest in order to ensure that we can use the checked-in
|
|
|
|
# platform configurations for the "ubuntu16_04" image. Otherwise the autoconfig rule would
|
|
|
|
# need to pull the image and run it in order determine the toolchain configuration. See:
|
|
|
|
# https://github.com/bazelbuild/bazel-toolchains/blob/0.27.0/configs/ubuntu16_04_clang/versions.bzl
|
|
|
|
base_container_digest = "sha256:94d7d8552902d228c32c8c148cc13f0effc2b4837757a6e95b73fdc5c5e4b07b",
|
2019-03-15 13:45:20 -04:00
|
|
|
# Note that if you change the `digest`, you might also need to update the
|
|
|
|
# `base_container_digest` to make sure marketplace.gcr.io/google/rbe-ubuntu16-04-webtest:<digest>
|
|
|
|
# and marketplace.gcr.io/google/rbe-ubuntu16-04:<base_container_digest> have
|
2019-06-25 04:07:01 -04:00
|
|
|
# the same Clang and JDK installed. Clang is needed because of the dependency on
|
|
|
|
# @com_google_protobuf. Java is needed for the Bazel's test executor Java tool.
|
|
|
|
digest = "sha256:76e2e4a894f9ffbea0a0cb2fbde741b5d223d40f265dbb9bca78655430173990",
|
2019-03-15 13:45:20 -04:00
|
|
|
env = clang_env(),
|
|
|
|
registry = "marketplace.gcr.io",
|
2019-06-25 04:07:01 -04:00
|
|
|
# We can't use the default "ubuntu16_04" RBE image provided by the autoconfig because we need
|
|
|
|
# a specific Linux kernel that comes with "libx11" in order to run headless browser tests.
|
2019-03-15 13:45:20 -04:00
|
|
|
repository = "google/rbe-ubuntu16-04-webtest",
|
|
|
|
)
|