| commit | 270b8689c52c4c67e4f164471f5749ba40015904 | [log] [tgz] |
|---|---|---|
| author | Alex Eagle <eagle@post.harvard.edu> | Tue Mar 19 09:36:31 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 19 09:36:49 2019 -0700 |
| tree | 2a0338b50ee33b9a6b678c982d51cfe779ee294e | |
| parent | 68739d9ccbf100bb134a50b11250fea48a9705d5 [diff] |
Use the canonical name for JS modules in node_modules Closes #438 PiperOrigin-RevId: 239207994
Looking for documentation for TypeScript bazel rules that used to be here? See https://npmjs.com/package/@bazel/typescript
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.