Update @tailwindcss/vite 4.1.4 → 4.1.8 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​tailwindcss/vite (4.1.4 → 4.1.8)

Sorry, we couldn't find anything useful about this release.

↗️ @​emnapi/core (indirect, 1.4.0 → 1.4.3) · Repo

Release Notes

1.4.3

What's Changed

• update @emnapi/[email protected] in the package.json dependency of @emnapi/core

Full Changelog: v1.4.2...v1.4.3

1.4.2

What's Changed

• fix: check SharedArrayBuffer by @toyobayashi in #144

Full Changelog: v1.4.1...v1.4.2

1.4.1

What's Changed

• add checks for message channel usage in web runtime by @gvkhna in #142

New Contributors

• @gvkhna made their first contribution in #142

Full Changelog: v1.4.0...v1.4.1

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​emnapi/runtime (indirect, 1.4.0 → 1.4.3) · Repo

Release Notes

1.4.3

What's Changed

• update @emnapi/[email protected] in the package.json dependency of @emnapi/core

Full Changelog: v1.4.2...v1.4.3

1.4.2

What's Changed

• fix: check SharedArrayBuffer by @toyobayashi in #144

Full Changelog: v1.4.1...v1.4.2

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​emnapi/wasi-threads (indirect, 1.0.1 → 1.0.2) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ @​napi-rs/wasm-runtime (indirect, 0.2.8 → 0.2.10) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ detect-libc (indirect, 2.0.3 → 2.0.4) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ lightningcss (indirect, 1.29.2 → 1.30.1) · Repo

Release Notes

1.30.1

Fixed crash on process exit when lightningcss was loaded inside a Node.js worker thread on Linux

1.30.0

Features

• Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
• Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See https://web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
• Skip generating unnecessary @supports rules when already nested in a @supports rule – #878, d398c1b
• Improve error recovery for media queries – #954
• Add support for ::picker, ::picker-icon and ::checkmark – #957
• Add build support for Android – #932

Fixes

• Fix error message for invalid composes selectors – #948
• Update browserslist – #961
• Fix linear-gradient direction conversion for legacy vendor-prefixed values – #936
• Prevent new lines in license comments from breaking source maps – #971
• Do not inline layers before imports – 33ea2c1
• Statically link Visual Studio redistributables on Windows builds – e5c4139
• update browser compat data – 17bdc80

1.29.3

• Support for ::details-content and ::target-text selectors – @philipp-spiess in #930
• Update :placeholder-shown selector name across browsers – @Marukome0743 in #929
• Support /* cssmodules-pure-no-check */ comments – @jantimon in #898
• Update browser compatibility data – c03a7e7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ lightningcss-darwin-arm64 (indirect, 1.29.2 → 1.30.1) · Repo

Release Notes

1.30.1

Fixed crash on process exit when lightningcss was loaded inside a Node.js worker thread on Linux

1.30.0

Features

• Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
• Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See https://web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
• Skip generating unnecessary @supports rules when already nested in a @supports rule – #878, d398c1b
• Improve error recovery for media queries – #954
• Add support for ::picker, ::picker-icon and ::checkmark – #957
• Add build support for Android – #932

Fixes

• Fix error message for invalid composes selectors – #948
• Update browserslist – #961
• Fix linear-gradient direction conversion for legacy vendor-prefixed values – #936
• Prevent new lines in license comments from breaking source maps – #971
• Do not inline layers before imports – 33ea2c1
• Statically link Visual Studio redistributables on Windows builds – e5c4139
• update browser compat data – 17bdc80

1.29.3

• Support for ::details-content and ::target-text selectors – @philipp-spiess in #930
• Update :placeholder-shown selector name across browsers – @Marukome0743 in #929
• Support /* cssmodules-pure-no-check */ comments – @jantimon in #898
• Update browser compatibility data – c03a7e7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ lightningcss-darwin-x64 (indirect, 1.29.2 → 1.30.1) · Repo

Release Notes

1.30.1

Fixed crash on process exit when lightningcss was loaded inside a Node.js worker thread on Linux

1.30.0

Features

• Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
• Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See https://web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
• Skip generating unnecessary @supports rules when already nested in a @supports rule – #878, d398c1b
• Improve error recovery for media queries – #954
• Add support for ::picker, ::picker-icon and ::checkmark – #957
• Add build support for Android – #932

Fixes

• Fix error message for invalid composes selectors – #948
• Update browserslist – #961
• Fix linear-gradient direction conversion for legacy vendor-prefixed values – #936
• Prevent new lines in license comments from breaking source maps – #971
• Do not inline layers before imports – 33ea2c1
• Statically link Visual Studio redistributables on Windows builds – e5c4139
• update browser compat data – 17bdc80

1.29.3

• Support for ::details-content and ::target-text selectors – @philipp-spiess in #930
• Update :placeholder-shown selector name across browsers – @Marukome0743 in #929
• Support /* cssmodules-pure-no-check */ comments – @jantimon in #898
• Update browser compatibility data – c03a7e7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ lightningcss-linux-arm64-gnu (indirect, 1.29.2 → 1.30.1) · Repo

Release Notes

1.30.1

Fixed crash on process exit when lightningcss was loaded inside a Node.js worker thread on Linux

1.30.0

Features

• Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
• Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See https://web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
• Skip generating unnecessary @supports rules when already nested in a @supports rule – #878, d398c1b
• Improve error recovery for media queries – #954
• Add support for ::picker, ::picker-icon and ::checkmark – #957
• Add build support for Android – #932

Fixes

• Fix error message for invalid composes selectors – #948
• Update browserslist – #961
• Fix linear-gradient direction conversion for legacy vendor-prefixed values – #936
• Prevent new lines in license comments from breaking source maps – #971
• Do not inline layers before imports – 33ea2c1
• Statically link Visual Studio redistributables on Windows builds – e5c4139
• update browser compat data – 17bdc80

1.29.3

• Support for ::details-content and ::target-text selectors – @philipp-spiess in #930
• Update :placeholder-shown selector name across browsers – @Marukome0743 in #929
• Support /* cssmodules-pure-no-check */ comments – @jantimon in #898
• Update browser compatibility data – c03a7e7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ lightningcss-linux-arm64-musl (indirect, 1.29.2 → 1.30.1) · Repo

Release Notes

1.30.1

Fixed crash on process exit when lightningcss was loaded inside a Node.js worker thread on Linux

1.30.0

Features

• Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
• Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See https://web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
• Skip generating unnecessary @supports rules when already nested in a @supports rule – #878, d398c1b
• Improve error recovery for media queries – #954
• Add support for ::picker, ::picker-icon and ::checkmark – #957
• Add build support for Android – #932

Fixes

• Fix error message for invalid composes selectors – #948
• Update browserslist – #961
• Fix linear-gradient direction conversion for legacy vendor-prefixed values – #936
• Prevent new lines in license comments from breaking source maps – #971
• Do not inline layers before imports – 33ea2c1
• Statically link Visual Studio redistributables on Windows builds – e5c4139
• update browser compat data – 17bdc80

1.29.3

• Support for ::details-content and ::target-text selectors – @philipp-spiess in #930
• Update :placeholder-shown selector name across browsers – @Marukome0743 in #929
• Support /* cssmodules-pure-no-check */ comments – @jantimon in #898
• Update browser compatibility data – c03a7e7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ lightningcss-linux-x64-gnu (indirect, 1.29.2 → 1.30.1) · Repo

Release Notes

1.30.1

Fixed crash on process exit when lightningcss was loaded inside a Node.js worker thread on Linux

1.30.0

Features

• Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
• Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See https://web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
• Skip generating unnecessary @supports rules when already nested in a @supports rule – #878, d398c1b
• Improve error recovery for media queries – #954
• Add support for ::picker, ::picker-icon and ::checkmark – #957
• Add build support for Android – #932

Fixes

• Fix error message for invalid composes selectors – #948
• Update browserslist – #961
• Fix linear-gradient direction conversion for legacy vendor-prefixed values – #936
• Prevent new lines in license comments from breaking source maps – #971
• Do not inline layers before imports – 33ea2c1
• Statically link Visual Studio redistributables on Windows builds – e5c4139
• update browser compat data – 17bdc80

