angular/modules/benchmarks/src
Paul Gschwendtner 9d7768ccd6 build: rework benchmarks and examples in modules/ to new optimization rule (#61566)
We are dropping the custom ESBuild and Terser pipeline from dev-infra
and instead leverage the Angular CLI directly. This commit adjusts
the benchmarks to use this new rule.

PR Close #61566
2025-05-29 14:39:11 -04:00
..
change_detection build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
class_bindings build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
defer build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
expanding_rows build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
hydration build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
js-web-frameworks build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
largeform build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
largetable build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
ng_template_outlet_context build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
styling build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
tree build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
BUILD.bazel build: rework benchmarks and examples in modules/ to new optimization rule (#61566) 2025-05-29 14:39:11 -04:00
README.md build(bazel): //modules/benchmarks/src/largetable/render3:perf bazel protractor test (#24788) 2018-07-24 08:26:16 -07:00
util.ts refactor: remove unnecessary TSLint rule flags (#59365) 2025-01-07 16:06:21 +00:00

Benchmark Directory Layout

Bazel

Under bazel the rules for laying out test files are slightly different. Use largetable/render3 as an example.

Put the perf file in current subdirectory (ie largetable) such that the same perf file can be used for each of the sub-subdirectories. (ie largetable/* should all be testable with the same perf file largetable/largetable_perf.spec.ts). Under bazel, typescript protractor spec files must end with .spec.ts or .test.ts.