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

[dependabot]

Bumps tailwindcss from 3.4.17 to 4.1.16.

Release notes

Sourced from tailwindcss's releases.

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 & > :pseudo and & :pseudo arbitrary variants (#19178)

v4.1.15

Fixed

• Fix Safari devtools rendering issue due to color-mix fallback (#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-*, and in-* (#19100)
• Prevent important utilities from affecting other utilities (#19110)
• Don’t index into strings with the theme(…) function (#19111)
• Fix parsing issue when \t is used in at-rules (#19130)
• Upgrade: Canonicalize utilities containing 0 values (#19095)
• Upgrade: Migrate deprecated break-words to wrap-break-word (#19157)

Changed

• Remove the postinstall script from oxide (#19149)

v4.1.14

Fixed

• Handle ' syntax in ClojureScript when extracting classes (#18888)
• Handle @variant inside @custom-variant (#18885)
• Merge suggestions when using @utility (#18900)
• Ensure that file system watchers created when using the CLI are always cleaned up (#18905)
• Do not generate grid-column utilities when configuring grid-column-start or grid-column-end (#18907)
• Do not generate grid-row utilities when configuring grid-row-start or grid-row-end (#18907)
• Prevent duplicate CSS when overwriting a static utility with a theme key (#18056)
• Show Lightning CSS warnings (if any) when optimizing/minifying (#18918)
• Use default export condition for @tailwindcss/vite (#18948)
• Re-throw errors from PostCSS nodes (#18373)
• Detect classes in markdown inline directives (#18967)
• Ensure files with only @theme produce no output when built (#18979)
• Support Maud templates when extracting classes (#18988)
• Upgrade: Do not migrate variant = 'outline' during upgrades (#18922)
• Upgrade: Show version mismatch (if any) when running upgrade tool (#19028)
• Upgrade: Ensure first class inside className is migrated (#19031)
• Upgrade: Migrate classes inside *ClassName and *Class attributes (#19031)

v4.1.13

Changed

• Drop warning from browser build (#18731)

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.1.16] - 2025-10-23

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 & > :pseudo and & :pseudo arbitrary variants (#19178)

[4.1.15] - 2025-10-20

Fixed

• Fix Safari devtools rendering issue due to color-mix fallback (#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-*, and in-* (#19100)
• Prevent important utilities from affecting other utilities (#19110)
• Don’t index into strings with the theme(…) function (#19111)
• Fix parsing issue when \t is used in at-rules (#19130)
• Upgrade: Canonicalize utilities containing 0 values (#19095)
• Upgrade: Migrate deprecated break-words to wrap-break-word (#19157)

Changed

• Remove the postinstall script from oxide (#19149)(tailwindlabs/tailwindcss#19149)

[4.1.14] - 2025-10-01

Fixed

• Handle ' syntax in ClojureScript when extracting classes (#18888)
• Handle @variant inside @custom-variant (#18885)
• Merge suggestions when using @utility (#18900)
• Ensure that file system watchers created when using the CLI are always cleaned up (#18905)
• Do not generate grid-column utilities when configuring grid-column-start or grid-column-end (#18907)
• Do not generate grid-row utilities when configuring grid-row-start or grid-row-end (#18907)
• Prevent duplicate CSS when overwriting a static utility with a theme key (#18056)
• Show Lightning CSS warnings (if any) when optimizing/minifying (#18918)
• Use default export condition for @tailwindcss/vite (#18948)
• Re-throw errors from PostCSS nodes (#18373)
• Detect classes in markdown inline directives (#18967)
• Ensure files with only @theme produce no output when built (#18979)
• Support Maud templates when extracting classes (#18988)
• Upgrade: Do not migrate variant = 'outline' during upgrades (#18922)
• Upgrade: Show version mismatch (if any) when running upgrade tool (#19028)
• Upgrade: Ensure first class inside className is migrated (#19031)
• Upgrade: Migrate classes inside *ClassName and *Class attributes (#19031)

[4.1.13] - 2025-09-03

... (truncated)

Commits

• cbbbe84 Release 4.1.16 (#19185)
• 601d671 Fix incorrect colors used in pseudo-element (#19184)
• a41add9 Improve canonicalization for & > :pseudo and & :pseudo arbitrary variants...
• 0113b88 Fix canonicalization of arbitrary variants with attribute selectors (#19176)
• 29687e0 Discard candidates with an empty data type (#19172)
• 56e7f3b Improve memory usage during canonicalization (#19171)
• 3a4ab82 Stop suggesting legacy utilities (#19169)
• 7537e34 Ignore --tw- variables during internal signature computation (#19156)
• 66c18ca Collapse multiple utilities (#19147)
• b2e2435 Release 4.1.15 (#19159)
• 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 from TailwindCSS v3 to v4 may introduce breaking changes

Category
Correctness
Code Snippet
Lines 33 and 73-74 in package.json and pnpm-lock.yaml:

• "tailwindcss": "^3.4.16",

• "tailwindcss": "^4.1.16",
  Recommendation
  Review TailwindCSS v4 migration guide and update configuration files accordingly. Check for deprecated utilities, configuration syntax changes, and ensure all existing styles still work. Consider updating tailwind.config.js to use the new v4 syntax and test the build process thoroughly.
  Reasoning
  TailwindCSS v4 introduces significant breaking changes including new configuration syntax, deprecated utilities (like break-words → wrap-break-word mentioned in changelog), and new features that may require code changes to maintain compatibility.

Mixed TailwindCSS versions in lockfile dependencies

Category
Maintainability
Code Snippet
Lines in pnpm-lock.yaml:
tailwindcss: 4.1.16 (main dependency)
tailwindcss: 3.4.18 (transitive dependency via vite)
Recommendation
Ensure all TailwindCSS-related packages and plugins are compatible with v4. Update or verify compatibility of @tailwindcss/typography and any other TailwindCSS plugins. Consider updating the entire toolchain to use consistent versions.
Reasoning
Having mixed versions of TailwindCSS in the dependency tree can lead to inconsistent behavior, styling conflicts, and potential runtime errors. The lockfile shows both v3.4.18 and v4.1.16 which indicates some dependencies haven't been updated to support v4.

Verify build performance impact of TailwindCSS v4 upgrade

Category
Performance
Code Snippet
Package.json change from v3 to v4 across the entire project
Recommendation
Test build times and bundle sizes before and after the upgrade. TailwindCSS v4 has significant architectural changes that may affect performance. Monitor for any regression in build speed or output size, and optimize configuration if needed.
Reasoning
TailwindCSS v4 includes major performance improvements and new optimization features, but the architectural changes may also introduce different performance characteristics that should be validated in the specific project context.