Update tailwindcss 3.4.4 → 3.4.18 (patch) #152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 (3.4.4 → 3.4.18) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 59 commits:
v3: Bundle postcss-load-config v4 with the standalone CLI (#19042)Prepare v3.4.18 release (#19038)v3: Remove irrelevant utility rules when matching important classes (#19030)Fix native ESM config loading in v3 (#18938)Fix `require.cache` error when loaded through a typescript file in Node 22.18+ (#18665)v3: Allow hyphen character in regex pattern to use support queries as is (#13605)Fix errorv3.4.17Update changelogWork around issue with Node 22 and Jiti (#15421)Bump macos versionv3.4.16fix: update lilconfig for ESM and Windows support (#15289)Fix Plugin type issue (#14668)v3.4.15Add variable fallback to fix Chrome issue (#15003)Fix config types for boxShadow (#14856)update changelogAdd `CODEOWNERS` file (#14702)Bump dependencies to fix vulnerabilities (#14697)3.4.14Don't set `display: none` on elements that use `hidden="until-found"` (#14625)3.4.13Improve the performance when checking broad glob patterns. (#14481)3.4.12Insert `@defaults` at start of stylesheet (#14427)3.4.11update changelogAllow `anchor-size(…)` in arbitrary values (#14393)3.4.10Bump versions of plugins in the Standalone CLI (#14185)3.4.9Don't warn about broad globs in vendor folders (#14147)3.4.8rename `master` to `main`Warn when broad glob patterns are used in the content configuration (#14140)Bump to latest cssnano v6 (#14105)Automate checksum generation for standalone CLI (#14081)Update version in package.jsonAdd missing heading to changelogUpdate changelog for v3.4.7Update CHANGELOG.mdNormalize attribute selector for `data-*` and `aria-*` modifiers (#14037)Print eventual lightning CSS parsing errors when the CSS matcher fail (#14034)Fix class detection in Slim templates with attached attributes and IDs (#14019)Update changelogLoosen :is() wrapping rules in applyImportantSelector for more readable output. (#13900)3.4.6Update changelogFix extracting utilities from slim/pug templates (#14006)Update runner image3.4.5Always generate -webkit-backdrop-filter property (#13997)Avoid over-extracting utilities from candidates with decimal values (#13959)Add `.mts` and `.cts` config file detection (#13940)refactor(util): code refactor (#13872)fix: typo (#13864)Use no value instead of `blur(0px)` for `backdrop-blur-none` and `blur-none` utilities (#13830)Disable automatic `var()` injection for anchor properties (#13826)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