angular-cn/packages/bazel/test/protractor-2/tsconfig.json

{
  "compilerOptions": {
    "lib": ["dom", "es2015"],
    "types": []
  }
}
feat(bazel): protractor_web_test_suite for release (#24787) PR Close #24787 2018-07-06 17:51:37 -04:00			`{`
			`"compilerOptions": {`
build(bazel): use fine-grained npm deps (#26111) (#26488) PR Close #26488 2018-10-04 16:14:14 -04:00			`"lib": ["dom", "es2015"],`
test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags (#26471) We are close enough to blacklist a few test targets, rather than whitelist targets to run... Because bazel rules can be composed of other rules that don't inherit tags automatically, I had to explicitly mark all of our ts_library and ng_module targes with "ivy-local" and "ivy-jit" tags so that we can create a query that excludes all fixme- tagged targets even if those targets are composed of other targets that don't inherit this tag. This is the updated overview of ivy related bazel tags: - ivy-only: target that builds or runs only under ivy - fixme-ivy-jit: target that doesn't yet build or run under ivy with --compile=jit - fixme-ivy-local: target that doesn't yet build or run under ivy with --compile=local - no-ivy-jit: target that is not intended to build or run under ivy with --compile=jit - no-ivy-local: target that is not intended to build or run under ivy with --compile=local PR Close #26471 2018-10-16 02:24:22 -04:00			`"types": []`
feat(bazel): protractor_web_test_suite for release (#24787) PR Close #24787 2018-07-06 17:51:37 -04:00			`}`
			`}`