Skip to content

Explain closure_ts_compile.deps #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pcj merged 1 commit into from
Oct 5, 2025
Merged

Explain closure_ts_compile.deps #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,11 +44,15 @@ closure_ts_compile(
- download npm deps and prepare the `js_binary` tsickle runner
(`//tools/tsicklecompiler`).
- run the tool, which roughly works as follows:
- prepare in internal/minimal `tsconfig.json` configuration.
- prepare an internal/minimal `tsconfig.json` configuration.
- runs `tsc` over the inputs to generate a `ts.Program`
- runs tsickle over the `ts.Program` to AST-rewrite/transform it.
- emits the transformed `.js` files.
- output files:
- each `{basename}.ts` will produce an equivalent `{basename}.js` file
- if any `.d.ts` files are present, a single `{name}-externs.js` file will be
produced.

`closure_ts_compile` can take `deps` on other `closure_ts_compile` rules. The
source `.ts` files will be made available to `tsc`. Only direct `.ts` files in
the primary rule will emitted.
Loading