build(deps): bump tailwindcss from 3.3.2 to 4.0.14

[dependabot]

Bumps tailwindcss from 3.3.2 to 4.0.14.

Release notes

Sourced from tailwindcss's releases.

v4.0.14

Fixed

• Do not extract candidates with JS string interpolation ${ (#17142)
• Fix extraction of variants containing . character (#17153)
• Fix extracting candidates in Clojure/ClojureScript (#17087)

v4.0.13

Fixed

• Fix Haml pre-processing (#17051)
• Ensure .node and .wasm files are not scanned for utilities (#17123)
• Improve performance when scanning JSON files (#17125)
• Fix extracting candidates containing dots in Haml, Pug, and Slim pre processors (#17094, #17085, #17113)
• Don't create invalid CSS when encountering a link wrapped in square brackets (#17129)

v4.0.12

Fixed

• Vite: Fix url(…) rebasing in transitively imported CSS files (#16965)
• PostCSS: Rebase url(…)s in imported CSS files (#16965)
• Ensure utilities are sorted based on their actual property order (#16995)
• Ensure strings in Pug and Slim templates are handled correctly (#17000)
• Ensure classes between } and { are properly extracted (#17001)
• Fix razor/cshtml pre-processing (#17027)
• Ensure extracting candidates from JS embedded in a PHP string works as expected (#17031)

v4.0.11

Fixed

• Ensure classes containing -- are extracted correctly (#16972)
• Ensure classes containing numbers followed by dash or underscore are extracted correctly (#16980)
• Ensure arbitrary container queries are extracted correctly (#16984)
• Ensure classes ending in [ are extracted in Slim templating language (#16985)
• Ensure arbitrary variables with data types are extracted correctly (#16986)

v4.0.10

Added

• Add col-<number> and row-<number> utilities for grid-column and grid-row (#15183)

Fixed

• Ensure not-* does not remove :is(…) from variants (#16825)
• Ensure @keyframes are correctly emitted when using a prefix (#16850)
• Don't swallow @utility declarations when @apply is used in nested rules (#16940)
• Ensure outline-hidden behaves like outline-none outside of forced colors mode (#16943)
• Allow !important on CSS variables again (#16873)
• Vite: Do not crash when encountering an .svg file with # or ? in the filename (#16957)
• Ensure utilities are properly detected within square brackets (#16306)

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.0.14] - 2025-03-13

Fixed

• Do not extract candidates with JS string interpolation ${ (#17142)
• Fix extraction of variants containing . character (#17153)
• Fix extracting candidates in Clojure/ClojureScript (#17087)

[4.0.13] - 2025-03-11

Fixed

• Fix Haml pre-processing (#17051)
• Ensure .node and .wasm files are not scanned for utilities (#17123)
• Improve performance when scanning JSON files (#17125)
• Fix extracting candidates containing dots in Haml, Pug, and Slim pre processors (#17094, #17085, #17113)
• Don't create invalid CSS when encountering a link wrapped in square brackets (#17129)

[4.0.12] - 2025-03-07

Fixed

• Vite: Fix url(…) rebasing in transitively imported CSS files (#16965)
• PostCSS: Rebase url(…)s in imported CSS files (#16965)
• Ensure utilities are sorted based on their actual property order (#16995)
• Ensure strings in Pug and Slim templates are handled correctly (#17000)
• Ensure classes between } and { are properly extracted (#17001)
• Fix razor/cshtml pre-processing (#17027)
• Ensure extracting candidates from JS embedded in a PHP string works as expected (#17031)

[4.0.11] - 2025-03-06

Fixed

• Ensure classes containing -- are extracted correctly (#16972)
• Ensure classes containing numbers followed by dash or underscore are extracted correctly (#16980)
• Ensure arbitrary container queries are extracted correctly (#16984)
• Ensure classes ending in [ are extracted in Slim templating language (#16985)
• Ensure arbitrary variables with data types are extracted correctly (#16986)

[4.0.10] - 2025-03-05

Added

• Add col-<number> and row-<number> utilities for grid-column and grid-row (#15183)

Fixed

• Ensure not-* does not remove :is(…) from variants (#16825)
• Ensure @keyframes are correctly emitted when using a prefix (#16850)

... (truncated)

Commits

• 3c5903c Prepare v4.0.14 release (#17173)
• 215f4f3 Add @source inline(…) (#17147)
• 4455048 Prepare release 4.0.13 (#17132)
• 2f28e5f Prepare v4.0.12 release (#17033)
• 3d0606b Fix sorting of classes that have undefined declarations (#16995)
• b676da8 Prepare v4.0.11 release (#16987)
• 1638b16 Prepare v4.0.10 release (#16963)
• 1c2ad57 Add pointer-* variants (#16946)
• 2eecb4d Remove max-w-auto and max-h-auto (#16917)
• 57b080c Allow !important on CSS variables (#16873)
• 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
devcastle	❌ Failed (Inspect)			Mar 17, 2025 8:46am

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[dependabot]

Superseded by #259.