build(deps): bump tailwindcss from 4.1.8 to 4.1.10

[dependabot]

Bumps tailwindcss from 4.1.8 to 4.1.10.

Release notes

Sourced from tailwindcss's releases.

v4.1.10

Fixed

• Fix incorrectly generated CSS when using percentages in arbitrary values with calc (e.g. w-[calc(100%-var(--offset))]) (#18289)

v4.1.9

Fixed

• Correctly parse custom properties with strings containing semicolons (#18251)
• Upgrade: Migrate arbitrary modifiers without percentage signs to bare values (e.g. /[0.16] → /16) (#18184)
• Upgrade: Migrate CSS variable shorthands where fallback value contains function call (#18184)
• Upgrade: Migrate negative arbitrary values to negative bare values (e.g. mb-[-32rem] → -mb-128) (#18212)
• Upgrade: Do not migrate blur in wire:model.blur (#18216)
• Don't add spaces around CSS dashed idents when formatting math expressions (#18220)

Changelog

Sourced from tailwindcss's changelog.

[4.1.10] - 2025-06-11

Fixed

• Fix incorrectly generated CSS when using percentages in arbitrary values with calc (e.g. w-[calc(100%-var(--offset))]) (#18289)

[4.1.9] - 2025-06-11

Fixed

• Correctly parse custom properties with strings containing semicolons (#18251)
• Upgrade: Migrate arbitrary modifiers without percentage signs to bare values (e.g. /[0.16] → /16) (#18184)
• Upgrade: Migrate CSS variable shorthands where fallback value contains function call (#18184)
• Upgrade: Migrate negative arbitrary values to negative bare values (e.g. mb-[-32rem] → -mb-128) (#18212)
• Upgrade: Do not migrate blur in wire:model.blur (#18216)
• Don't add spaces around CSS dashed idents when formatting math expressions (#18220)

Commits

• d06bbb8 Prepare v4.1.10 (#18290)
• ddb0bef Fix missing space around - when using % regression (#18289)
• b88371a Prepare v4.1.9 (#18285)
• aa817fb fix: don't break CSS keywords when formatting math expressions (#18220)
• bea843c CSS Parser: Handle string with semi-colon in custom properties. (#18251)
• 8bfbac5 docs: fix typo in container.ts comment ("a the" -> "the") (#18223)
• See full diff 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)

[jazzberry-ai]

Bug Report

| framer-motion incompatibility | Medium | Update framer-motion and check components using animation. | The update of framer-motion from 12.16.0 to 12.18.1 might introduce compatibility issues with existing components that rely on specific framer-motion APIs. This could manifest as broken animations, unexpected behavior, or runtime errors, especially regarding peer dependency requirements with react and react-dom. Components using motion from framer-motion should be checked. |

_{Comments? Email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Potential Stale Styles due to Missing Content Configuration	Medium	1. Apply the patch. 2. Add a new React component (.tsx file) in the src/components directory that uses Tailwind CSS classes. 3. Build the application. 4. Verify if the styles for the new component are correctly applied.	The update to tailwindcss might have introduced changes in the default behavior of the purge/content functionality. Since there's no explicit tailwind.config.js or tailwind.config.ts file, the project relies on the default configuration within the @tailwindcss/vite plugin. If the default configuration doesn't include all the necessary file types or paths, the update might inadvertently remove styles for new components or files that are added to the project after the update. This can lead to stale styles or broken layouts.

_{Comments? Email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Potential wouter-preact incompatibility with preact 10.26.9	Medium	Navigate through different routes in the application.	The update to preact 10.26.9 might introduce subtle breaking changes that affect the compatibility with wouter-preact, leading to routing issues or rendering errors. Thoroughly test the routing functionality after the update.

_{Comments? Email us.}

[dependabot]

Superseded by #20.