1.29.3

• Support for ::details-content and ::target-text selectors – @philipp-spiess in #930
• Update :placeholder-shown selector name across browsers – @Marukome0743 in #929
• Support /* cssmodules-pure-no-check */ comments – @jantimon in #898
• Update browser compatibility data – c03a7e7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ lightningcss-linux-x64-musl (indirect, 1.29.2 → 1.30.1) · Repo

Release Notes

1.30.1

Fixed crash on process exit when lightningcss was loaded inside a Node.js worker thread on Linux

1.30.0

Features

• Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
• Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See https://web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
• Skip generating unnecessary @supports rules when already nested in a @supports rule – #878, d398c1b
• Improve error recovery for media queries – #954
• Add support for ::picker, ::picker-icon and ::checkmark – #957
• Add build support for Android – #932

Fixes

• Fix error message for invalid composes selectors – #948
• Update browserslist – #961
• Fix linear-gradient direction conversion for legacy vendor-prefixed values – #936
• Prevent new lines in license comments from breaking source maps – #971
• Do not inline layers before imports – 33ea2c1
• Statically link Visual Studio redistributables on Windows builds – e5c4139
• update browser compat data – 17bdc80

1.29.3

• Support for ::details-content and ::target-text selectors – @philipp-spiess in #930
• Update :placeholder-shown selector name across browsers – @Marukome0743 in #929
• Support /* cssmodules-pure-no-check */ comments – @jantimon in #898
• Update browser compatibility data – c03a7e7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ lightningcss-win32-x64-msvc (indirect, 1.29.2 → 1.30.1) · Repo

Release Notes

1.30.1

Fixed crash on process exit when lightningcss was loaded inside a Node.js worker thread on Linux

1.30.0

Features

• Update relative color parsing to latest spec: colors now support numbers in addition to percentages, and calcs in colors are now always numbers. Note that this was technically a breaking change in the spec. You may need to update code using relative color calculations on percentages to use numbers instead. See the PR for details. – #465
• Update nesting implementation for new spec: It is now possible to nest selectors with pseudo elements, and declarations and nested rules can be interleaved. See https://web.dev/blog/css-nesting-cssnesteddeclarations for more details. – 6c465c1
• Skip generating unnecessary @supports rules when already nested in a @supports rule – #878, d398c1b
• Improve error recovery for media queries – #954
• Add support for ::picker, ::picker-icon and ::checkmark – #957
• Add build support for Android – #932

Fixes

• Fix error message for invalid composes selectors – #948
• Update browserslist – #961
• Fix linear-gradient direction conversion for legacy vendor-prefixed values – #936
• Prevent new lines in license comments from breaking source maps – #971
• Do not inline layers before imports – 33ea2c1
• Statically link Visual Studio redistributables on Windows builds – e5c4139
• update browser compat data – 17bdc80

1.29.3

• Support for ::details-content and ::target-text selectors – @philipp-spiess in #930
• Update :placeholder-shown selector name across browsers – @Marukome0743 in #929
• Support /* cssmodules-pure-no-check */ comments – @jantimon in #898
• Update browser compatibility data – c03a7e7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ tailwindcss (indirect, 4.1.4 → 4.1.8) · Repo · Changelog

Release Notes

4.1.8

Added

