| commit | a82986561fbc78465957c6b46a87e61f26f931d8 | [log] [tgz] |
|---|---|---|
| author | Alex Eagle <eagle@post.harvard.edu> | Tue Mar 12 11:02:07 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 12 11:03:30 2019 -0700 |
| tree | d605c7eff742216bfc4b53b175e50a6dd5360798 | |
| parent | 2cd949c016fc52c500970a6c66a121b54215a56f [diff] |
Fix downstream @bazel/typescript package It was picking up a build file containing a rules_go dependency. This was caught by our new Renovate setup which sent a red PR: https://circleci.com/gh/bazelbuild/rules_nodejs/5625#tests/containers/3 Closes #437 PiperOrigin-RevId: 238052911
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.