chore(deps): update dependencies and tauri packages

[AbianS]

Summary by CodeRabbit

• Chores

  • Updated project dependencies to latest versions for improved stability and security.
  • Enhanced build tooling and testing infrastructure with latest tool versions.

• Improvements

  • Enabled CSS parser configuration to improve support for utility-first styling frameworks.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The pull request updates configuration files and dependency versions across the project. It bumps the Biome JSON schema from 2.2.5 to 2.3.7 with added CSS parser configuration for Tailwind directives, updates multiple JavaScript/TypeScript package versions in package.json, and increments Rust dependency versions in src-tauri/Cargo.toml.

Changes

Cohort / File(s)	Change Summary
Configuration Updates biome.json	Updates JSON schema reference from 2.2.5 to 2.3.7 and adds CSS parser configuration to enable Tailwind directives
JavaScript/TypeScript Dependencies package.json	Bumps runtime dependencies: lucide-react (0.553.0 → 0.555.0), react-hook-form (7.66.0 → 7.66.1), zod (4.1.12 → 4.1.13); bumps dev dependencies: @biomejs/biome (2.2.5 → 2.3.7), @types/node (24.10.0 → 24.10.1), @types/react (19.2.2 → 19.2.7), @types/react-dom (19.2.2 → 19.2.3), @vitejs/plugin-react (5.1.0 → 5.1.1), @vitest/ui (4.0.8 → 4.0.14), jsdom (27.1.0 → 27.2.0), vite (7.2.2 → 7.2.4), vitest (4.0.8 → 4.0.14)
Rust Dependencies src-tauri/Cargo.toml	Updates tauri-build (2.5.1 → 2.5.2) and tauri (2.9.2 → 2.9.3)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Version bumps are straightforward across all manifests with no logic changes
• Verify Biome schema compatibility and CSS parser configuration correctness
• Confirm dependency compatibility between correlated version updates (e.g., @vitest/ui and vitest both bump from 4.0.8 to 4.0.14)

Possibly related PRs

• chore: update dependencies #29: Overlapping dependency version bumps in package.json affecting lucide-react, react-hook-form, vitest, vite, and TypeScript type definitions packages

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 clearly and accurately summarizes the main change: updating dependencies across multiple manifest files (package.json, biome.json, Cargo.toml) and tauri packages specifically.
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 5123a0a and 63b8f00.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (3)

• biome.json (1 hunks)
• package.json (1 hunks)
• src-tauri/Cargo.toml (1 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 (5)

package.json (3)

61-61: Core dependency updates are safe.

Minor application dependency updates (lucide-react, react-hook-form, zod) are all patch/minor increments and pose minimal risk.

Also applies to: 64-64, 70-70

---

73-73: Biome and type definitions updates align with configuration changes.

@biomejs/biome 2.3.7 update aligns with the schema change in biome.json. Type definition updates (@types/node, @types/react, @types/react-dom) and @vitejs/plugin-react updates are all patch-level and safe.

Also applies to: 78-82

---

83-88: All version updates are verified as backwards-compatible with no documented breaking changes.

The package.json versions are confirmed correct:

• vitest and @vitest/ui: 4.0.14 (patch update from 4.0.8)
• vite: 7.2.4 (patch update from 7.2.2)
• jsdom: 27.2.0 (minor update from 27.1.0)

Both vitest.config.ts and vite.config.ts exist and are properly configured with no syntax issues. Web search confirms that vitest releases from 4.0.8 through 4.0.14 contain no breaking changes—only bugfixes and performance improvements. Patch-level and minor version updates are designed to be backwards-compatible by semantic versioning standards. No CI/CD or test setup issues are evident from configuration inspection.

src-tauri/Cargo.toml (1)

21-21: Tauri patch updates verified as safe and compatible.

The version claims are accurate: tauri-build is at 2.5.2 and tauri is at 2.9.3. These patch-level updates are backwards-compatible. The Rust-side versions (tauri 2.9.3, tauri-build 2.5.2) remain compatible with the Node-side @tauri-apps versions (@tauri-apps/cli 2.9.4, @tauri-apps/api 2.9.0)—minor version differences between Rust and Node sides are expected and safe.

biome.json (1)

2-7: Schema and CSS parser configuration update is correct and properly aligned.

The schema bump to 2.3.7 matches the @biomejs/biome devDependency version (confirmed in package.json). The tailwindDirectives: true setting is a legitimate Biome 2.3+ feature that enables parsing of Tailwind v4 directives (@theme, @Utility, @apply), and the project actively uses TailwindCSS dependencies (@tailwindcss/vite, tailwindcss, tailwind-merge). The configuration syntax is correct per Biome documentation.

Note: There are known parser edge cases with some Tailwind plugins (e.g., DaisyUI @plugin syntax), but this does not invalidate the configuration for standard Tailwind usage.

---

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.}