Tailwind CSS v4.1.4 — Release Notes & Engineering Impact

Source available — automated, not human-reviewed

Component: tailwind · Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified — check source notes

$ npm install --save-exact [email protected]

📄 .MD

✨ Features 1 🔧 Bug Fixes 6

⚡ Executive Summary (TL;DR)

Tailwind CSS v4.1.4. Source highlight: Add experimental `@tailwindcss/oxide-wasm32-wasi` target for running Tailwind in browser environments like StackBlitz (#17558)

Visit Tailwind CSS Official Site ↗ Official Release Source ↗ All Tailwind CSS Releases 📡 Tailwind CSS RSS

Who Does This Impact? (Role-Based Analysis)

💻 Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

📊 Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

⚙️ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

✨ New Features & Capabilities (1)

Add experimental `@tailwindcss/oxide-wasm32-wasi` target for running Tailwind in browser environments like StackBlitz (#17558)

🔧 Bug Fixes & Patches (6)

Ensure `color-mix(…)` polyfills do not cause used CSS variables to be removed (#17555)
Ensure `color-mix(…)` polyfills create fallbacks for theme variables that reference other theme variables (#17562)
Fix brace expansion in declining ranges like `{10..0..5}` and `{0..10..-5}` (#17591)
Work around a Chrome rendering bug when using the `skew-*` utilities (#17627)
Ensure container query variant names can contain hyphens (#17628)
Ensure `shadow-inherit`, `inset-shadow-inherit`, `drop-shadow-inherit`, and `text-shadow-inherit` inherit the shadow color (#17647)

📄 View Raw Release Notes (Original Developer Log)

### Added - Add experimental `@tailwindcss/oxide-wasm32-wasi` target for running Tailwind in browser environments like StackBlitz ([#17558](https://github.com/tailwindlabs/tailwindcss/pull/17558)) ### Fixed - Ensure `color-mix(…)` polyfills do not cause used CSS variables to be removed ([#17555](https://github.com/tailwindlabs/tailwindcss/pull/17555)) - Ensure `color-mix(…)` polyfills create fallbacks for theme variables that reference other theme variables ([#17562](https://github.com/tailwindlabs/tailwindcss/pull/17562)) - Fix brace expansion in declining ranges like `{10..0..5}` and `{0..10..-5}` ([#17591](https://github.com/tailwindlabs/tailwindcss/pull/17591)) - Work around a Chrome rendering bug when using the `skew-*` utilities ([#17627](https://github.com/tailwindlabs/tailwindcss/pull/17627)) - Ensure container query variant names can contain hyphens ([#17628](https://github.com/tailwindlabs/tailwindcss/pull/17628)) - Ensure `shadow-inherit`, `inset-shadow-inherit`, `drop-shadow-inherit`, and `text-shadow-inherit` inherit the shadow color ([#17647](https://github.com/tailwindlabs/tailwindcss/pull/17647)) - Ensure compatibility with array tuples used in `fontSize` JS theme keys ([#17630](https://github.com/tailwindlabs/tailwindcss/pull/17630)) - Ensure folders with binary file extensions in their names are scanned for utilities ([#17595](https://github.com/tailwindlabs/tailwindcss/pull/17595)) - Upgrade: Convert `fontSize` array tuple syntax to CSS theme variables ([#17630](https://github.com/tailwindlabs/tailwindcss/pull/17630))

← Older Version Tailwind CSS v4.1.3 Newer Version → Tailwind CSS v4.1.5