mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00

Files

T

Greg Magolan d91ecd2c8b build: update to rules_typescript 0.25.1 (#28896 )

* build_bazel_rules_typescript renamed to npm_bazel_typescript
* build_bazel_rules_karma renamed to npm_bazel_karma
* browser_repositories.bzl removed and now using @npm_bazel_karma//:browser_repositories.bzl
* includes some fixes for future ts_library devmode es2015 support but some failure still remain when devmode is es2015 so this PR keeps it as es5 using the bazelOptions.devmodeTargetOverride tsconfig setting

PR Close #28896

2019-02-22 12:18:59 -08:00

largeform

build: update to rules_typescript 0.25.1 (#28896 )

2019-02-22 12:18:59 -08:00

largetable

build: update to rules_typescript 0.25.1 (#28896 )

2019-02-22 12:18:59 -08:00

old

…

tree

build: update to rules_typescript 0.25.1 (#28896 )

2019-02-22 12:18:59 -08:00

bootstrap_ng2.ts

…

bootstrap_plain.ts

…

BUILD.bazel

build: run tree benchmark tests with bazel (#28568 )

2019-02-08 13:42:00 -08: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

…

README.md

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.