commit | fe53ee0498dd7cd96b5538a2219c9557209fa250 | [log] [tgz] |
---|---|---|
author | alexeagle <alexeagle@google.com> | Tue Sep 17 09:25:59 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 17 09:26:20 2019 -0700 |
tree | 766b554065047bf0e44063a6338a8a8689825f78 | |
parent | 42049c24c72493a35d52ae6f4786bfd89d4835fb [diff] |
Fix ts_library to produce files that rollup knows how to find. Currently we produce .closure.js files with ESModules, this naming convention was chosen arbitrarily to indicate we expected these to be inputs to closure compiler. However other bundlers don't understand this convention and cannot find their inputs. Today we work around this by copying a bunch of files around before running rollup, but this is a performance issue we can avoid just by naming our outputs in the standard way for esmodules. PiperOrigin-RevId: 269585536
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.