iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/dev-infra/benchmark/driver-utilities/BUILD.bazel

21 lines
610 B
Python
Raw Normal View History

revert: "feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)" (#36798) This reverts commit b7f2a033df47080084e73340f25286c8ec1a419a. PR Close #36798
2020-04-24 13:26:36 -04:00
package(default_visibility = ["//visibility:public"])
feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434) * Move tools/brotli-cli, tools/browsers, tools/components, tools/ng_rollup_bundle, and modules/e2e_util to dev-infra/benchmarking * Fix imports and references to moved folders and files * Set up BUILD.bazel files for moved folders so they can be packaged with dev-infra's :npm_package PR Close #36434
2020-04-22 12:41:04 -04: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 04:32:41 -04:00
load("@npm//@bazel/typescript:index.bzl", "ts_library")
revert: "revert: "feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)" (#36798)" (#36800) This reverts commit ad8c4cdd752d310316e8fc019f21855701c3a950. PR Close #36800
2020-04-24 16:14:28 -04:00
build(bazel): //modules/benchmarks/src/largetable/render3:perf bazel protractor test (#24788) PR Close #24788
2018-07-06 18:42:07 -04:00
ts_library(
revert: "revert: "feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)" (#36798)" (#36800) This reverts commit ad8c4cdd752d310316e8fc019f21855701c3a950. PR Close #36800
2020-04-24 16:14:28 -04:00
name = "driver-utilities",
build(bazel): //modules/benchmarks/src/largetable/render3:perf bazel protractor test (#24788) PR Close #24788
2018-07-06 18:42:07 -04:00
srcs = glob(["*.ts"]),
refactor(dev-infra): small changes and fixes (#36800) Rename bazel workspace from npm_dev_infra to npm_angular_dev_infra_private to make it clear that this package is private to angular. Change driver-utilities module_name to match the new bazel workspace name. Correct a comment by rewording it from "deployed version" to "published version". Fix merge conflicts in tmpl-package.json Make "//packages/bazel/src:esm5.bzl" replacement more generalized so that importing from "//packages/bazel" works. Deleted "dev_infra/*" path from modules/benchmarks tsconfig. Moved //dev-infra/benchmark/browsers to //dev-infra/browsers. PR Close #36800
2020-05-08 15:56:39 -04:00
module_name = "@angular/dev-infra-private/benchmark/driver-utilities",
revert: "revert: "feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)" (#36798)" (#36800) This reverts commit ad8c4cdd752d310316e8fc019f21855701c3a950. PR Close #36800
2020-04-24 16:14:28 -04:00
tsconfig = "//dev-infra/benchmark/component_benchmark:tsconfig-e2e.json",
build(bazel): //modules/benchmarks/src/largetable/render3:perf bazel protractor test (#24788) PR Close #24788
2018-07-06 18:42:07 -04:00
deps = [
"//packages/benchpress",
revert: "revert: "feat(dev-infra): exposed new rule 'component_benchmark' via dev_infra (#36434)" (#36798)" (#36800) This reverts commit ad8c4cdd752d310316e8fc019f21855701c3a950. PR Close #36800
2020-04-24 16:14:28 -04:00
"@npm//@types/node",
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871
2019-02-20 12:54:42 -05:00
"@npm//@types/selenium-webdriver",
refactor(dev-infra): use shelljs instead of fs-extra for benchmark utils (#37594) We added a new dependency on `fs-extra` to the dev-infra package. We can remove this dependency and replace it with `shelljs` that is extensively used in other places already. The motiviation is that we can reduce dependencies needed for for consumption of the shared dev-infra package. PR Close #37594
2020-06-15 16:10:20 -04:00
"@npm//@types/shelljs",
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871
2019-02-20 12:54:42 -05:00
"@npm//node-uuid",
"@npm//protractor",
"@npm//selenium-webdriver",
refactor(dev-infra): use shelljs instead of fs-extra for benchmark utils (#37594) We added a new dependency on `fs-extra` to the dev-infra package. We can remove this dependency and replace it with `shelljs` that is extensively used in other places already. The motiviation is that we can reduce dependencies needed for for consumption of the shared dev-infra package. PR Close #37594
2020-06-15 16:10:20 -04:00
"@npm//shelljs",
build(bazel): //modules/benchmarks/src/largetable/render3:perf bazel protractor test (#24788) PR Close #24788
2018-07-06 18:42:07 -04:00
],
)