@tailwindcss/vite - npm Package Versions

[4.0.0-alpha.27] - 2024-10-15

Added

• Add support for tailwindcss/colors.js, tailwindcss/defaultTheme.js, and tailwindcss/plugin.js exports (#14595)
• Support keyframes in JS config file themes (#14594)
• Support the color parameter in JS theme configuration callbacks (#14651)
• Support using the object parameter in the JS theme configuration callback as theme() function (#14659)
• Upgrade (experimental): Automatically discover JavaScript config files (#14597)
• Upgrade (experimental): Inject @config "…" when a tailwind.config.{js,ts,…} is detected (#14635)
• Upgrade (experimental): Migrate @media screen(…) when running codemods (#14603)
• Upgrade (experimental): Migrate aria-*, data-*, and supports-* variants from arbitrary values to bare values (#14644)
• Upgrade (experimental): Migrate arbitrary values to bare values (#14669)
• Upgrade (experimental): Migrate legacy classes to the v4 alternative (#14643)
• Upgrade (experimental): Migrate static JS configurations to CSS (#14639, #14650, #14648, #14666)
• Upgrade (experimental): Migrate v3 PostCSS setups to v4 in some cases (#14612)

Fixed

• Don’t crash when scanning a candidate equal to the configured prefix (#14588)
• Ensure there's always a space before !important when stringifying CSS (#14611)
• Don't set display: none on elements that use hidden="until-found" (#14631)
• Ensure the CSS theme() function resolves to the right value in some compatibility situations (#14614)
• Fix issue that could cause the CLI to crash when files are deleted while watching (#14616)
• Ensure custom variants using the JS API have access to modifiers (#14637)
• Ensure auto complete suggestions work when using matchUtilities (#14589)
• Pass options when using addComponents and matchComponents (#14590)
• Ensure boxShadow and animation theme keys in JS config files are accessible under --shadow-* and --animate-* using the theme() function (#14642)
• Ensure all theme keys with new names are also accessible under their old names when using the theme() function with the legacy dot notation syntax (#14642)
• Ensure var(…) can be used as the opacity value inside the theme([path] / [modifier]) function (#14653)
• Ensure font-stretch utilities only accepts positive integer bare values (#14670)
• Upgrade (experimental): Ensure CSS before a layer stays unlayered when running codemods (#14596)
• Upgrade (experimental): Resolve issues where some prefixed candidates were not properly migrated (#14600)

[4.0.0-alpha.26] - 2024-10-03

Added

• Add support for prefixes (#14501)
• Expose timing information in debug mode (#14553)
• Add support for blocklist in JS config files (#14556)
• Add color-scheme utilities (#14567)
• Add support for important option in JS config files (#14448)
• Upgrade (experimental): Convert @import "tailwindcss/tailwind.css" to @import "tailwindcss" in CSS files (#14514)
• Upgrade (experimental): Apply all utility upgrades to @apply in CSS files (#14574)
• Upgrade (experimental): Update variant order in template files (#14524)
• Upgrade (experimental): Convert bg-gradient-* utilities to bg-linear-* in template files (#14537)
• Upgrade (experimental): Convert legacy prefixes to variant prefixes in template files (#14557)
• Upgrade (experimental): Convert bare CSS variables in arbitrary values to var(…) in template files (#14526)
• Upgrade (experimental): Convert legacy important modifier syntax to trailing syntax (#14502)

Fixed

• Use the right import base path when using the CLI to reading files from stdin (#14522)
• Ensure that @utility is top-level and cannot be nested (#14525)
• Only setup a single compiler in @tailwindcss/postcss for initial builds (#14565)
• Ensure editing imported CSS files triggers a rebuild (#14561)
• Ensure @apply and CSS functions work inside imported stylesheets (#14576)
• Upgrade (experimental): Don't wrap custom CSS after utilities in a layer (#14512)
• Upgrade (experimental): Don't add empty layer() to @import at-rules when the styles do not need to be imported into a layer (#14513)
• Upgrade (experimental): Don't wrap comment nodes in @layer when running codemods (#14517)
• Upgrade (experimental): Fix scenario where selectors can be lost in multi-selector rules (#14518)
• Upgrade (experimental): Ensure custom CSS before @tailwind rules is wrapped with @layer base when prepending @import "tailwindcss" to the top of the file (#14536)

Changed

• Disallow bare values with decimal places (#14562)

[4.0.0-alpha.25] - 2024-09-24

Added

• Add support for aria, supports, and data variants defined in JS config files (#14407)
• Add @tailwindcss/upgrade tooling (#14434)
• Support screens in JS config files (#14415)
• Add bg-radial-* and bg-conic-* utilities for radial and conic gradients (#14467)
• Add new shadow-initial and inset-shadow-initial utilities for resetting shadow colors (#14468)
• Add field-sizing-* utilities (#14469)
• Include gradient color properties in color transitions (#14489)
• Upgrade (experimental): Convert important syntax in @apply in CSS files (#14411)
• Upgrade (experimental): Convert @tailwind directives to @import rules in CSS files (#14411, #14504)
• Upgrade (experimental): Convert custom CSS in @layer utilities and @layer components to use @utility in CSS files (#14455)

Fixed

• Support borderRadius.* as an alias for --radius-* when using dot notation inside the theme() function (#14436)
• Ensure individual variants from groups are always sorted earlier than stacked variants from the same groups (#14431)
• Allow anchor-size(…) in arbitrary values (#14394)
• Skip candidates with invalid theme() calls (#14437)
• Don't generate inset-* utilities for --inset-shadow-* and --inset-ring-* theme values (#14447)
• Include --default-transition-* variables in transition-* utility output (#14482)
• Ensure rtl and ltr variants work with [dir=auto] (#14306)

Changed

• Preserve explicit leading-*, tracking-*, and font-{weight} value when overriding font-size (#14403)
• Disallow negative bare values in core utilities and variants (#14453)
• Preserve explicit shadow color when overriding shadow size (#14458)
• Preserve explicit transition duration and timing function when overriding transition property (#14490)
• Change the implementation for @import resolution to speed up initial builds (#14446)
• Remove automatic var(…) injection (#13657)
• Only apply :hover states on devices that support @media (hover: hover) (#14500)

[4.0.0-alpha.24] - 2024-09-11

Added

• Support CSS theme() functions inside other @custom-media, @container, and @supports rules (#14358)
• Export Config type from tailwindcss for JS config files (#14360)
• Add support for matchVariant plugins using the @plugin directive (#14371)
• Warn when the tailwindcss package is used as a PostCSS plugin (#14378)

Fixed

• Ensure there is always CLI feedback on save even when no new classes were found (#14351)
• Properly resolve theme('someKey.DEFAULT') when all --some-key-* keys have a suffix (#14354)
• Make sure tuple theme values in JS configs take precedence over @theme default values (#14359)
• Improve IntelliSense completions for border utilities (#14370)

[4.0.0-alpha.23] - 2024-09-05

Added

• Add opacity modifier support to the theme() function in plugins (#14348)

[4.0.0-alpha.22] - 2024-09-04

Added

• Support TypeScript for @plugin and @config files (#14317)
• Add default option to @theme to support overriding default theme values from plugins/JS config files (#14327)
• Add support for <style> tags in Astro files to the Vite plugin (#14340)

Fixed

• Ensure content globs defined in @config files are relative to that file (#14314)
• Ensure CSS theme() functions are evaluated in media query ranges with collapsed whitespace (#14321)
• Fix support for Nuxt projects in the Vite plugin (requires Nuxt 3.13.1+) (#14319)
• Evaluate theme functions in plugins and JS config files (#14326)
• Ensure theme values overridden with reference values don't generate stale CSS variables (#14327)
• Don’t suggest named opacity modifiers in IntelliSense (#14339)
• Fix a crash with older Node.js versions (#14342)
• Support defining theme values as arrays of strings in JS config files (#14343)
• Ensure --default-font-* and --default-mono-font-* variables respect theme customizations in JS config files (#14344)

[4.0.0-alpha.21] - 2024-09-02

Added

• Add new standalone builds of Tailwind CSS v4 (#14270)
• Support JavaScript configuration files using @config (#14239)
• Support plugin options in @plugin (#14264)
• Add support for using the Vite extension with css.transformer set to lightningcss (#14269)

Fixed

• Bring back type exports for the cjs build of @tailwindcss/postcss (#14256)
• Correctly merge tuple values when using the plugin API (#14260)
• Handle arrays in the CSS theme() function when using plugins (#14262)
• Fix fallback values when using the CSS theme() function (#14262)
• Fix support for declaration fallbacks in plugins (#14265)
• Support bare values when using tailwindcss/defaultTheme (#14257)
• Correctly update builds when using the Vite extension with build --watch (#14269)

Changed

• Remove named opacity support for color opacity modifiers (#14278)

[4.0.0-alpha.20] - 2024-08-23

Added

• Add support for addBase plugins using the @plugin directive (#14172)
• Add support for the tailwindcss/plugin export (#14173)
• Add support for the theme() function in plugins (#14207)
• Add support for addComponents, matchComponents, prefix plugin APIs (#14221)
• Add support for tailwindcss/colors and tailwindcss/defaultTheme exports for use with plugins (#14221)
• Add support for the @tailwindcss/typography and @tailwindcss/forms plugins (#14221)
• Add support for the theme() function in CSS and class names (#14177)
• Add support for matching multiple utility definitions for one candidate (#14231)

Fixed

• Don't wrap relative selectors in arbitrary variants with :is(…) (#14203)

[4.0.0-alpha.19] - 2024-08-09

Added

• Add support for inline option when defining @theme values (#14095)
• Add inert variant (#14129)
• Add support for explicitly registering content paths using new @source at-rule (#14078)
• Add support for scanning <style> tags in Vue files to the Vite plugin (#14158)
• Add support for basic addUtilities and matchUtilities plugins using the @plugin directive (#14114)

Fixed

• Ensure @apply works inside @utility (#14144)

[4.0.0-alpha.18] - 2024-07-25

Added

• Add support for basic addVariant plugins with new @plugin directive (#13982, #14008)
• Add @variant at-rule for defining custom variants in CSS (#13992, #14008)
• Add @utility at-rule for defining custom utilities in CSS (#14044)

Fixed

• Discard invalid classes such as bg-red-[#000] (#13970)
• Fix parsing body-less at-rule without terminating semicolon (#13978)
• Ensure opacity modifier with variables work with color-mix() (#13972)
• Discard invalid variants and utilities with modifiers (#13977)
• Add missing utilities that exist in v3, such as resize, fill-none, accent-none, drop-shadow-none, and negative hue-rotate and backdrop-hue-rotate utilities (#13971)
• Don’t allow at-rule-only variants to be compounded (#14015)
• Ensure compound variants work with variants with multiple selectors (#14016)
• Ensure attribute values in data-* and aria-* modifiers are always quoted in the generated CSS (#14040)

Changed

• Reduce the specificity of the * variant so those styles can be overridden by child elements (#14056)