chore(ui): updated dependencies to latest versions for March 2025

[billcookie]

Overview

March 2025 (monthly dependencies update)

What I've done

What I haven't done

How I tested

Screenshot

Which point I want you to review particularly

Memo

Dependencies not upgraded:

• Tailwind from 3.4 > 4.0 (will require refactor and attention, so task has been created)
• Radix Ui (shadcn): currently breaking scroll area

Summary by CodeRabbit

• Chores
  • Updated various third-party libraries and developer tools to enhance overall performance, stability, and compatibility for a smoother user experience.

[coderabbitai]

Walkthrough

This pull request updates several package versions in the ui/package.json file. Both production dependencies and development dependencies have been incremented to newer versions. No modifications were made to exported or public entity declarations.

Changes

File	Change Summary
ui/package.json (dependencies)	Updated versions for packages including @rjsf/core, @rjsf/utils, @rjsf/validator-ajv8, @tanstack/react-query, @tanstack/react-router, @tanstack/react-table, @xyflow/react, cesium, cmdk, i18next, i18next-browser-languagedetector, jotai, react-datepicker, react-i18next, uuid, and yjs.
ui/package.json (devDependencies)	Updated versions for various packages: multiple @graphql-codegen/*, @storybook/*, @tanstack/* packages, type definitions (e.g., @types/file-saver, @types/react, @types/react-dom), and utility packages like eslint, prettier, typescript, vite, and vitest.

Possibly related PRs

• chore(ui): Feb Dependencies Update  #848: The changes in the main PR and the retrieved PR are related as both involve updates to the same @rjsf/core, @rjsf/utils, and @rjsf/validator-ajv8 packages, indicating a direct connection at the code level.

Poem

I’m a rabbit with hops so light,
Celebrating version bumps with delight,
Packages updated to shine anew,
Dependencies dancing in a colorful queue,
I nibble on code both day and night,
With every update, my heart feels bright!
🐰 Happy coding in moonlit bytes!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 172446d and e65c496.

⛔ Files ignored due to path filters (1)

• ui/yarn.lock is excluded by !**/yarn.lock, !**/*.lock, !**/*.lock

📒 Files selected for processing (1)

• ui/package.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• ui/package.json

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: ci
• GitHub Check: Redirect rules - reearth-flow
• GitHub Check: Header rules - reearth-flow
• GitHub Check: Pages changed - reearth-flow

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

✅ Deploy Preview for reearth-flow ready!

Name	Link
🔨 Latest commit	e65c496
🔍 Latest deploy log	https://app.netlify.com/sites/reearth-flow/deploys/67e23c8b37d76100084e7313
😎 Deploy Preview	https://deploy-preview-1082--reearth-flow.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

ui/package.json (1)

137-137: TailwindCSS Version Maintained by Design
The tailwindcss dependency remains pinned at version 3.4.17 as noted in the PR objectives, pending a planned refactor for an upgrade to version 4.0. Ensure that this decision is documented and communicated with the team, especially if any Tailwind-related issues are encountered in the future.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ed32d93 and 172446d.

⛔ Files ignored due to path filters (1)

• ui/yarn.lock is excluded by !**/yarn.lock, !**/*.lock, !**/*.lock

📒 Files selected for processing (1)

• ui/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Collect information

🔇 Additional comments (17)

ui/package.json (17)

57-64: Dependency Updates – rjsf and TanStack Packages
The versions for @rjsf/core, @rjsf/utils, @rjsf/validator-ajv8, @tanstack/react-query, @tanstack/react-router, @tanstack/react-table, @xyflow/react, and cesium have been bumped. These appear to be routine minor/patch upgrades. Please verify via changelogs that no breaking changes were introduced and that these updates remain compatible with the rest of the stack.

---

67-67: Update for cmdk Package
The dependency cmdk has been updated from 1.0.4 to 1.1.1. This minor version bump should be safe; however, it’s good to validate that any components relying on it function as expected.

---

74-76: Internationalization and State Management Libraries Update
The upgrades for i18next, i18next-browser-languagedetector, and jotai are straightforward. Ensure that these updates do not inadvertently affect locale detection or state handling flows.

---

81-83: React-Datepicker and React-i18next Upgrade
The new versions for react-datepicker and react-i18next appear to be patch-level updates. It is advisable to double-check visual components (date picker UI) and internationalization outputs following these upgrades to maintain consistency.

---

88-90: UUID and Yjs Version Bumps
The minor updates for uuid and yjs should provide incremental improvements. Please verify that UUID generation and collaborative features (if using Yjs) continue to behave as expected after these changes.

---

93-97: GraphQL Code Generator Tools Update
The GraphQL Codegen packages (@graphql-codegen/cli, @graphql-codegen/client-preset, @graphql-codegen/typescript, and @graphql-codegen/typescript-operations) have been updated. These upgrades should streamline code generation, but it is important to run the codegen process and tests to ensure compatibility with your GraphQL schema and operations.

---

100-107: Storybook Addons and Related Packages Update
Storybook-related packages have been uniformly updated to version 8.6.7. This consistency is beneficial; nonetheless, please verify that the Storybook interface, component previews, and interactions work as expected after these updates.

---

108-110: TanStack Dev Tools Consistency
The updates for @tanstack/react-query-devtools, @tanstack/router-devtools, and @tanstack/router-vite-plugin help align the development tools with their runtime counterparts. This change promotes consistency, but a fresh run of the dev environment and tests is recommended.

---

114-119: Type Definitions Enhancements
The type declarations for @types/file-saver, @types/react, and @types/react-dom have been updated. Ensure these align with the rest of your TypeScript configuration and do not introduce any type conflicts.

---

122-123: Vitest Coverage and Autoprefixer Upgrades
The updates for @vitest/coverage-v8 and autoprefixer should offer bug fixes and performance improvements. It is advisable to run your test suite and CSS build process to catch any regressions.

---

125-126: ESLint and Configuration Updates
eslint and eslint-config-reearth have been bumped. Since these tools enforce coding standards, please run the linter locally to ensure that the updates do not introduce unexpected warnings or errors.

---

128-128: ESLint-Plugin-Storybook Update
The eslint-plugin-storybook update to version 0.11.6 is in line with other Storybook package updates. Verify that Storybook linting remains smooth post-update.

---

130-130: i18next-parser Upgrade
Upgrading i18next-parser to 9.3.0 should help with extraction tasks for localization. Confirm that its configuration continues to correctly extract i18n strings from your source code.

---

132-133: PostCSS and Prettier Version Bumps
The PostCSS and Prettier updates are minor but can affect build output or code formatting, respectively. It is recommended to run a full build and format check to ensure there are no surprises.

---

135-135: Storybook Package Consistency
The storybook package has been updated to 8.6.7, which aligns with its addon counterparts. Visual regression testing in Storybook would be beneficial to confirm that no components have been adversely affected.

---

140-141: Typescript and Vite Upgrades
Upgrading typescript to 5.8.2 and vite to 6.2.2 can bring performance improvements and new features. Please ensure your build process and type-checking continue to work seamlessly with these updated versions.

---

143-143: Vitest Upgrade
The upgrade to vitest version 3.0.9 should enhance testing reliability. Running your full test suite is recommended to guarantee that all tests pass successfully following the update.