955423c79b
Under bazel and Ivy we don't need the shim files to be emmited by default. We still need to the shims for blaze however because google3 code imports them. This improves build latency by 1-2 seconds per ng_module target. PR Close #33765 |
||
|---|---|---|
| .. | ||
| e2e_test/old | ||
| src | ||
| BUILD.bazel | ||
| README.md | ||
| benchmark_test.bzl | ||
| start-server.js | ||
| tsconfig-build.json | ||
| tsconfig-e2e.json | ||
README.md
How to run the benchmarks locally
Run in the browser
yarn bazel run modules/benchmarks/src/tree/{name}:devserver
# e.g. "ng2" tree benchmark:
yarn bazel run modules/benchmarks/src/tree/ng2:devserver
Run e2e tests
# Run e2e tests of individual applications:
yarn bazel test modules/benchmarks/src/tree/ng2/...
# Run all e2e tests:
yarn bazel test modules/benchmarks/...
Use of *_aot.ts files
The *_aot.ts files are used as entry-points within Google to run the benchmark
tests. These are still built as part of the corresponding ng_module rule.