angular-cn/modules/benchmarks
Kara Erickson 0de2a5e408 refactor(core): rename ngFactoryDef to ɵfac (#33116)
Factory defs are not considered public API, so the property
that contains them should be prefixed with Angular's marker
for "private" ('ɵ') to discourage apps from relying on def
APIs directly.

This commit adds the prefix and shortens the name from
ngFactoryDef to fac. This is because property names
cannot be minified by Uglify without turning on property
mangling (which most apps have turned off) and are thus
size-sensitive.

Note that the other "defs" (ngPipeDef, etc) will be
prefixed and shortened in follow-up PRs, in an attempt to
limit how large and conflict-y this change is.

PR Close #33116
2019-10-14 20:27:25 +00:00
..
e2e_test/old build: convert largeform benchmarks to bazel (#28645) 2019-02-13 12:15:01 -08:00
src refactor(core): rename ngFactoryDef to ɵfac (#33116) 2019-10-14 20:27:25 +00:00
BUILD.bazel build: update instructions to run benchmark tests (#28645) 2019-02-13 12:15:01 -08:00
README.md build: update instructions to run benchmark tests (#28645) 2019-02-13 12:15:01 -08:00
benchmark_test.bzl refactor(bazel): remove @angular/bazel protractor rule now provided by @bazel/protractor (#32485) 2019-09-10 15:19:31 -04:00
start-server.js build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) 2019-07-26 15:01:25 -07:00
tsconfig-build.json build: serve benchmark tree examples with bazel (#28568) 2019-02-08 13:37:36 -08:00
tsconfig-e2e.json build: convert largeform benchmarks to bazel (#28645) 2019-02-13 12:15:01 -08:00

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.