Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/BUILD.bazel

83 lines
2.5 KiB
Text
Raw Normal View History

build: disable bazel nodejs linker to improve stability on windows (#45872) The NodeJS Bazel linker does not work well on Windows because there is no sandboxing and linker processes from different tests will attempt to modify the same `node_modules`, causing concurrency race conditions and resulting in flakiness. PR Close #45872
2022-05-04 12:47:58 +00:00
load("//tools:defaults.bzl", "nodejs_binary")
build: share Saucelabs browsers between karma test targets using background Saucelabs daemon and custom karma launcher (#49200) This upgrades the Saucelabs Bazel step on CI to use the more efficient Saucelabs daemon PR Close #49200
2023-02-20 20:37:34 +00:00
load("@build_bazel_rules_nodejs//:index.bzl", "js_library")
build(bazel): incrementally run aio example e2e tests Replaces the workflow where all example e2es are run at once
2022-07-06 23:16:50 +00:00
load("//:yarn.bzl", "YARN_PATH")
build: update bazel (#45431) Update `@bazel` packages to the latest 5.x version. Some of the changes here are modeled after angular/dev-infra@40c0ac855975ce9586b07af3a36a0bf4e3b58350. Co-Authored-By: George Kalpakas <kalpakas.g@gmail.com> PR Close #45431
2022-03-21 17:09:54 +00:00
build: Introduce Bazel build rules So far this just compiles the core and common packages.
2017-06-02 16:43:52 +00:00
package(default_visibility = ["//visibility:public"])
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768
2017-12-06 14:56:49 +00:00
build: add bazel test rules for remainder of packages (#21053) PR Close #21053
2017-12-17 23:10:54 +00:00
exports_files([
test(bazel): Build and test ts-api-guardian locally (#22544) Also use it to test the public API for core and common Once we have an ng_package for every package, we can remove the npm dependency on ts-api-guardian and the gulp-based public api check. PR Close #22544
2018-03-01 18:41:35 +00:00
"LICENSE",
build(bazel): run a number of web tests with karma_web_test in saucelabs in CircleCI (#27721) PR Close #27721
2018-12-18 06:09:39 +00:00
"karma-js.conf.js",
"browser-providers.conf.js",
build(bazel): incrementally run aio example e2e tests Replaces the workflow where all example e2es are run at once
2022-07-06 23:16:50 +00:00
YARN_PATH,
build: disable payload size uploading within bazel (#45446) Uploading payload size is unreliable from within Bazel. This is because tests might not run for every commit, tests might have been cached from a pull request RBE-build (causing payload uploading to be skipped most of the time as every change comes from a PR) We should disable the uploading as this is a fundamental problem (good thing to note now) that we can solve with better payload size tracking that we want to establish as part of dev-infra. PR Close #45446
2022-03-25 22:32:26 +00:00
"scripts/ci/bazel-payload-size.sh",
build: remove legacy integration test runner (#35985) * integration tests target definitions in integration/BUILD.bazel updated to use a single dict * payload tracking for integration tests updated to work under Bazel * legacy integration_test CI job removed * integration/run_tests.sh script no longer used in CI so it has been updated for running integration tests locally in the legacy way PR Close #35985
2020-03-10 05:17:48 +00:00
"scripts/ci/payload-size.sh",
"scripts/ci/payload-size.js",
build: remove rollup packaging from dev-infra (#35647) 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
2020-03-17 11:58:17 +00:00
"package.json",
refactor(docs-infra): refactor adev to build using architect (#53497) Refactor adev as needed to build using architect. PR Close #53497
2023-12-07 20:57:21 +00:00
"angular.json",
build: add bazel test rules for remainder of packages (#21053) PR Close #21053
2017-12-17 23:10:54 +00:00
])
build: Introduce Bazel build rules So far this just compiles the core and common packages.
2017-06-02 16:43:52 +00:00
build(bazel): create targets for aio docs tests This replaces the docs-test npm script
2022-04-27 01:14:27 +00:00
filegroup(
# filegroup is needed so that this package.json file can be a dep
# in a js_library target, which doesn't allow source file deps
name = "package_json",
srcs = ["package.json"],
)
fix(bazel): use //:tsconfig.json as the default for ng_module (#29670) This matches the behavior of ts_library PR Close #29670
2019-04-02 18:42:58 +00:00
alias(
name = "tsconfig.json",
actual = "//packages:tsconfig-build.json",
)
build: share Saucelabs browsers between karma test targets using background Saucelabs daemon and custom karma launcher (#49200) This upgrades the Saucelabs Bazel step on CI to use the more efficient Saucelabs daemon PR Close #49200
2023-02-20 20:37:34 +00:00
js_library(
name = "browser-providers",
srcs = [
"browser-providers.conf.d.ts",
"browser-providers.conf.js",
],
)
build: move _testing_init into tools; limit web_test concurrency (#21053) PR Close #21053
2017-12-18 23:37:05 +00:00
filegroup(
build(bazel): re-enable packages/upgrade/test:test_web test with static_files in ts_web_test_suite (#24214) PR Close #24214
2018-05-31 06:49:37 +00:00
name = "angularjs_scripts",
build: move _testing_init into tools; limit web_test concurrency (#21053) PR Close #21053
2017-12-18 23:37:05 +00:00
srcs = [
docs(bazel): fix typo in BUILD.bazel comments (#38054) Update BUILD.bazel PR Close #38054
2020-07-14 17:44:07 +00:00
# We also declare the unminified AngularJS files since these can be used for
build: load angular.js minified output in upgrade tests (#27711) * We should try loading Angular.JS for the upgrade tests in their minfied output. There seems to be a lot flakiness in regards to loading `AngularJS` within Travis, and the `onerror` messages aren't really too helpful. In order to reduce the payload that will be passed through the Saucelabs tunnel, we should try to load the minfied output files. PR Close #27711
2018-12-17 17:28:06 +00:00
# local debugging (e.g. see: packages/upgrade/test/common/test_helpers.ts)
build: update to rules_nodejs 0.32.2 (#31325) Brings in ts_library fixes required to get angular/angular building after 0.32.0: typescript: exclude typescript lib declarations in node_module_library transitive_declarations typescript: remove override of @bazel/tsetse (+1 squashed commit) @npm//node_modules/foobar:foobar.js labels changed to @npm//:node_modules/foobar/foobar.js with fix for bazelbuild/rules_nodejs#802 also updates to rules_rass commit compatible with rules_nodejs 0.32.0 PR Close #31325
2019-06-19 04:26:53 +00:00
"@npm//:node_modules/angular-1.5/angular.js",
"@npm//:node_modules/angular-1.5/angular.min.js",
"@npm//:node_modules/angular-1.6/angular.js",
"@npm//:node_modules/angular-1.6/angular.min.js",
test(upgrade): run tests against AngularJS v1.8.x as well (#39972) We intend to run the `@angular/upgrade` tests against all supported versions of AngularJS (v1.5+). Previously, we only ran them against v1.5, v1.6 and v1.7. Since AngularJS v1.8 was released recently, this commit adds it to the list of AngularJS versions we test against. PR Close #39972
2020-12-04 14:53:12 +00:00
"@npm//:node_modules/angular-1.7/angular.js",
"@npm//:node_modules/angular-1.7/angular.min.js",
build: update to rules_nodejs 0.32.2 (#31325) Brings in ts_library fixes required to get angular/angular building after 0.32.0: typescript: exclude typescript lib declarations in node_module_library transitive_declarations typescript: remove override of @bazel/tsetse (+1 squashed commit) @npm//node_modules/foobar:foobar.js labels changed to @npm//:node_modules/foobar/foobar.js with fix for bazelbuild/rules_nodejs#802 also updates to rules_rass commit compatible with rules_nodejs 0.32.0 PR Close #31325
2019-06-19 04:26:53 +00:00
"@npm//:node_modules/angular-mocks-1.5/angular-mocks.js",
"@npm//:node_modules/angular-mocks-1.6/angular-mocks.js",
test(upgrade): run tests against AngularJS v1.8.x as well (#39972) We intend to run the `@angular/upgrade` tests against all supported versions of AngularJS (v1.5+). Previously, we only ran them against v1.5, v1.6 and v1.7. Since AngularJS v1.8 was released recently, this commit adds it to the list of AngularJS versions we test against. PR Close #39972
2020-12-04 14:53:12 +00:00
"@npm//:node_modules/angular-mocks-1.7/angular-mocks.js",
fix(dev-infra): `ng_rollup_bundle` rule should error if import cannot be resolved (#42760) Rollup just prints a warning if an import cannot be resolved and ends up being treated as an external dependency. This in combination with the `silent = True` attribute for `rollup_bundle` means that bundles might end up being extremely small without people noticing that it misses actual imports. To improve this situation, the warning is replaced by an error if an import cannot be resolved. This unveiles an issue with the `ng_rollup_bundle` macro from dev-infra where imports in View Engine were not resolved but ended up being treated as external. This did not prevent benchmarks using this macro from working because the ConcatJS devserver had builtin resolution for workspace manifest paths. Though given the new check for no unresolved imports, this will now cause errors within Rollup, and we need to fix the resolution. We can fix the issue by temporarily enabling workspace linking. This does not have any performance downsides. To enable workspace linking (which we might need more often in the future given the linker taking over patched module resolution), we had to rename the `angular` dependency to a more specific one so that the Angular linker could link into `node_modules/angular`. PR Close #42760
2021-07-06 13:29:19 +00:00
"@npm//:node_modules/angular-mocks-1.8/angular-mocks.js",
"@npm//:node_modules/angular-1.8/angular.js",
"@npm//:node_modules/angular-1.8/angular.min.js",
build: move _testing_init into tools; limit web_test concurrency (#21053) PR Close #21053
2017-12-18 23:37:05 +00:00
],
)
build: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0 (#39182) Updates to rules_nodejs 2.2.0. This is the first major release in 7 months and includes a number of features as well as breaking changes. Release notes: https://github.com/bazelbuild/rules_nodejs/releases/tag/2.0.0 Features of note for angular/angular: * stdout/stderr/exit code capture; this could be potentially be useful * TypeScript (ts_project); a simpler tsc rule that ts_library that can be used in the repo where ts_library is too heavy weight Breaking changes of note for angular/angular: * loading custom rules from npm packages: `ts_library` is no longer loaded from `@npm_bazel_typescript//:index.bzl` (which no longer exists) but is now loaded from `@npm//@bazel/typescript:index.bzl` * with the loading changes above, `load("@npm//:install_bazel_dependencies.bzl", "install_bazel_dependencies")` is no longer needed in the WORKSPACE which also means that yarn_install does not need to run unless building/testing a target that depends on @npm. In angular/angular this is a minor improvement as almost everything depends on @npm. * @angular/bazel package is also updated in this PR to support the new load location; Angular + Bazel users that require it for ng_package (ng_module is no longer needed in OSS with Angular 10) will need to load from `@npm//@angular/bazel:index.bzl`. I investigated if it was possible to maintain backward compatability for the old load location `@npm_angular_bazel` but it is not since the package itself needs to be updated to load from `@npm//@bazel/typescript:index.bzl` instead of `@npm_bazel_typescript//:index.bzl` as it depends on ts_library internals for ng_module. * runfiles.resolve will now throw instead of returning undefined to match behavior of node require Other changes in angular/angular: * integration/bazel has been updated to use both ng_module and ts_libary with use_angular_plugin=true. The latter is the recommended way for rules_nodejs users to compile Angular 10 with Ivy. Bazel + Angular ViewEngine is supported with @angular/bazel <= 9.0.5 and Angular <= 8. There is still Angular ViewEngine example on rules_nodejs https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular_view_engine on these older versions but users that want to update to Angular 10 and are on Bazel must switch to Ivy and at that point ts_library with use_angular_plugin=true is more performant that ng_module. Angular example in rules_nodejs is configured this way as well: https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular. As an aside, we also have an example of building Angular 10 with architect() rule directly instead of using ts_library with angular plugin: https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular_bazel_architect. NB: ng_module is still required for angular/angular repository as it still builds ViewEngine & @angular/bazel also provides the ng_package rule. ng_module can be removed in the future if ViewEngine is no longer needed in angular repo. * JSModuleInfo provider added to ng_module. this is for forward compat for future rules_nodejs versions. PR Close #39182
2020-06-25 08:32:41 +00:00
# Detect if the build is running under --stamp
config_setting(
name = "stamp",
values = {"stamp": "true"},
)
build: update bazel (#45431) Update `@bazel` packages to the latest 5.x version. Some of the changes here are modeled after angular/dev-infra@40c0ac855975ce9586b07af3a36a0bf4e3b58350. Co-Authored-By: George Kalpakas <kalpakas.g@gmail.com> PR Close #45431
2022-03-21 17:09:54 +00:00
nodejs_binary(
name = "yarn_vendored",
build: update yarn (#50732) update yarn to the latest version PR Close #50732
2023-06-15 20:15:50 +00:00
data = [".yarn/releases/yarn-1.22.19.cjs"],
entry_point = ".yarn/releases/yarn-1.22.19.cjs",
build(bazel): incrementally run aio example e2e tests Replaces the workflow where all example e2es are run at once
2022-07-06 23:16:50 +00:00
visibility = [
"//aio/tools/examples/shared:__pkg__",
"//integration:__subpackages__",
],
build: update bazel (#45431) Update `@bazel` packages to the latest 5.x version. Some of the changes here are modeled after angular/dev-infra@40c0ac855975ce9586b07af3a36a0bf4e3b58350. Co-Authored-By: George Kalpakas <kalpakas.g@gmail.com> PR Close #45431
2022-03-21 17:09:54 +00:00
)
build: share Saucelabs browsers between karma test targets using background Saucelabs daemon and custom karma launcher (#49200) This upgrades the Saucelabs Bazel step on CI to use the more efficient Saucelabs daemon PR Close #49200
2023-02-20 20:37:34 +00:00
alias(
name = "sauce_connect",
actual = select({
"@npm//@angular/build-tooling/bazel/constraints:linux_x64": "@sauce_connect_linux_amd64//:bin/sc",
"@npm//@angular/build-tooling/bazel/constraints:macos_x64": "@sauce_connect_mac//:bin/sc",
"@npm//@angular/build-tooling/bazel/constraints:macos_arm64": "@sauce_connect_mac//:bin/sc",
}),
)
Reference in a new issue Copy permalink