No description
26fcae0e1a
Shutdown captured the swap promise once, so it waited for whichever swap was current when stdin closed. A rebuild already in flight can start its own swap after that point, and the queue was then closed while the later one was still flushing — the same dropped changes, one interleaving further out. Read the current swap each time round instead, until it stops changing. The regression test drives that interleaving directly: it replaces the swap while shutdown is already waiting, and asserts the queue stays open until the later one has flushed. Against capture-by-value the queue is already closed with only the first swap's work landed. 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.