| commit | 9bde60b23f0f21f4152b15cce6bf3d66d8448a02 | [log] [tgz] |
|---|---|---|
| author | alexeagle <alexeagle@google.com> | Wed Feb 12 13:32:58 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 12 13:33:18 2020 -0800 |
| tree | 228ba6f35264d054aabbe3623b89aec0b2cd0d59 | |
| parent | b16833abc627282733650c0ce2011aa20df58acb [diff] |
Switch tsc_wrapped to a .js entry point This lets it work under the linker, where the execpath to the .js file is hard to calculate from the .ts input file path. This also wires up the ts-lit-plugin under Bazel if it appears in the tsconfig settings. Closes #490 PiperOrigin-RevId: 294743226
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.