The traditional ESLint approach to linting TS-based languages has been a pain for a very long time. It is hard to configure, and it has a lot of limitations that don’t allow type-aware rules to work as well as they should. Learn how Flint’s architecture solves this once and for all!
Flint is an experimental linter. It intentionally revisits many of the core design decisions from other popular web linters. This post covers the categories of changes and each high-level change’s hypothesis.
ESLint has been the leading web ecosystem linter for a decade. Its dominance is being challenged by new native speed linters such as Biome and Oxlint that implement blazing fast linting using native speed languages. Even TypeScript’s source is being ported from TypeScript to Go. Yet, this Flint project -a new, experimental linter- is implemented in TypeScript rather than Go or Rust. Why does Flint exist when there are so many other linters already, and why is it implemented the way it is?