• Improve error messages when @apply fails (#18059)

Fixed

• Upgrade: Do not migrate declarations that look like candidates in <style> blocks (#18057, 18068)
• Upgrade: Don't error when looking for tailwindcss in pnpm monorepos (#18065)
• Upgrade: Don't error when updating dependencies in pnpm monorepos (#18065)
• Upgrade: Migrate deprecated order-none to order-0 (#18126)
• Support Leptos class: attributes when extracting classes (#18093)
• Fix "Cannot read properties of undefined" crash on malformed arbitrary value (#18133)
• Upgrade: Migrate -mt-[0px] to mt-[0px] instead of the other way around (#18154)
• Fix Haml pre-processing crash when there is no \n at the end of the file (#18155)
• Ignore .pnpm-store folders by default (can be overridden by @source … rules) (#18163)
• Fix PostCSS crash when calling toJSON() (#18083)

4.1.7

Added

• Upgrade: Migrate bare values to named values (#18000)
• Upgrade: Added cache to improve template migration performance (#18025)

Fixed

• Allow _ before numbers during candidate extraction (#17961)
• Prevent duplicate suggestions when using @theme and @utility together (#17675)
• Ensure that media queries within ::before and ::after pseudo selectors create valid CSS rules in production builds (#17979)
• Ensure that the standalone CLI does not leave temporary files behind (#17981)
• Ensure -rotate-* utilities properly negate arbitrary values (#18014)
• Ignore custom variants using :merge(…) selectors in legacy JS plugins (#18020)
• Ensure classes containing . are properly extracted from Clojure files (#18038)
• Upgrade: Fix error when using @import … source(…) (#17963)
• Upgrade: Change casing of utilities with named values to kebab-case to match updated theme variables (#18017)
• Upgrade: Don't migrate strings that match utility names in Vue attribute bindings other than class (#18025)

4.1.6

Added

• Upgrade: Automatically convert arbitrary values to named values when possible (e.g. h-[1lh] to h-lh) (#17831, #17854)
• Upgrade: Update dependencies in parallel for improved performance (#17898)
• Add detailed logging about @source directives, discovered files and scanned files when using DEBUG=* (#17906, #17952)
• Add support for generating source maps in development (#17775)

Fixed

• Ensure negative arbitrary scale values generate negative values (#17831)
• Fix HAML extraction with embedded Ruby (#17846)
• Don't scan files for utilities when using @reference (#17836)
• Fix incorrectly replacing _ with in arbitrary modifier shorthand bg-red-500/(--my_opacity) (#17889)
• Don't scan .log files for classes by default (#17906)
• Ensure that custom utilities applying other custom utilities don't swallow nested @apply rules (#17925)
• Download platform specific package if optionalDependencies are skipped (#17929)

4.1.5

Added

• Support using @tailwindcss/upgrade to upgrade between versions of v4.* (#17717)
• Add h-lh / min-h-lh / max-h-lh utilities (#17790)
• Transition display, visibility, content-visibility, overlay, and pointer-events when using transition to simplify @starting-style usage (#17812)

Fixed

• Don't scan .geojson or .db files for classes by default (#17700, #17711)
• Hide default shadow suggestions when missing default shadow theme keys (#17743)
• Replace _ with . in theme suggestions for @utility if surrounded by digits (#17733)
• Skip color-mix(…) when opacity is 100% (#17815)
• PostCSS: Ensure that errors in imported stylesheets are recoverable (#17754)
• Upgrade: Bump all Tailwind CSS related dependencies during upgrade (#17763)
• Upgrade: Don't add - to variants starting with @ (#17814)
• Upgrade: Don't format stylesheets that didn't change when upgrading (#17824)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ tapable (indirect, 2.2.1 → 2.2.2) · Repo

Release Notes

2.2.2

Developer Experience

• add interceptors type to hook class

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 @​ampproject/remapping (added, 2.3.0)

🆕 @​isaacs/fs-minipass (added, 4.0.1)

🆕 @​jridgewell/gen-mapping (added, 0.3.8)

🆕 @​jridgewell/resolve-uri (added, 3.1.2)

🆕 @​jridgewell/set-array (added, 1.2.1)

🆕 @​jridgewell/trace-mapping (added, 0.3.25)

🆕 chownr (added, 3.0.0)

🆕 minipass (added, 7.1.2)

🆕 minizlib (added, 3.0.2)

🆕 mkdirp (added, 3.0.1)

🆕 tar (added, 7.4.3)

🆕 yallist (added, 5.0.0)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
ngoquocdat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 29, 2025 4:44pm

[what-the-diff]

PR Summary

• Updated @tailwindcss/vite Package Version in package.json
  The version of the @tailwindcss/vite package has been updated from ^4.1.4 to ^4.1.8. This update helps in keeping our system's dependencies up-to-date and provides us with any feature enhancements or bug fixes that the upgraded version comes with. This ultimately results in better performance of our software.

[depfu]

Closed in favor of #300.