v4.1.18
📦 tailwind-cssView on GitHub →
✨ 5 features🐛 11 fixes🔧 9 symbols
Summary
This release focuses on bug fixes and stability improvements for the CLI, Vite plugin, and JS configuration compatibility. Key updates include better CSS error reporting, source map fixes in watch mode, and improved canonicalization of utility classes.
✨ New Features
- Support environment API in @tailwindcss/vite
- Include filename and line numbers in CSS parse errors
- Preserve case of theme keys from JS configs and plugins
- Handle future and experimental config keys during upgrade
- Canonicalization: combine text-* and leading-* classes
🐛 Bug Fixes
- Ensure validation of source(…) happens relative to the file it is in
- Skip comments in Ruby files when checking for class names
- Skip over arbitrary property utilities with a top-level ! in the value
- Write source maps correctly on the CLI when using --watch
- Handle special defaults (like ringColor.DEFAULT) in JS configs
- Improve backwards compatibility for content theme key from JS configs
- Try to canonicalize any arbitrary utility to a bare value
- Validate candidates similarly to Oxide
- Correctly handle duplicate CLI arguments
- Don’t emit color-mix fallback rules inside @keyframes
- CLI: Don't hang when output is /dev/stdout
🔧 Affected Symbols
source()@tailwindcss/viteringColor.DEFAULTcontenttext-*leading-*@keyframesfutureexperimental