No description
2b9a5c4112
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 |
||
|---|---|---|
| .github | ||
| crates | ||
| integrations | ||
| packages | ||
| patches | ||
| playgrounds | ||
| scripts | ||
| .gitignore | ||
| .prettierignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| rust-toolchain.toml | ||
| turbo.json | ||
| vitest.config.mts | ||
A utility-first CSS framework for rapidly building custom user interfaces.
Documentation
For full documentation, visit tailwindcss.com.
Community
For help, discussion about best practices, or feature ideas:
Discuss Tailwind CSS on GitHub
Contributing
If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.