| commit | bad5a075147b13faa7140213a7fd18065eb8d8e4 | [log] [tgz] |
|---|---|---|
| author | evanm <evanm@google.com> | Fri Feb 21 11:19:02 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Feb 21 11:19:18 2020 -0800 |
| tree | 1e588ceee7da7f2abf48786c18b911992f32a7ce | |
| parent | 816b8dda52ffc59506d26724645ddd5d2da61655 [diff] |
don't stat() all input files As part of transpilation we might receive directories as input files. To check, we tested each file for whether it was a directory or not. This disk access evaded our various caches. To fix: 1. only check for directories in transpilation; 2. when checking for directories, assume names ending in sourc file extensions like ".js" are not directories. PiperOrigin-RevId: 296473783
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.