tailwindcss/packages/@tailwindcss-cli/src
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
..
commands Add a regression test for the newest change winning 2026-08-31 15:24:27 +02:00
utils Fix overlapping CLI watch rebuilds 2026-08-31 14:34:34 +02:00
index.ts Add --poll option to @tailwindcss/cli (#20297) 2026-07-01 21:25:26 +02:00