chore(deps-dev): bump tailwindcss from 3.4.17 to 4.0.0 in the css group

[dependabot]

Bumps the css group with 1 update: tailwindcss.

Updates tailwindcss from 3.4.17 to 4.0.0

Release notes

Sourced from tailwindcss's releases.

v4.0.0

Holy shit it's actually done — we just tagged Tailwind CSS v4.0.

Tailwind CSS v4.0 is an all-new version of the framework optimized for performance and flexibility, with a reimagined configuration and customization experience, and taking full advantage of the latest advancements the web platform has to offer.

• New high-performance engine — where full builds are up to 5x faster, and incremental builds are over 100x faster — and measured in microseconds.
• Designed for the modern web — built on cutting-edge CSS features like cascade layers, registered custom properties with @property, and color-mix().
• Simplified installation — fewer dependencies, zero configuration, and just a single line of code in your CSS file.
• First-party Vite plugin — tight integration for maximum performance and minimum configuration.
• Automatic content detection — all of your template files are discovered automatically, with no configuration required.
• Built-in import support — no additional tooling necessary to bundle multiple CSS files.
• CSS-first configuration — a reimagined developer experience where you customize and extend the framework directly in CSS instead of a JavaScript configuration file.
• CSS theme variables — all of your design tokens exposed as native CSS variables so you can access them anywhere.
• Dynamic utility values and variants — stop guessing what values exist in your spacing scale, or extending your configuration for things like basic data attributes.
• Modernized P3 color palette — a redesigned, more vivid color palette that takes full advantage of modern display technology.
• Container queries — first-class APIs for styling elements based on their container size, no plugins required.
• New 3D transform utilities — transform elements in 3D space directly in your HTML.
• Expanded gradient APIs — radial and conic gradients, interpolation modes, and more.
• @​starting-style support — a new variant you can use to create enter and exit transitions, without the need for JavaScript.
• not-* variant — style an element only when it doesn't match another variant, custom selector, or media or feature query.
• Even more new utilities and variants — including support for color-scheme, field-sizing, complex shadows, inert, and more.

Start using Tailwind CSS v4.0 today by installing it in a new project, or playing with it directly in the browser on Tailwind Play.

For existing projects, we've published a comprehensive upgrade guide and built an automated upgrade tool to get you on the latest version as quickly and painlessly as possible.

For a deep-dive into everything that's new, check out the announcement post.

v4.0.0-beta.10

Added

• Add support for using @variant to use variants in your CSS (#15663)
• Include outline-color when transitioning colors (#15690)

Fixed

• Add missing main and browser fields for @tailwindcss/browser (#15594)
• Support escaping * in theme namespace syntax (e.g.: --color-\*: initial;) (#15603)
• Respect @theme options when resolving values in custom functional utilities (#15623)
• Discard invalid variants (e.g. data-checked-[selected=1]:*) (#15629)
• Ensure -outline-offset-* utilities are suggested in IntelliSense (#15646)
• Write to stdout when --output is set to - or omitted with @tailwindcss/cli (#15656)
• Prevent not-* from being used with variants that have multiple sibling rules (#15689)
• Upgrade (experimental): Pretty print --spacing(…) to prevent ambiguity (#15596)

Changed

• Use more modern --alpha(color / 50%) syntax instead of --alpha(color, 50%) (#15665)

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.0.0] - 2025-01-21

[4.0.0-beta.10] - 2025-01-21

Added

• Add support for using @variant to use variants in your CSS (#15663)
• Include outline-color when transitioning colors (#15690)

Fixed

• Add missing main and browser fields for @tailwindcss/browser (#15594)
• Support escaping * in theme namespace syntax (e.g.: --color-\*: initial;) (#15603)
• Respect @theme options when resolving values in custom functional utilities (#15623)
• Discard invalid variants (e.g. data-checked-[selected=1]:*) (#15629)
• Ensure -outline-offset-* utilities are suggested in IntelliSense (#15646)
• Write to stdout when --output is set to - or omitted with @tailwindcss/cli (#15656)
• Prevent not-* from being used with variants that have multiple sibling rules (#15689)
• Upgrade (experimental): Pretty print --spacing(…) to prevent ambiguity (#15596)

Changed

• Use more modern --alpha(color / 50%) syntax instead of --alpha(color, 50%) (#15665)
• Rename @variant to @custom-variant (#15663)
• Change outline-hidden to set outline-style: none except in forced colors mode (#15690)

[4.0.0-beta.9] - 2025-01-09

Added

• Add @tailwindcss/browser package to run Tailwind CSS in the browser (#15558)
• Add @reference "…" API as a replacement for the previous @import "…" reference option (#15565)
• Add support for defining functional utilities in CSS (#15455)
• Add new --spacing(…), --alpha(…), and --theme(…) CSS functions (#15572)
• Add musl-based Linux builds of the standalone CLI (#15567)
• Improve performance of internal AST manipulations (#15529)

Fixed

• Use the correct property value for place-content-between, place-content-around, and place-content-evenly utilities (#15440)
• Don’t detect arbitrary properties when preceded by an escape (#15456)
• Fix incorrectly named bg-round and bg-space utilities to bg-repeat-round to bg-repeat-space (#15462)
• Fix inset-shadow-* suggestions in IntelliSense (#15471)
• Only compile arbitrary values ending in ] (#15503)
• Ensure @apply rules are processed in the correct order (#15542)
• Allow negative utility names in @utility (#15573)
• Remove all @keyframes contributed by JavaScript plugins when using @reference imports (#15581)
• Upgrade (experimental): Do not extract class names from functions (e.g. shadow in filter: 'drop-shadow(…)') (#15566)
• Upgrade (experimental): Migrate theme(spacing.2) to --spacing(2) (#15579)
• Upgrade (experimental): Migrate theme(…) to --theme(…) (#15579)

... (truncated)

Commits

• a8c54ac Prepare v4.0.0 release (#15693)
• 8a97a6a v4.0.0-beta.10 (#15691)
• 4820f6b Transition outline-color (#15690)
• 79f21a8 Prevent not-* from being used with variants with multiple sibling rules (#1...
• 4035ab0 Implement @variant (#15663)
• a51b214 Use more modern --alpha(color / 50%) syntax (#15665)
• 2f8c517 Ensure -outline-offset-* utilities are suggested in IntelliSense (#15646)
• 528c848 Discard invalid variants such as data-checked-[selected=1]:* (#15629)
• 2de644b Remove @property fallbacks for Firefox (#15622)
• da2da51 Resolve values in functional utilities based on @theme options (#15623)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

♻️ PR Preview 6f9477b has been successfully destroyed since this PR has been closed.

_{🤖 By surge-preview}

[tbouffard]

ℹ️ Here is the error logs, and it is pretty explicit

 x Build failed in 495ms
error during build:
[vite:css] [postcss] It looks like you're trying to use `tailwindcss` directly as a PostCSS plugin.
The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS
you'll need to install `@tailwindcss/postcss` and update your PostCSS configuration.

[github-actions]

♻️ PR Preview 6f9477b has been successfully destroyed since this PR has been closed.

_{🤖 By surge-preview}

[tbouffard]

note: From the documentation, https://tailwindcss.com/docs/upgrade-guide#using-postcss:

Additionally, in v4 imports and vendor prefixing is now handled for you automatically, so you can remove postcss-import and autoprefixer if they are in your project

[csouchet]

Before	Now

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud