FRONTEND
Tailwind CSS v4.1.18
RESUMEN
Fixed - Ensure validation of `source(…)` happens relative to the file it is in - Include filename and line numbers in CSS parse errors - Skip comments in Rub
Descripción Detallada
Fixed - Ensure validation of `source(…)` happens relative to the file it is in - Include filename and line numbers in CSS parse errors - Skip comments in Ruby files when checking for class names - Skip over arbitrary property utilities with a top-level `!` in the value - Support environment API in `@tailwindcss/vite` - Preserve case of theme keys from JS configs and plugins - 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 - Upgrade: Handle `future` and `experimental` config keys - Try to canonicalize any arbitrary utility to a bare value - Validate candidates similarly to Oxide ([#193
Actualización de correcciones y mejoras en Tailwind CSS v4.1.18.
- Validación de `source(…)` ahora es relativa al archivo correspondiente.
- Errores de análisis CSS incluyen nombre de archivo y números de línea.
- Se omiten comentarios en archivos Ruby al verificar nombres de clase.
- Mejoras en la compatibilidad y manejo de configuraciones en JS.
A quién le importa
Todos los que usan Tailwind CSS.
Generado por IA · puede contener errores
Releases Relacionados
FRONTEND
Tailwind CSS v4.2.4
### Fixed - Ensure imports in `@import` and `@plugin` still resolve correctly when using Vite aliases in `@tailwindcss/vite` ([#19947](https://github.com/tailwindlabs/tailwindcss/pull/19947))
FRONTEND
Tailwind CSS v4.2.3
### Fixed - Canonicalization: improve canonicalizations for `tracking-*` utilities by preferring non-negative utilities (e.g. `-tracking-tighter` → `tracking-wider`) ([#19827](https://github.com/tailwindlabs/tailwindcss/pull/19827)) - Fix crash due to invalid characters in candidate (exceeding v