Full Byte Developer.

Compare tsrs with your existing TypeScript check

Try the experimental Rust port without replacing the compiler that currently validates your project.

Originally posted · Published here · 1 source

Cloudflare describes tsrs as an experimental Rust port developed with VoidZero and Max Schwenk in collaboration with the TypeScript team. Its announcement reports benchmark improvements against TypeScript 7.0, with matching worker configurations. [1]

Those results do not measure your project. Keep your existing type check while evaluating the port.

Try it in an isolated checkout

Cloudflare documents these commands: [1]

bash
npm install tsrs
npx tsrs

The install changes the project's dependencies. Use a branch or disposable checkout so you can review that change separately.

Compare results before speed

Run your existing check and tsrs on the same revision. Compare the diagnostics and exit status before comparing elapsed time. Use the same machine and worker settings for repeated measurements.

The announcement notes behavioral differences such as diagnostic ordering and discusses ongoing work toward matching upstream TypeScript. [1] Record any difference that affects your build. Keep the established compiler in CI until you have resolved it.

Keep this guide

By Full Byte Developer

Original post: Instagram post

Filed under Dev tools

Sources

  1. Cloudflare introduces tsrsblog.cloudflare.com

Next in this stack