|author||TypeScript Team <email@example.com>||Tue Jan 28 11:14:23 2020 -0800|
|committer||Copybara-Service <firstname.lastname@example.org>||Tue Jan 28 11:14:46 2020 -0800|
Improve formatting of cyclical dependency error reporting This adds a line break between dependencies, since each line tends to be very long. It's easier to understand the cycle if the actual file names are grouped closer together into a column. This change adds a newline between each dependency in the cycle to better achieve that. It also adds space between the stacktrace below and the context above. Previously: Compilation failed Error: Cyclical dependency between files: src/b.ts -> src/a.ts -> src/b.ts Now: Compilation failed Error: Cyclical dependency between files: src/b.ts -> src/a.ts -> src/b.ts PiperOrigin-RevId: 291974463
This repo contains a mirror of some Google-internal bits that support TypeScript development under Bazel.
It contains these utilities:
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
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.