No description
This PR ignores Lightning CSS warnings for the unknow at-rule `@position-try`. This is a temporary fix/workaround until support for `@position-try` lands in Lightning CSS: https://github.com/parcel-bundler/lightningcss/pull/1238 Fixes: #20275 ## Test plan Ran a test based on the issue: Before: ```shellsession ❯ tw -i x.css -o out.css --optimize ≈ tailwindcss v4.3.1 Found 1 warning while optimizing generated CSS: │ position-try-fallbacks: --flip-above; │ } │ @position-try --flip-above { ┆ ^-- Unknown at rule: @position-try ┆ │ top: auto; │ bottom: 0; Done in 29ms ``` After: ```shellsession ❯ tw -i x.css -o out.css --optimize ≈ tailwindcss v4.3.1 Done in 14ms ``` |
||
|---|---|---|
| .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.ts | ||
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.