chore: upgrade package version

[mduthey]

Summary by CodeRabbit

• Chores
  • Updated core framework dependencies including React, Vite, and development tooling to latest versions for improved stability and performance.

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

[coderabbitai]

Walkthrough

This PR updates dependencies in the dashboard frontend's package.json, including React (19.2.0→19.2.1), multiple TanStack libraries, devtools packages, Vite tooling (7.2.7), and related type definitions. No code modifications or API surface changes are included.

Changes

Cohort / File(s)	Summary
Frontend Dashboard Dependencies frontends/dashboard/package.json	Updated React and React DOM to ^19.2.1; bumped TanStack packages (react-query, react-router, react-router-ssr-query, react-start, router-plugin); updated devtools packages and associated type definitions; upgraded Vite to ^7.2.7 and @vitejs/plugin-react to ^5.1.2; updated @types/react to ^19.2.7 and @types/react-dom to ^19.2.3

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify package.json syntax and dependency lock consistency
• Confirm compatibility across multiple TanStack and Vite ecosystem updates
• Check if any breaking changes exist between updated versions that may require code adjustments

Possibly related PRs

• fix: upgrade packages version #23: Performs matching dependency version bumps for React/TanStack/Vite tooling in a different frontend package.json file (catalog), addressing similar ecosystem updates across the project.

Poem

🐰 Hop, hop, versions rise!
React and Vite in fresh disguise,
TanStack tools now gleam so bright,
Dependencies dance in the dashboard's light! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is generic and does not specifically identify which packages are being upgraded or the scope of the changes.	Consider using a more specific title like 'chore: upgrade dashboard dependencies to latest versions' or 'chore: update TanStack and Vite packages in dashboard'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 fix/upgrade-dashboard-packages

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 320eb6b and f907cfe.

⛔ Files ignored due to path filters (1)

• frontends/dashboard/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• frontends/dashboard/package.json (3 hunks)

🔇 Additional comments (3)

frontends/dashboard/package.json (3)

24-30: Verify breaking changes and compatibility for TanStack ecosystem upgrades.

Multiple TanStack packages are being updated to versions in the 1.140.x range (React Router, React Start, Query, etc.). These appear to be significant version bumps that may introduce breaking changes.

Additionally, devtools packages are being updated alongside their main counterparts, which need to remain in sync.

Ensure thorough testing of the updated interdependencies before merging, particularly:

• @tanstack/react-router with @tanstack/react-start
• @tanstack/react-query with @tanstack/react-query-devtools
• Compatibility of all TanStack packages with react@^19.2.1

Please verify the TanStack ecosystem updates by checking:

1. Release notes for breaking changes in the 1.140.x versions
2. Known compatibility issues between TanStack packages and React 19.2.1
3. Whether your test suite covers integration between these packages

Also applies to: 52-55

---

41-42: Clarify the React type definition version mismatch.

react and react-dom are pinned to ^19.2.1, but @types/react and @types/react-dom are updated to ^19.2.7 and ^19.2.3 respectively. This creates a version skew where type definitions are ahead of the runtime packages.

While this can work (caret ranges allow patch upgrades), it's unusual and could mask type safety issues if runtime and types diverge unexpectedly.

Verify the intention here:

• Is this intentional (e.g., types ahead for early type fixes)?
• Should React and React-DOM also be bumped to 19.2.7?
• Are there any type errors or warnings after this change in your local build?

Also applies to: 60-61

---

24-30: All specified package versions exist on npm and are not deprecated.

Verification confirms that all versions in the package.json exist on the npm registry and none are marked as deprecated or yanked, including:

• @tanstack/react-router@1.140.5
• @tanstack/react-query@5.90.12
• react@19.2.1
• vite@7.2.7

However, security advisories should still be checked by running npm audit in your development environment with the full dependency tree once the lock file is generated.