Hacker News Reader

We are working on this here:

It's already used within Google to effectively optimize TypeScript apps. However, someone still needs to write the integrations between tsickle and the multitude of public JS build systems and there's not a lot of pressure on me to do it (I have lots of other work to do).

View on HN

Oh yes, I've been following this, at least the bits of information that emerge publicly.

But my dream is that this work could make it back into typescript itself - that a future version could possibly be persuaded to emit Closure type limitations without the help of a parallel/postprocessing pass by a tool.

I wonder if that would that change your workflow in any way? Usually people use typescript compiler to compile TS into JS and usually it's being executed by some runner (grunt, gulp, bazel...). Adding tsickle + closure compiler to the process should be essentially just adding couple of lines in the build process. I agree that it may be slower and have bugs - is that the worry?

Reply on news.ycombinator.com