TL;DR

A typical TypeScript project runs tsc for type checking, then runs eslint again for code style.

@ttsc/lint collapses those two steps into a single compile pass . Lint violations come out as plain compile errors.

It's built on typescript-go (the next-generation TS compiler rewritten in Go, about 10x faster than legacy tsc ), and reuses the AST the compiler already builds — so there is no extra parsing cost .

Combine "two steps into one" with "JavaScript moved to Go," and you get about 20x faster, in theory .

Compatible with TypeScript v6 — drop on top with ttsx or ttsc --noEmit , no migration.

GitHub Repository:

https://github.com/samchon/ttsc

https://github.com/samchon/ttsc/tree/master/packages/lint

1. The thing every TypeScript developer does twice a day

If you've ever set up a TypeScript project, this pair of commands will look familiar.

# Are the types correct? tsc --noEmit

# Is the code style okay?…