# tailwindlabs/tailwindcss · RepoSense Release & Migration Intelligence

> Canonicalization: improve performance in projects with man. Drop-in upgrade. Migration: None.

## Metadata
- **Repository URL**: https://github.com/tailwindlabs/tailwindcss
- **Primary Package**: `tailwindcss` (NPM)
- **Categories**: `STYLING`, `BUILD_TOOL`
- **Latest Version**: `v4.3.5`
- **Semantic Status**: `COMPATIBLE`
- **Bundle Size Impact (oxide-engine)**: `+0.1 kB (+0.2%)`
- **Atom Ingestion Feed**: https://github.com/tailwindlabs/tailwindcss/releases.atom

## The Human Context (Plain-English Pitch)
Tailwind CSS is a utility-first styling framework that lets you design components directly in your HTML or JSX using small, composable class names. It removes the pain of inventing CSS class names, switching between files, and fighting unintended style overrides as your project grows.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
Canonicalization: improve performance in projects with man. Drop-in upgrade. Migration: None.

## Breaking Changes & Required Actions
- Canonicalization: improve performance in projects with many functional variant values (e.g. a `matchVariant` plugin with thousands of values) (#20663)
- Don't crash or create a fallback with the wrong color for a `color-mix(…)` without a color interpolation method (e.g. `color-mix(var(--color-red-500))` or `color-mix(currentcolo...
- Ensure `@tailwindcss/oxide-wasm32-wasi` loads instead of hanging forever (e.g. with `NAPI_RS_FORCE_WASI=error` or in WebContainers) (#20667)
- Remove `as: '*.css'` from the `@tailwindcss/turbopack` setup in its README, because it breaks CSS modules (#20660)

## Migration Snippet
```ts
npm install tailwindcss@4.3.5
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.
- **Graph Conflict (tailwindcss ↔ shadcn)**: Tailwind v4 replaces `tailwind.config.js` with CSS-first `@theme` blocks, breaking HSL plugin variables in legacy `shadcn/ui` registries. Run the OKLCH token codemod and upgrade `shadcn` to `v2.4.0`. Migration: Moderate. | Resolution: `npx @tailwindcss/upgrade@latest && npx shadcn@latest add --overwrite`

## Zero-Noise Release Timeline
- **v4.3.5** (2026-11-06) [COMPATIBLE]: Canonicalization: improve performance in projects with man. Drop-in upgrade. Migration: None.
- **v4.3.4** (2026-11-02) [COMPATIBLE]: Add `@tailwindcss/turbopack`, a Turbopack loader for using. Drop-in upgrade. Migration: None.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is tailwindlabs/tailwindcss v4.3.5 safe to upgrade in production?
tailwindlabs/tailwindcss v4.3.5 is classified as COMPATIBLE (PATCH release). Canonicalization: improve performance in projects with man. Drop-in upgrade. Migration: None.

### What breaking changes or compatibility risks exist in tailwindlabs/tailwindcss v4.3.5?
tailwindcss with shadcn: Tailwind v4 replaces `tailwind.config.js` with CSS-first `@theme` blocks, breaking HSL plugin variables in legacy `shadcn/ui` registries. Run the OKLCH token codemod and upgrade `shadcn` to `v2.4.0`. Migration: Moderate.

### What is the bundle size impact of tailwindcss v4.3.5?
tailwindcss v4.3.5 records a +0.1 kB (+0.2%) delta (oxide-engine), moving from 72,587 bytes to 72,706 bytes.

### How do I upgrade tailwindcss to v4.3.5?
Upgrade tailwindcss to v4.3.5 by running "npm install tailwindcss@4.3.5" and applying the migration steps: npm install tailwindcss@4.3.5