chore(deps-dev): bump tailwindcss from 3.4.17 to 4.1.13 in /moonbit-tour

[dependabot]

Bumps tailwindcss from 3.4.17 to 4.1.13.

Release notes

Sourced from tailwindcss's releases.

v4.1.13

Changed

• Drop warning from browser build (#18731)
• Drop exact duplicate declarations when emitting CSS (#18809)

Fixed

• Don't transition visibility when using transition (#18795)
• Discard matched variants with unknown named values (#18799)
• Discard matched variants with non-string values (#18799)
• Show suggestions for known matchVariant values (#18798)
• Replace deprecated clip with clip-path in sr-only (#18769)
• Hide internal fields from completions in matchUtilities (#18820)
• Ignore .vercel folders by default (can be overridden by @source … rules) (#18855)
• Consider variants starting with @- to be invalid (e.g. @-2xl:flex) (#18869)
• Do not allow custom variants to start or end with a - or _ (#18867, #18872)
• Upgrade: Migrate aria theme keys to @custom-variant (#18815)
• Upgrade: Migrate data theme keys to @custom-variant (#18816)
• Upgrade: Migrate supports theme keys to @custom-variant (#18817)

v4.1.12

Fixed

• Don't consider the global important state in @apply (#18404)
• Add missing suggestions for flex-<number> utilities (#18642)
• Fix trailing ) from interfering with extraction in Clojure keywords (#18345)
• Detect classes inside Elixir charlist, word list, and string sigils (#18432)
• Track source locations through @plugin and @config (#18345)
• Allow boolean values of process.env.DEBUG in @tailwindcss/node (#18485)
• Ignore consecutive semicolons in the CSS parser (#18532)
• Center the dropdown icon added to an input with a paired datalist by default (#18511)
• Extract candidates in Slang templates (#18565)
• Improve error messages when encountering invalid functional utility names (#18568)
• Discard CSS AST objects with false or undefined properties (#18571)
• Allow users to disable URL rebasing in @tailwindcss/postcss via transformAssetUrls: false (#18321)
• Fix false-positive migrations in addEventListener and JavaScript variable names (#18718)
• Fix Standalone CLI showing default Bun help when run via symlink on Windows (#18723)
• Read from --border-color-* theme keys in divide-* utilities for backwards compatibility (#18704)
• Don't scan .hdr and .exr files for classes by default (#18734)

v4.1.11

Fixed

• Add heuristic to skip candidate migrations inside emit(…) (#18330)
• Extract candidates with variants in Clojure/ClojureScript keywords (#18338)
• Document --watch=always in the CLI's usage (#18337)
• Add support for Vite 7 to @tailwindcss/vite (#18384)

v4.1.10

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.1.13] - 2025-09-03

Changed

• Drop warning from browser build (#18731)
• Drop exact duplicate declarations when emitting CSS (#18809)

Fixed

• Don't transition visibility when using transition (#18795)
• Discard matched variants with unknown named values (#18799)
• Discard matched variants with non-string values (#18799)
• Show suggestions for known matchVariant values (#18798)
• Replace deprecated clip with clip-path in sr-only (#18769)
• Hide internal fields from completions in matchUtilities (#18820)
• Ignore .vercel folders by default (can be overridden by @source … rules) (#18855)
• Consider variants starting with @- to be invalid (e.g. @-2xl:flex) (#18869)
• Do not allow custom variants to start or end with a - or _ (#18867, #18872)
• Upgrade: Migrate aria theme keys to @custom-variant (#18815)
• Upgrade: Migrate data theme keys to @custom-variant (#18816)
• Upgrade: Migrate supports theme keys to @custom-variant (#18817)

[4.1.12] - 2025-08-13

Fixed

• Don't consider the global important state in @apply (#18404)
• Add missing suggestions for flex-<number> utilities (#18642)
• Fix trailing ) from interfering with extraction in Clojure keywords (#18345)
• Detect classes inside Elixir charlist, word list, and string sigils (#18432)
• Track source locations through @plugin and @config (#18345)
• Allow boolean values of process.env.DEBUG in @tailwindcss/node (#18485)
• Ignore consecutive semicolons in the CSS parser (#18532)
• Center the dropdown icon added to an input with a paired datalist by default (#18511)
• Extract candidates in Slang templates (#18565)
• Improve error messages when encountering invalid functional utility names (#18568)
• Discard CSS AST objects with false or undefined properties (#18571)
• Allow users to disable URL rebasing in @tailwindcss/postcss via transformAssetUrls: false (#18321)
• Fix false-positive migrations in addEventListener and JavaScript variable names (#18718)
• Fix Standalone CLI showing default Bun help when run via symlink on Windows (#18723)
• Read from --border-color-* theme keys in divide-* utilities for backwards compatibility (#18704)
• Don't scan .hdr and .exr files for classes by default (#18734)

[4.1.11] - 2025-06-26

Fixed

• Add heuristic to skip candidate migrations inside emit(…) (#18330)
• Extract candidates with variants in Clojure/ClojureScript keywords (#18338)
• Document --watch=always in the CLI's usage (#18337)

... (truncated)

Commits

• 1334c99 Prepare v4.1.13 release (#18868)
• 65dc530 Do not allow variants to end with - or _ (#18872)
• 54c3f30 Do not allow variants to start with - (#18867)
• 494051c Consider variants starting with @- to be invalid (e.g. @-2xl:flex) (#18869)
• c318329 chore: remove redundant words (#18853)
• ddc84b0 update test after prettier change
• f1331a8 run prettier
• e5513b6 Fix missing code block delimiters in comment blocks (#18837)
• 5e2a160 Drop exact duplicate declarations from output CSS within a style rule (#18809)
• b1fb02a Hide internal fields from completions in matchUtilities (#18820)
• 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)

[peter-jerry-ye-code-review]

Major version upgrade may introduce breaking changes requiring code updates

Category
Correctness
Code Snippet
Lines 32, 70: tailwindcss upgraded from ^3.4.16 to ^4.1.13
Recommendation
Review TailwindCSS v4 migration guide and test all styling functionality. Key breaking changes include: new CSS-first configuration, removal of deprecated utilities, and changes to plugin APIs. Consider updating tailwind.config.js and verifying all CSS classes still work as expected.
Reasoning
Major version upgrades typically introduce breaking changes that can cause styling regressions or build failures if not properly tested and migrated

Missing configuration updates for TailwindCSS v4

Category
Maintainability
Code Snippet
Package.json shows version bump but no config file changes visible
Recommendation
Ensure tailwind.config.js is updated for v4 syntax. TailwindCSS v4 uses a new CSS-first configuration approach with @config directives instead of JavaScript config files. Update build processes and verify compatibility with @tailwindcss/typography plugin.
Reasoning
TailwindCSS v4 introduces a fundamentally different configuration system that requires updates to existing config files and build processes

Potential build performance implications with new CSS engine

Category
Performance
Code Snippet
[email protected] introduces new Rust-based engine
Recommendation
Monitor build times and bundle sizes after upgrade. TailwindCSS v4 includes a new Rust-based CSS engine that should improve performance, but may require build process adjustments. Test development and production builds thoroughly.
Reasoning
Major infrastructure changes like the new CSS engine can impact build performance and may require optimization of existing build pipelines