Packages

@tailwindcss/oxide

4.3.4 · 2 Nov 2026MIT112.9M / weekRepositorynpmAtom feed

Your version

4.3.0

8 May 2026Where it was published

4.3.4 is the newest release of 4.x.

In short

9 new13 fixed

Release note

Added

  • Add @container-size utility

  • Add scrollbar-{auto,thin,none} utilities for scrollbar-width, and scrollbar-thumb-* / scrollbar-track-* color utilities for scrollbar-color (#19981, #20019)

  • Add scrollbar-gutter-* utilities

  • Add zoom-* utilities

  • Add tab-* utilities

  • Allow using @variant with stacked variants (e.g. @variant hover:focus { … })

  • Allow using @variant with compound variants (e.g. @variant hover, focus { … })

  • Support --default(…) in --value(…) and --modifier(…) for functional @utility definitions

Fixed

  • Ensure @plugin resolves package JavaScript entries instead of browser CSS entries when using @tailwindcss/vite

  • Fix relative @import and @plugin paths resolving from the wrong directory when using @tailwindcss/vite

  • Ensure CSS files containing @variant are processed by @tailwindcss/vite

  • Resolve imports relative to base when result.opts.from is not provided when using @tailwindcss/postcss

  • Canonicalization: Preserve significant _ whitespace in arbitrary values

  • Canonicalization: Add parentheses when removing whitespace from arbitrary values would hurt readability (e.g. w-[calc(100%---spacing(60))] → w-[calc(100%-(--spacing(60)))])

  • Canonicalization: Preserve the original unit in arbitrary values instead of normalizing to base units (e.g. -mt-[20in] → mt-[-20in], not mt-[-1920px])

  • Canonicalization: Migrate arbitrary :has() variants from [&:has(…)] to has-[…]

  • Upgrade: don’t migrate inline style attributes (e.g. style="flex-grow: 1" → style="flex-grow: 1", not style="grow: 1")

  • Allow multiple @utility definitions with the same name but different value types

  • Export missing PluginWithConfig type from tailwindcss/plugin to fix errors when inferring plugin config types

  • Ensure start and end legacy utilities without values do not generate CSS

  • Ensure --value(…) is required in functional @utility definitions

  • Canonicalization: Preserve required whitespace around operators in negated arbitrary values (e.g. -left-[(var(--a)+var(--b))])