Tailwind CSS

Why it's ranked here

Most styling libraries stop at a build plugin. This one ships a Rust crate whose only job is reading source files and pulling class candidates out of raw bytes, with parallel sorting and per-file modification times so repeat builds skip untouched files. Separate adapters for the command line, PostCSS, Vite, webpack, Turbopack and the browser all drive one compiler. That breadth is the cost too: the integration surface is wide and each adapter caches differently. The scanning contract is explicit rather than implicit magic, and for a dependency this central that legibility is worth the wide surface.

What's good

Incremental work is handled at both ends. The PostCSS adapter bails out early when a stylesheet contains none of the at-rules it handles, keeps compilers in a bounded cache keyed by input file, and only rebuilds fully when a tracked file's modification time changes. The scanner keeps a set of candidates it has already seen and returns only new ones. The browser build watches the document and rebuilds incrementally when class attributes change. Integration tests exercise real bundlers rather than mocks: Vite, webpack, Turbopack, Astro, Nuxt, Svelte, Qwik and Solid each get their own suite.

Tradeoffs

Extraction is heuristic, not semantic. The scanner reads bytes and accepts anything shaped like a class, so ordinary words in your source can become candidates and generate rules you never asked for. The browser build refuses plugins and configuration files outright, throwing on any import it does not recognise, so it is a different product from the build-time path. In the upgrade command, the dependency update step catches every error and discards it silently, and stylesheet migration failures are printed but the run continues, which can leave a project half migrated.

How to use it well

Reach for it when a team needs one shared styling vocabulary across many components and wants the design tokens to live in a stylesheet rather than a configuration module. Pick the adapter that matches your build: the bundler plugins for apps, the command line binary for pipelines that only produce CSS, the in-page script for demos and prototypes. It does not give you components, accessibility behaviour or state management, so pair it with a headless component library. Before upgrading a major version, commit first: the migration tool rewrites your stylesheets and templates in place.

Observed

License

MIT, Tailwind Labs

Languages

TypeScript and Rust

Interfaces

CLI, PostCSS plugin, Vite plugin, webpack and Turbopack loaders, in-browser script, standalone binary

Configuration

CSS at-rules in the input stylesheet, no JavaScript config file required

Repo layout

pnpm workspace of packages over a Cargo workspace of crates

Migration path

bundled upgrade command that runs stylesheet, config and template codemods

Scanning

filesystem walk that honours gitignore rules, with incremental rescans

Test surface

integration suites that build against real bundlers and frameworks