Porting 600KLOC of Closure Compiler JS to typescript: https://www.lucidchart.com/techblog/2017/11/16/converting-600k-lines-to-typescript-in-72-hours/
Although Closure offers a set of static analysis tools, typescript is often stricter! This finds bugs but complicates porting.
Related Posts
Delighted to see that Typescript 7 is moving to conventional LSP for its IDE services!
https://devblogs.microsoft.com/typescript/progress-on-typescript-7-december-2025/#resetting-language-service-issues
I've been building an 'extract function' refactor feature. It's surprisingly nuanced.
Where do you put the extracted function? Once you've done the static analysis, what order do you use for the parameters?
One interesting consequence of the rise of LLMs: there's more demand for tools that handle untrusted input.
Arbitrary HTML+JS can be safely run in a browser. Lean can check an arbitrary proof.
These work really well with an LLM that can be wrong, but sometimes gives exactly what you want. Are there other tools in this family?