commit | 99c6b5f74d241d42b67727724624c99d3e3bcfda | [log] [tgz] |
---|---|---|
author | alexeagle <alexeagle@google.com> | Mon Jul 08 18:05:38 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 08 18:05:56 2019 -0700 |
tree | ea9be644b4d661e01e46bfb1c23dedd5d5173b8b | |
parent | 5060a4393a8f4dc81829227101f963d3394d1eb2 [diff] |
Print a shorter error in tsc_wrapped FileCache When the TypeScript compiler tries to read a file from the cache, but the file wasn't declared as an input, this indicates a bug in the compiler. However the result is a massive data dump to the terminal, observed in e.g. https://circleci.com/gh/angular/angular/382012 To make the output less huge, only print the first 100 keys in the cache. Note that this might make it harder to debug a failure by reasoning about all the entries that *are* present in the cache, though. PiperOrigin-RevId: 257096480
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).ts_auto_deps
: a Go library and binary which generates BUILD.bazel
files from TypeScript sources.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.