| commit | 331ee29d69f60ff8e6296eb1d618d5433d746085 | [log] [tgz] |
|---|---|---|
| author | evanm <evanm@google.com> | Tue Feb 18 11:00:44 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Feb 18 11:01:04 2020 -0800 |
| tree | 0dd1204821a2fb7fb624855b4cae84f7b740ecd3 | |
| parent | cd559f4e8b30a5be975c0730211d1ca18a3fbcd3 [diff] |
construct plugins just before using them The common plugins includes the tsetse plugin, which grabs the Program's TypeChecker as part of its construction, which causes TS to do a bunch of work. By moving the plugin construction here, that work happens in the code above (where we explicitly ask TS for diagnostics), which makes perf trace accounting for type checking more accurate. PiperOrigin-RevId: 295773738
This repo contains a mirror of some Google-internal bits that support TypeScript development under Bazel.
It contains these utilities:
ts_devserver: a Go library and binary that runs a fast local web server which concatenates JavaScript on-the-fly. It requires inputs in a named module format (module ids must be contained in the file, not inferred from the file's path).tsc_wrapped: a TypeScript program which wraps the TypeScript compiler, hosting it under a Bazel worker.tsetse: a collection of third-party “strictness” checks which we add to the TypeScript compiler.internal/common/*.bzl: some Starlark utility code for running the ts_library rule.There are no user-facing bits in this repo. These utilities are consumed in https://github.com/bazelbuild/rules_nodejs/tree/master/packages/typescript
Please file issues for ts_library rule and other Bazel rules in that repo.