Hello, and welcome to the first State of Flint blog post! These posts explain the high-level status of the Flint project - what’s been done, what’s coming up next, and what’s being pushed to the backlog. For this first post, we’ll cover progress made from Flint’s start in 2025 through the first few months of 2026.
Traditional approaches to linting TypeScript-based languages have had significant drawbacks for many years. They’re often difficult to configure and come with limitations that prevent rules from fully understanding the types of code. Flint introduces a comprehensive Volar.js-based architecture that enables fully type-aware lint rules for languages like Astro, Svelte, and Vue. 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?
