tailwindcss

History

Michael Glass 2b9a5c4112 Add a regression test for the newest change winning The existing tests cover the scheduling: serial-batches asserts that only one rebuild runs at a time, and the watcher tests cover event filtering and shutdown flushing. Neither asserts the outcome the bug was reported as — that what ends up written is the newest change. This drives the watcher wiring with an older change whose rebuild is slow and a newer change whose rebuild is fast, and asserts the newer result is written last. Against the previous fire-and-forget behaviour the two rebuilds overlap and the stale one lands on top, so the test fails. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lcj4iQ3fBxMwAu2rf4zLbC		2026-08-31 15:24:27 +02:00
..
src	Add a regression test for the newest change winning	2026-08-31 15:24:27 +02:00
package.json	Bump dependencies (#20381 )	2026-08-04 13:55:03 +02:00
README.md	docs: update package README CI badge to main (#19692 )	2026-02-18 11:52:07 +01:00
tsconfig.json	Move the CLI to its own package `@tailwindcss/cli` (#13095 )	2024-03-06 05:41:12 -05:00
tsup.config.ts	Resolve `@import` in core (#14446 )	2024-09-23 17:05:55 +02:00

A utility-first CSS framework for rapidly building custom user interfaces.

Documentation

For full documentation, visit tailwindcss.com.

For help, discussion about best practices, or feature ideas:

If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.