| commit | acb63cc62e7197aa6a659f89ea6ce79398e5b3fd | [log] [tgz] |
|---|---|---|
| author | TypeScript Team <noreply@google.com> | Thu Apr 04 07:26:47 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 04 07:27:05 2019 -0700 |
| tree | 7119730264fb0f9a7514b4e39e6d34eb00520476 | |
| parent | ad940da7349e824f69c3d40e66ec4f6060f5a9ef [diff] |
Add a fix to the error reporting mechanism in Tsetse. I forgot that Rules don't generate their own Failures... Now there's a way to get a Fix in, though it's still not consumed. PiperOrigin-RevId: 241926568
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.