[Snyk] Upgrade tailwindcss from 3.4.17 to 4.1.3

[Dargon789]

Snyk has created this PR to upgrade tailwindcss from 3.4.17 to 4.1.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 68 versions ahead of your current version.

• The recommended version was released a month ago.

Release notes

Package name: tailwindcss

• 4.1.3 - 2025-04-04
  

  Fixed

  • Show warning when using unsupported bare value data type in --value(…) (#17464)
  • PostCSS: Ensure changes to the input CSS file don't generate stale output when using Turbopack (#17554)
  • Ensure classes are detected in Ruby's %w syntax in Slim templates (#17557)
• 4.1.2 - 2025-04-03
  

  Fixed

  • Don't rely on the presence of @ layer base to polyfill @ property (#17506)
  • Support setting multiple inset shadows as arbitrary values (#17523)
  • Fix drop-shadow-* utilities that are defined with multiple shadows (#17515)
  • PostCSS: Fix race condition when two changes are queued concurrently (#17514)
  • PostCSS: Ensure files containing @ tailwind utilities are processed (#17514)
  • Ensure the color-mix(…) polyfill creates fallbacks even when using colors that cannot be statically analyzed (#17513)
  • Fix slow incremental builds with @ tailwindcss/vite and @ tailwindcss/postscss (especially on Windows) (#17511)
  • Vite: Fix missing CSS file in Qwik setups (#17533)
• 4.1.1 - 2025-04-02
  

  Fixed

  • Disable padding in @ source inline(…) brace expansion (#17491)
  • Inject polyfills after @ import and body-less @ layer (#17493)
  • Ensure @ tailwindcss/cli does not contain an import for jiti (#17502)
• 4.1.0 - 2025-04-01
  

  Added

  • Add details-content variant (#15319)
  • Add inverted-colors variant (#11693)
  • Add noscript variant (#11929, #17431)
  • Add items-baseline-last and self-baseline-last utilities (#13888, #17476)
  • Add pointer-none, pointer-coarse, and pointer-fine variants (#16946)
  • Add any-pointer-none, any-pointer-coarse, and any-pointer-fine variants (#16941)
  • Add safe alignment utilities (#14607)
  • Add user-valid and user-invalid variants (#12370)
  • Add wrap-anywhere, wrap-break-word, and wrap-normal utilities (#12128)
  • Add @ source inline(…) and @ source not inline(…) (#17147)
  • Add @ source not "…" (#17255)
  • Add text-shadow-* utilities (#17389)
  • Add mask-* utilities (#17134)
  • Add bg-{position,size}-* utilities for arbitrary values (#17432)
  • Add shadow-*/<alpha>, inset-shadow-*/<alpha>, drop-shadow-*/<alpha>, and text-shadow-*/<alpha> utilities to control shadow opacity (#17398, #17434)
  • Add drop-shadow-<color> utilities (#17434)
  • Improve compatibility with older versions of Safari and Firefox (#17435)

  Fixed

  • Follow symlinks when resolving @ source directives (#17391)
  • Don't scan ignored files for classes when changing an ignored file triggers a rebuild using @ tailwindcss/cli (#17255)
  • Support negated content rules in legacy JavaScript configuration (#17255)
  • Interpret syntax like @("@")md:… as @ md:… in Razor files (#17427)
  • Disallow top-level braces, top-level semicolons, and unbalanced parentheses and brackets in arbitrary values (#17361)
  • Ensure the --theme(…) function still resolves to the CSS variables when using legacy JS plugins (#17458)
  • Detect used theme variables in CSS module files (#17433, #17467)

  Changed

  • Ignore node_modules by default (can be overridden by @ source … rules) (#17255)
  • @ source rules that include file extensions or point inside node_modules/ folders no longer consider your .gitignore rules (#17255)
  • Deprecate bg-{left,right}-{top,bottom} in favor of bg-{top,bottom}-{left,right} utilities (#17378)
  • Deprecate object-{left,right}-{top,bottom} in favor of object-{top,bottom}-{left,right} utilities (#17437)
• 4.0.17 - 2025-03-26
  

  Fixed

  • Fix an issue causing the CLI to hang when processing Ruby files (#17383)
• 4.0.16 - 2025-03-25
  

  Added

  • Add support for literal values in --value('…') and --modifier('…') (#17304)

  Fixed

  • Fix class extraction followed by ( in Pug (#17320)
  • Ensure @ keyframes for theme animations are emitted if they are referenced following a comma (#17352)
  • Vite: Ensure that updates to an imported CSS file are properly propagated after updating source files (#17347)
  • Pre process Slim templates embedded in Ruby files (#17336)
  • Error when input and output files resolve to the same file when using the CLI (#17311)
  • Add missing suggestions when --spacing(--value(integer, number)) is used (#17308)
  • Add ::-webkit-details-marker pseudo to marker variant (#17362)
• 4.0.15 - 2025-03-20
  

  Fixed

  • Fix incorrect angle in -bg-conic-* utilities (#17174)
  • Fix border-[12px_4px] being interpreted as a border-color instead of a border-width (#17248)
  • Work around a crash in Safari 16.4 and 16.5 when using the default Preflight styles (#17306)
  • Pre-process <template lang="…"> in Vue files (#17252)
  • Ensure that all CSS variables used by Preflight are prefixed (#17036)
  • Prevent segfault when loaded in a worker thread on Linux (#17276)
  • Ensure multiple --value(…) or --modifier(…) calls don't delete subsequent declarations (#17273)
  • Fix class extraction followed by ( in Slim (#17278)
  • Export PluginUtils from tailwindcss/plugin for compatibility with v3 (#17299)
  • Remove redundant line-height: initial from Preflight (#15212)
  • Increase Standalone hardware compatibility on macOS x64 builds (#17267)
  • Ensure that the CSS file rebuilds if a new CSS variable is used from templates (#17301)

  Changed

  • The --theme(…) function now returns CSS variables from your theme variables unless used inside positions where CSS variables are invalid (e.g. inside @ media queries) (#17036)
• 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
• 4.0.12 - 2025-03-07
• 4.0.11 - 2025-03-06
• 4.0.10 - 2025-03-05
• 4.0.9 - 2025-02-25
• 4.0.8 - 2025-02-21
• 4.0.7 - 2025-02-18
• 4.0.6 - 2025-02-10
• 4.0.5 - 2025-02-08
• 4.0.4 - 2025-02-06
• 4.0.3 - 2025-02-01
• 4.0.2 - 2025-01-31
• 4.0.1 - 2025-01-29
• 4.0.0 - 2025-01-21
• 4.0.0-beta.10 - 2025-01-21
• 4.0.0-beta.9 - 2025-01-09
• 4.0.0-beta.8 - 2024-12-17
• 4.0.0-beta.7 - 2024-12-13
• 4.0.0-beta.6 - 2024-12-06
• 4.0.0-beta.5 - 2024-12-04
• 4.0.0-beta.4 - 2024-11-29
• 4.0.0-beta.3 - 2024-11-27
• 4.0.0-beta.2 - 2024-11-22
• 4.0.0-beta.1 - 2024-11-21
• 4.0.0-alpha.36 - 2024-11-21
• 4.0.0-alpha.35 - 2024-11-20
• 4.0.0-alpha.34 - 2024-11-14
• 4.0.0-alpha.33 - 2024-11-12
• 4.0.0-alpha.32 - 2024-11-11
• 4.0.0-alpha.31 - 2024-10-30
• 4.0.0-alpha.30 - 2024-10-24
• 4.0.0-alpha.29 - 2024-10-23
• 4.0.0-alpha.28 - 2024-10-17
• 4.0.0-alpha.27 - 2024-10-15
• 4.0.0-alpha.26 - 2024-10-03
• 4.0.0-alpha.25 - 2024-09-24
• 4.0.0-alpha.24 - 2024-09-12
• 4.0.0-alpha.23 - 2024-09-05
• 4.0.0-alpha.22 - 2024-09-05
• 4.0.0-alpha.21 - 2024-09-02
• 4.0.0-alpha.20 - 2024-08-23
• 4.0.0-alpha.19 - 2024-08-09
• 4.0.0-alpha.18 - 2024-07-25
• 4.0.0-alpha.17 - 2024-07-04
• 4.0.0-alpha.16 - 2024-06-07
• 4.0.0-alpha.15 - 2024-05-08
• 4.0.0-alpha.14 - 2024-04-09
• 4.0.0-alpha.13 - 2024-04-04
• 4.0.0-alpha.12 - 2024-04-04
• 4.0.0-alpha.11 - 2024-03-27
• 4.0.0-alpha.10 - 2024-03-21
• 4.0.0-alpha.9 - 2024-03-13
• 4.0.0-alpha.8 - 2024-03-11
• 4.0.0-alpha.7 - 2024-03-08
• 4.0.0-alpha.6 - 2024-03-07
• 4.0.0-alpha.5 - 2024-03-06
• 4.0.0-alpha.4 - 2024-03-06
• 4.0.0-alpha.3 - 2024-03-06
• 4.0.0-alpha.2 - 2024-03-06
• 4.0.0-alpha.1 - 2024-03-05
• 3.4.17 - 2024-12-17

from tailwindcss GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Upgrade Tailwind CSS from version 3.4.17 to 4.1.3, a major version upgrade with potential breaking changes

New Features:

• Added new variants like details-content, inverted-colors, and noscript
• Introduced new utilities for text shadows, masks, and background positioning
• Added support for arbitrary values in various utilities

Bug Fixes:

• Fixed various class extraction issues
• Resolved PostCSS and build system compatibility problems
• Addressed template preprocessing for different frameworks

Enhancements:

• Improved compatibility with older browsers
• Enhanced class detection in various template languages
• Added more flexible CSS variable and theme handling

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
js-dashboard	❌ Failed (Inspect)			Apr 30, 2025 3:18pm

[sourcery-ai]

Reviewer's Guide

The tailwindcss dependency version was updated in the package.json file.

File-Level Changes

Change	Details	Files
Updated tailwindcss dependency version.	Bumped tailwindcss from version 3.4.17 to 4.1.3.	apps/wallet-ui/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​react-dom@​19.1.2
	prompts@​2.4.2
	tiny-invariant@​1.3.3
	@​types/​react@​19.1.0
	node-html-parser@​6.1.13
	he@​1.2.0
	@​types/​node@​22.14.0
	cross-spawn@​7.0.6
	postcss@​8.5.3
	react@​19.1.0
	turbo@​2.5.0
	tailwindcss@​3.4.17
	tslib@​2.8.1
	typescript@​5.8.3
	react-dom@​19.1.0
	prettier@​3.5.3
	zod@​3.24.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		glob@7.2.3 has a License Policy Violation. License: CC-BY-SA-4.0 (package/LICENSE) Source ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/glob@7.2.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		polished@4.3.1 has a License Policy Violation. License: OFL-1.1 (package/docs/assets/fonts/LICENSE.txt) Source ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/polished@4.3.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		spdx-exceptions@2.5.0 has a License Policy Violation. License: CC-BY-3.0 (npm metadata) License: CC-BY-3.0 (package/package.json) Source ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/spdx-exceptions@2.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		typescript@5.8.3 has a License Policy Violation. License: CC-BY-4.0 (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old (package/ThirdPartyNoticeText.txt) Source: apps/dashboard/package.json Source: apps/login/package.json Source: apps/playground-web/package.json Source: apps/portal/package.json Source: apps/wallet-ui/package.json Source: package.json Source: packages/insight/package.json Source: packages/react-native-adapter/package.json Source: packages/service-utils/package.json Source: packages/thirdweb/package.json Source: packages/wagmi-adapter/package.json Source: pnpm-lock.yaml ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@5.8.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		glob@7.2.3 is Deprecated. Reason: Glob versions prior to v9 are no longer supported Source ℹ Read more on: This package | This alert | What is a deprecated package? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/glob@7.2.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		inflight@1.0.6 is Deprecated. Reason: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. Source ℹ Read more on: This package | This alert | What is a deprecated package? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/inflight@1.0.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		rimraf@3.0.2 is Deprecated. Reason: Rimraf versions prior to v4 are no longer supported Source ℹ Read more on: This package | This alert | What is a deprecated package? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rimraf@3.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report