chore: update dependencies

[AbianS]

Summary by CodeRabbit

• Chores
  • Updated multiple dependency versions across the project stack, including UI components, styling frameworks, form management, development tools, and type definitions. These updates ensure compatibility and support for the latest library versions.

[coderabbitai]

Walkthrough

Multiple runtime and development dependencies are updated to newer versions in package.json, including Radix UI components, Tailwind-related packages, lucide-react, react-hook-form, Tauri CLI, Node types, Vitest UI, Vite, and Vitest. No public API changes or new exports.

Changes

Cohort / File(s)	Summary
Dependency Version Updates package.json	Updated versions for Radix UI (label, progress, separator, slot), Tailwind CSS ecosystem (vite integration, tailwindcss, tailwind-merge), lucide-react, react-hook-form, Tauri CLI, Node types, Vitest UI, Vite, and Vitest.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify dependency version compatibility and that lock file updates are consistent
• Confirm no breaking changes in updated packages that would affect existing functionality

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: update dependencies' is directly related to the main change in the changeset, which involves updating multiple dependency versions across runtime and devDependencies.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-dependencies

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ac33c01 and 673bea4.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Backend (Tests + Build)

🔇 Additional comments (4)

package.json (4)

78-78: Node.js version requirement increase with Vite 7.

Vite 7 requires Node.js 20.19+ or 22.12+, dropping support for Node.js 18. The project's @types/node@24.10.0 is compatible, but ensure CI/CD and local development environments meet this minimum version requirement.

Also applies to: 87-87

---

42-46: Good: Minor Radix UI and package version coordination.

The Radix UI component version updates and the aligned versions for Tailwind ecosystem packages (@tailwindcss/vite and tailwindcss both at 4.1.17) show attention to version coherence. The React plugin is compatible with Vite 7, removing upgrade friction on the frontend toolchain.

Also applies to: 61-61, 64-64, 68-69

---

87-88: The review comment is not applicable to this codebase and should be dismissed.

The warning focuses on browser provider API changes (string → object) and performance regression concerns. However, inspection of vitest.config.ts reveals that this project:

• Uses jsdom environment, not browser provider
• Does not have @vitest/browser as a dependency
• Does not configure any browser provider
• Only specifies coverage provider as { provider: 'v8' }, which is already in the correct object format

The browser provider API migration step mentioned in the review comment is not applicable here. The codebase's vitest configuration is already compliant with Vitest 4 standards.

Likely an incorrect or invalid review comment.

---

50-50: ****

The CSS in this project is already using Tailwind CSS v4 syntax. The App.css file imports with @import "tailwindcss" (not @tailwind directives), uses @theme inline {} for configuration, and correctly nests @apply directives within @layer blocks—all of which are Tailwind v4 patterns. The project also uses the @tailwindcss/vite plugin which handles CSS compilation automatically. No manual migration of CSS files, configuration updates, or running the migration tool is needed. The dependency update to @tailwindcss/vite 4.1.17 is compatible with the existing setup.

Likely an incorrect or invalid review comment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}