feat: update package versions across v2 apps

[kemuru]

PR-Codex overview

This PR focuses on updating dependencies in the package.json and yarn.lock files, specifically upgrading various @types packages, react, react-dom, vite, and rollup to their latest versions, as well as updating other related packages.

Detailed summary

• Updated @types/react from 18.2.0 to ^18.2.59.
• Updated react from ^18.2.0 to ^18.3.1.
• Updated react-dom from ^18.2.0 to ^18.3.1.
• Added vite with version ^5.4.2.
• Updated rollup from ^4.13.0 to ^4.20.0.
• Updated postcss from ^8.4.39 to ^8.4.43.
• Updated source-map-js from ^1.2.0 to ^1.2.1.
• Updated scheduler from ^0.23.2 to 0.23.2.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

• New Features

  • Introduced the vite dependency to enhance development performance.

• Updates

  • Updated @types/react, react, and react-dom to their latest versions for improved functionality and compatibility.

[coderabbitai]

Walkthrough

The pull request involves updates to the package.json file for the @kleros/escrow-v2-web project. Key changes include the upgrading of several dependencies, specifically @types/react, react, react-dom, and the introduction of a new dependency, vite. The updates reflect changes in versioning to ensure compatibility with the latest features and fixes, while the overall structure of the package.json remains unchanged.

Changes

File	Change Summary
web/package.json	- Updated @types/react from 18.2.0 to ^18.2.59
	- Updated react from ^18.2.0 to ^18.3.1
	- Updated react-dom from ^18.2.0 to ^18.3.1
	- Updated vite from ^5.2.10 to ^5.4.2
	- Various updates to devDependencies for compatibility

Possibly related PRs

• chore(web): bump-ui-components-library-to-2.15.0 #82: The changes in this PR also involve updates to the package.json file, specifically modifying dependency versions, which aligns with the main PR's focus on dependency updates.

Suggested reviewers

• alcercu

Poem

🐇 In the garden of code, we hop with glee,
New versions sprout, as fresh as can be.
With react and vite, our tools now refined,
A patchwork of updates, all perfectly aligned.
So let’s dance through the branches, let our code sing,
For each little change, a new joy we bring! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4f14169 and f1ecbcd.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• web/package.json (3 hunks)

🧰 Additional context used

🔇 Additional comments (5)

web/package.json (5)

98-98: Approve react-dom update, noting synchronization with React.

The update of react-dom from "^18.2.0" to "^18.3.1" correctly mirrors the React update. This synchronization is crucial for maintaining compatibility between React and ReactDOM.

---

67-67: Approve Vite update with a changelog review recommendation.

The update from "^5.2.10" to "^5.4.2" for Vite represents multiple minor version updates. This likely includes performance improvements and bug fixes.

To ensure a smooth transition and take advantage of new features, please review the Vite changelog for any relevant updates or potential breaking changes. You can use the following command to open the changelog:

#!/bin/bash
# Description: Open Vite changelog in the default browser.
open https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md

---

Line range hint 52-98: Summary of package updates and recommendations.

The package.json file has been updated with several key dependency changes:

1. @types/react: "18.2.0" → "^18.2.59"
2. react: "^18.2.0" → "^18.3.1"
3. react-dom: "^18.2.0" → "^18.3.1"
4. vite: "^5.2.10" → "^5.4.2"

These updates appear to be part of a general dependency upgrade process. All changes follow good practices by using caret ranges for flexibility in patch and minor updates.

To ensure a smooth transition with these updates:

1. Run a full test suite to catch any potential issues.
2. Review the changelogs of the updated packages, especially React and Vite, for any breaking changes or new features that might affect your project.
3. Consider updating other related dependencies that might depend on these packages to ensure full compatibility.

You can use the following command to run your test suite:

#!/bin/bash
# Description: Run the project's test suite.
yarn test

---

52-52: Approve @types/react update with a compatibility check recommendation.

The update from "18.2.0" to "^18.2.59" for @types/react is a significant jump in patch version. This update likely includes important type definition improvements and bug fixes.

To ensure compatibility, please run the following command to check for any type-related issues:

---

96-96: Approve React update with a changelog review recommendation.

The update from "^18.2.0" to "^18.3.1" for React is a minor version bump. This update likely includes new features and improvements.

To ensure a smooth transition, please review the React changelog for any breaking changes or new features that might affect your project. You can use the following command to open the changelog:

---

🪧 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 resolve resolve all the CodeRabbit review comments.
• @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 or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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 kleros-escrow-v2 ready!

Name	Link
🔨 Latest commit	f1ecbcd
🔍 Latest deploy log	https://app.netlify.com/sites/kleros-escrow-v2/deploys/6706848a6c5a240008c2bec0
😎 Deploy Preview	https://deploy-preview-83--kleros-escrow-v2.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.

[alcercu]

lgtm