Chore(deps): Bump packages

[black7375]

Description

Bump packages

Related Issue

Summary by CodeRabbit

• Chores
  • Upgraded Yarn to version 4.6.0 to streamline dependency management.
  • Refreshed multiple core dependencies—such as React (upgraded from v18 to v19), linting and type-checking tools, and various plugins—to enhance stability and performance.
  • Updated supporting libraries for styling and logging, ensuring a modern and consistent development experience.

Additional context

Checklist

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0c90487

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

This pull request upgrades the Yarn version and updates a range of dependency versions across various package configuration files. The changes affect the yarn configuration file along with multiple package.json files in configuration, example, and package directories. All modifications involve version bumps and dependency updates with no changes to runtime control flow.

Changes

File(s)	Change Summary
.yarnrc.yml	Updated yarnPath from yarn-4.5.3.cjs to yarn-4.6.0.cjs.
configs/eslint-config-custom/package.json	Upgraded devDependencies: @eslint/js (^9.16.0 → ^9.19.0), @typescript-eslint/parser (^8.17.0 → ^8.23.0), eslint-config-prettier (^9.1.0 → ^10.0.1), eslint-plugin-prettier (^5.2.1 → ^5.2.3), globals (^15.13.0 → ^15.14.0), typescript-eslint (^8.17.0 → ^8.23.0).
configs/vite-config-custom/package.json	Upgraded devDependencies: vite-plugin-dts (^4.3.0 → ^4.5.0), vite-plugin-externalize-deps (^0.8.0 → ^0.9.0), vite-tsconfig-paths (^5.1.3 → ^5.1.4).
examples/react-swc/package.json	Upgraded dependencies: react and react-dom (^18.3.1 → ^19.0.0); and updated multiple devDependencies including @eslint/compat, @eslint/js, @types/react, @types/react-dom, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, various @vanilla-extract/* packages, eslint, eslint-plugin-react-hooks, eslint-plugin-react-refresh, globals, typescript, typescript-eslint, and vite.
package.json	Updated packageManager from yarn@4.5.3 to yarn@4.6.0 and upgraded devDependencies: @changesets/cli, @types/node, @vanilla-extract/vite-plugin, @vitest/coverage-v8, c8, eslint, prettier; as well as dependencies: terser, turbo, typescript, vite, vite-node, and vitest to newer versions.
packages/css/package.json packages/transform-to-vanilla/package.json	Upgraded dependencies: @fastify/deepmerge (^2.0.0 → ^2.0.2) and @vanilla-extract/css (^1.16.1 → ^1.17.1).
packages/debug-log/package.json	Upgraded dependency: chalk (^5.3.0 → ^5.4.1).

Poem

I'm a rabbit who hops with glee,
Upgrading code as swift as can be.
Dependencies dance in versioned delight,
Yarn and packages soaring to new height.
With twitching nose and ASCII cheer,
I celebrate the changes far and near!
🐇✨

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 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 842689a and 0c90487.

⛔ Files ignored due to path filters (2)

• .yarn/releases/yarn-4.6.0.cjs is excluded by !**/.yarn/**
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (8)

• .yarnrc.yml (1 hunks)
• configs/eslint-config-custom/package.json (1 hunks)
• configs/vite-config-custom/package.json (1 hunks)
• examples/react-swc/package.json (1 hunks)
• package.json (2 hunks)
• packages/css/package.json (1 hunks)
• packages/debug-log/package.json (1 hunks)
• packages/transform-to-vanilla/package.json (1 hunks)

🔇 Additional comments (12)

.yarnrc.yml (1)

17-17: Yarn Path Version Bump

The yarnPath value has been updated to use yarn-4.6.0.cjs. This change aligns with the upgrade goal and should ensure consistency with the updated package manager configuration. Please confirm that all build and dependency management workflows work as expected with the new Yarn version.

configs/vite-config-custom/package.json (1)

12-14: Update Dev Dependency Versions

The versions for vite-plugin-dts, vite-plugin-externalize-deps, and vite-tsconfig-paths have been bumped to ^4.5.0, ^0.9.0, and ^5.1.4, respectively. These updates contribute to overall dependency freshness. Ensure that these new versions are compatible with your build configuration and that no breaking changes are introduced.

configs/eslint-config-custom/package.json (1)

20-27: Bump ESLint and Related Tooling Versions

The dependency versions for @eslint/js, @typescript-eslint/parser, eslint-config-prettier, eslint-plugin-prettier, globals, and typescript-eslint have been updated. This coordinated update should help maintain consistency across your linting tools. As these packages often have interdependencies, please verify that your ESLint configurations and tests operate correctly after these bumps.

examples/react-swc/package.json (2)

13-14: Major Upgrade for React and React-DOM

React and React-DOM have been upgraded to ^19.0.0. Given that this is a major version bump, please ensure that all components, integrations, and testing suites are compatible with React 19.

---

17-34: Comprehensive DevDependencies Update

The updates in the devDependencies section—including upgrades for ESLint plugins, TypeScript tooling, Vanilla Extract packages, and others—reflect a consistent effort to keep the ecosystem up to date. It is advisable to run a full test suite and review any potential deprecation warnings to ensure a smooth transition.

packages/transform-to-vanilla/package.json (2)

64-64: Update @vanilla-extract/css Version

The version for @vanilla-extract/css has been bumped to ^1.17.1, which brings in newer fixes or features. Please verify that this update integrates well with your CSS transformation pipeline.

---

71-71: Bump @fastify/deepmerge Version

The dependency @fastify/deepmerge has been updated from ^2.0.0 to ^2.0.2. Although this is a minor update, please ensure that the merge behavior is as expected and no regressions occur.

packages/debug-log/package.json (1)

73-73: Bump for Chalk Dependency
The chalk version is updated from ^5.3.0 to ^5.4.1, which should include non-breaking improvements and bug fixes. Please verify that this minor bump does not introduce any unexpected behavior in output styling.

packages/css/package.json (2)

75-75: Update @fastify/deepmerge Version
The dependency @fastify/deepmerge has been bumped from ^2.0.0 to ^2.0.2. This appears to be a patch update; ensure that any deep merge behavior remains consistent with previous usage.

---

79-79: Upgrade @vanilla-extract/css in DevDependencies
The dev dependency @vanilla-extract/css is updated from ^1.16.1 to ^1.17.1. Please confirm that the new version does not affect any custom CSS build or theming configurations.

package.json (2)

5-5: Upgrade Package Manager Version
The packageManager field is updated from "yarn@4.5.3" to "yarn@4.6.0". Ensure that the corresponding Yarn binary (e.g., the yarnPath in .yarnrc.yml) is updated accordingly to avoid inconsistencies.

---

43-61: DevDependencies Version Bumps
A series of dependencies in the devDependencies section have been updated:

• @changesets/cli bumped to ^2.27.12
• @types/node bumped to ^22.13.1
• Major update: @vanilla-extract/vite-plugin bumped to ^5.0.0 (please review its changelog for any breaking changes)
• @vitest/coverage-v8 bumped to ^3.0.5
• c8 bumped to ^10.1.3
• eslint bumped to ^9.19.0
• prettier bumped to ^3.4.2
• terser bumped to ^5.37.0
• turbo bumped to ^2.4.0
• typescript bumped to ^5.7.3
• vite bumped to ^6.0.11
• vite-node bumped to ^3.0.5
• vitest bumped to ^3.0.5

These updates look aligned with our dependency maintenance practices. In particular, the major version update for @vanilla-extract/vite-plugin deserves extra scrutiny for any potential breaking API changes. Testing and verifying compatibility with your project's build and test processes is recommended.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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 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.

[github-actions]

Triggered from #142 by @​black7375.

Checking if we can fast forward main (842689a) to bump (0c90487).

Target branch (main):

commit 842689aca2986f939ab0436c44976c01567a4544 (HEAD -> main, origin/main, origin/HEAD)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Dec 1 19:56:38 2024 +0900

    Chore(deps): Bump packages

Pull request (bump):

commit 0c904876b01aaaa22d48eaae9aa964630c0ff53c (pull_request/bump)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Feb 2 00:50:43 2025 +0900

    Chore(deps): Bump packages

It is possible to fast forward main (842689a) to bump (0c90487). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to bump.

[black7375]

/fast-forward

[github-actions]

Triggered from #142 (comment) by @​black7375.

Trying to fast forward main (842689a) to bump (0c90487).

Target branch (main):

commit 842689aca2986f939ab0436c44976c01567a4544 (HEAD -> main, origin/main, origin/HEAD)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Dec 1 19:56:38 2024 +0900

    Chore(deps): Bump packages

Pull request (bump):

commit 0c904876b01aaaa22d48eaae9aa964630c0ff53c (pull_request/bump)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Feb 2 00:50:43 2025 +0900

    Chore(deps): Bump packages

Fast forwarding main (842689a) to bump (0c90487).

$ git push origin 0c904876b01aaaa22d48eaae9aa964630c0ff53c:main
To https://github.com/mincho-js/mincho.git
   842689a..0c90487  0c904876b01aaaa22d48eaae9aa964630c0ff53c -> main