interoperate with rules_closure

[yohcop]

It would be nice to have a ts_binary rule that turns ts_libraries into a single .js file.
Unless I miss something and there's already a way to do this?

Maybe with bazelbuild/rules_closure, it would be possible to optimized the output code using closure_js_binary.

[alexeagle]

right, we plan to re-use the closure compiler rules to get a single bundle file

[yohcop]

As a first approximation, would adding a outputFile option in a generated tsconfig file be possible?

[alexeagle]

I think we more commonly want some other bundling tool that knows how to flatten modules, like rollup. @robwormald might look into it next week, angular and ngrx need it soon.

[achew22]

Any luck on this? Feel free to ping me internally if there is any 20% stuff I can do to help 😄

[achew22]

I have a semi-working prototype but it requires google/closure-compiler#2641 to be submitted (at a minimum) due to google/closure-compiler#2637 which lines up with the timeline that Alex was talking about with the es6 module import issue

[unlikely-leo]

Hi there, we're looking into using Bazel for our mixed TS/JS codebase at the moment. Interoperability with the Closure rules to build minified bundles is definitely a key aspect of making that work. It's great to see that this is being worked on!

@achew22 could you clarify what timelines you were referring to in your comment?

[achew22]

@alexeagle looks like the snapshot build of Closure compiler now has the fix for deterministic ordering. Does that mean we can actually do this?

[alexeagle]

Sure, you can pick up from https://github.com/alexeagle/rules_typescript/tree/closure_js_binary?files=1
And just point to the new snapshot build?

[alexeagle]

I think closure compiler is released now, so someone could pick this up.