Pull Request Opened
PR #58 opened: build(deps-dev): bump tailwindcss from 3.4.19 to 4.1.18
Bumps tailwindcss from 3.4.19 to 4.1.18.
▶Release notes
Sourced from tailwindcss's releases.
v4.1.18
Fixed
- Ensure validation of
source(…)happens relative to the file it is in (#19274)- Include filename and line numbers in CSS parse errors (#19282)
- Skip comments in Ruby files when checking for class names (#19243)
- Skip over arbitrary property utilities with a top-level
!in the value (#19243)- Support environment API in
@tailwindcss/vite(#18970)- Preserve case of theme keys from JS configs and plugins (#19337)
- Write source maps correctly on the CLI when using
--watch(#19373)- Handle special defaults (like
ringColor.DEFAULT) in JS configs (#19348)- Improve backwards compatibility for
contenttheme key from JS configs (#19381)- Upgrade: Handle
futureandexperimentalconfig keys (#19344)- Try to canonicalize any arbitrary utility to a bare value (#19379)
- Validate candidates similarly to Oxide (#19397)
- Canonicalization: combine
text-*andleading-*classes (#19396)- Correctly handle duplicate CLI arguments (#19416)
- Don’t emit color-mix fallback rules inside
@keyframes(#19419)- CLI: Don't hang when output is
/dev/stdout(#19421)v4.1.17
Fixed
- Substitute
@variantinside legacy JS APIs (#19263)- Prevent occasional crash on Windows when loaded into a worker thread (#19242)
v4.1.16
Fixed
- Discard candidates with an empty data type (#19172)
- Fix canonicalization of arbitrary variants with attribute selectors (#19176)
- Fix invalid colors due to nested
&(#19184)- Improve canonicalization for
& > :pseudoand& :pseudoarbitrary variants (#19178)v4.1.15
Fixed
- Fix Safari devtools rendering issue due to
color-mixfallback (#19069)- Suppress Lightning CSS warnings about
:deep,:slotted, and:global(#19094)- Fix resolving theme keys when starting with the name of another theme key in JS configs and plugins (#19097)
- Allow named groups in combination with
not-*,has-*, andin-*(#19100)- Prevent important utilities from affecting other utilities (#19110)
- Don’t index into strings with the
theme(…)function (#19111)- Fix parsing issue when
\tis used in at-rules (#19130)- Upgrade: Canonicalize utilities containing
0values (#19095)- Upgrade: Migrate deprecated
break-wordstowrap-break-word(#19157)Changed
- Remove the
postinstallscript from oxide (#19149)
... (truncated)
▶Changelog
Sourced from tailwindcss's changelog.
[4.1.18] - 2025-12-11
Fixed
- Ensure validation of
source(…)happens relative to the file it is in (#19274)- Include filename and line numbers in CSS parse errors (#19282)
- Skip comments in Ruby files when checking for class names (#19243)
- Skip over arbitrary property utilities with a top-level
!in the value (#19243)- Support environment API in
@tailwindcss/vite(#18970)- Preserve case of theme keys from JS configs and plugins (#19337)
- Write source maps correctly on the CLI when using
--watch(#19373)- Handle special defaults (like
ringColor.DEFAULT) in JS configs (#19348)- Improve backwards compatibility for
contenttheme key from JS configs (#19381)- Upgrade: Handle
futureandexperimentalconfig keys (#19344)- Try to canonicalize any arbitrary utility to a bare value (#19379)
- Validate candidates similarly to Oxide (#19397)
- Canonicalization: combine
text-*andleading-*classes (#19396)- Correctly handle duplicate CLI arguments (#19416)
- Don’t emit color-mix fallback rules inside
@keyframes(#19419)- CLI: Don't hang when output is
/dev/stdout(#19421)
▶Commits
9b32f7cRelease v4.1.18 (#19431)820d907ExposecandidatesToAstto the language server (#19405)478e959Don’t emit color-mix fallback rules inside@keyframes(#19419)a5f4644Validate named values in candidate parser (#19397)229121dCanonicalization: combinetext-*andleading-*classes (#19396)243615eHandle backwards compatibility forcontenttheme from JS configs (#19381)7642751Improve compatibility with special default values in JS configs (#19348)af48117remove unnecessary intermediate check9e436f7Try to canonicalize any arbitrary utility to a bare value (#19379)479b725Bump Vitest to v4 (#19216)- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
+6
additions
-836
deletions
2
files changed