build(deps-dev): bump @tailwindcss/vite from 4.0.0-alpha.23 to 4.0.0-beta.1

[dependabot]

Bumps @tailwindcss/vite from 4.0.0-alpha.23 to 4.0.0-beta.1.

Release notes

Sourced from @​tailwindcss/vite's releases.

v4.0.0-beta.1

About eight months ago we open-sourced our progress on Tailwind CSS v4.0. Hundreds of hours of fixing bugs, soul-crushing backward compatibility work, and troubleshooting Windows CI failures later, I'm excited to finally tag the first public beta release.

As I talked about when we published the first alpha, Tailwind CSS v4.0 is an all-new engine built for performance, and designed for the modern web.

• Built for performance — full builds in the new engine are up to 5x faster, and incremental builds are over 100x faster — and measured in microseconds.
• Unified toolchain — built-in import handling, vendor prefixing, and syntax transforms, with no additional tooling required.
• CSS-first configuration — a reimagined developer experience where you customize and extend the framework directly in CSS instead of a JavaScript configuration file.
• Designed for the modern web — built on native cascade layers, wide-gamut colors, and including first-class support for modern CSS features like container queries, @starting-style, popovers, and more.

There's so much more to say, but everything you need to get started is in the new beta documentation we published today:

Get started with Tailwind CSS v4.0 Beta 1 →

Start building and help us bullet-proof this thing for the stable release early in the new year.

v4.0.0-alpha.36

Added

• Add consistent base styles for buttons and form controls (#15036)
• Upgrade (experimental): Convert group-[]:flex to in-[.group]:flex (#15054)
• Upgrade (experimental): Add form reset styles to CSS files for compatibility with v3 (#15036)
• Upgrade (experimental): Migrate ring to ring-3 (#15063)

Fixed

• Upgrade (experimental): Ensure migrating to the in-* requires a descendant selector (#15054)

Changed

• Use single drop shadow values instead of multiple (#15056)
• Do not parse invalid candidates with empty arbitrary values (#15055)

v4.0.0-alpha.35

Added

• Reintroduce max-w-screen-* utilities that read from the --breakpoint namespace as deprecated utilities (#15013)
• Support using CSS variables as arbitrary values without var(…) by using parentheses instead of square brackets (e.g. bg-(--my-color)) (#15020)
• Add new in-* variant (#15025)
• Bundle @tailwindcss/forms, @tailwindcss/typography, and @tailwindcss/aspect-ratio with the standalone CLI (#15028)
• Allow addUtilities() and addComponents() to work with child combinators and other complex selectors (#15029)
• Support colors that use <alpha-value> in JS configs and plugins (#15033)
• Add new transition-discrete and transition-normal utilities for transition-behavior (#15051)
• Upgrade (experimental): Migrate [&>*] to the * variant (#15022)
• Upgrade (experimental): Migrate [&_*] to the ** variant (#15022)
• Upgrade (experimental): Warn when trying to migrating a project that is not on Tailwind CSS v3 (#15015)
• Upgrade (experimental): Migrate colors that use <alpha-value> in JS configs (#15033)

... (truncated)

Changelog

Sourced from @​tailwindcss/vite's changelog.

[4.0.0-beta.1] - 2024-11-21

Added

• Upgrade (experimental): Drop unnecessary opacity theme values when migrating to CSS (#15067)

Fixed

• Ensure opacity theme values configured as decimal numbers via JS config files work with color utilities (#15067)
• Bring back support for decoration-clone, decoration-slice, overflow-ellipsis, flex-grow-*, and flex-shrink-* (#15069)
• Upgrade (experimental): Include color in the form reset snippet (#15064)

[4.0.0-alpha.36] - 2024-11-21

Added

• Add consistent base styles for buttons and form controls (#15036)
• Upgrade (experimental): Convert group-[]:flex to in-[.group]:flex (#15054)
• Upgrade (experimental): Add form reset styles to CSS files for compatibility with v3 (#15036)
• Upgrade (experimental): Migrate ring to ring-3 (#15063)

Fixed

• Upgrade (experimental): Don't migrate arbitrary variants to in-* that use the child combinator instead of the descendant combinator (#15054)

Changed

• Use single drop shadow values instead of multiple (#15056)
• Do not parse invalid candidates with empty arbitrary values (#15055)

[4.0.0-alpha.35] - 2024-11-20

Added

• Reintroduce max-w-screen-* utilities that read from the --breakpoint namespace as deprecated utilities (#15013)
• Support using CSS variables as arbitrary values without var(…) by using parentheses instead of square brackets (e.g. bg-(--my-color)) (#15020)
• Add new in-* variant (#15025)
• Bundle @tailwindcss/forms, @tailwindcss/typography, and @tailwindcss/aspect-ratio with the standalone CLI (#15028)
• Allow addUtilities() and addComponents() to work with child combinators and other complex selectors (#15029)
• Support colors that use <alpha-value> in JS configs and plugins (#15033)
• Add new transition-discrete and transition-normal utilities for transition-behavior (#15051)
• Upgrade (experimental): Migrate [&>*] to the * variant (#15022)
• Upgrade (experimental): Migrate [&_*] to the ** variant (#15022)
• Upgrade (experimental): Warn when trying to migrating a project that is not on Tailwind CSS v3 (#15015)
• Upgrade (experimental): Migrate colors that use <alpha-value> in JS configs (#15033)

Fixed

• Ensure flex is suggested (#15014)
• Improve module resolution for cjs-only and esm-only plugins (#15041)

... (truncated)

Commits

• 5e4f565 Prepare v4.0.0-beta.1 release (#15070)
• 11dce5a v4.0.0-alpha.36 (#15062)
• 8b098fc Prepare v4.0.0-alpha.35 release (#15052)
• 5edf6c7 Ensure clients pin the tailwindcss version (#15011)
• 953ecd2 Prepare v4.0.0-alpha.34 (#15002)
• dda181b Vite: Don't track candidate changes for Svelte \<style> tags (#14981)
• 437579d Prepare v4.0.0-alpha.33 release (#14967)
• 7da9272 Prepare v4.0.0-alpha.32 (#14954)
• c72c83f Vite: Support Tailwind in Svelte <style> blocks (#14151)
• 15fc7f4 Apply non-Tailwind CSS transforms in Vite plugin (#14871)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #178.