Skip to content

chore(deps-dev): bump vite from 6.2.0 to 6.3.5#813

Merged
tbouffard merged 1 commit intomainfrom
chore/deps_bump_vite
May 6, 2025
Merged

chore(deps-dev): bump vite from 6.2.0 to 6.3.5#813
tbouffard merged 1 commit intomainfrom
chore/deps_bump_vite

Conversation

@tbouffard
Copy link
Member

@tbouffard tbouffard commented May 6, 2025

In storybook, bump vite from 5.4.17 to 5.4.19 (storybook v7 only supports vite v5)

Summary by CodeRabbit

  • Chores
    • Updated the development dependency "vite" to newer versions across multiple packages to ensure up-to-date tooling. No changes to user-facing features or functionality.

In storybook, bump vite from 5.4.17 to 5.4.19 (storybook v7 only supports vite v5)
@tbouffard tbouffard added dependencies skip-changelog Do not include in Changelog and Release Notes javascript Pull requests that update Javascript code labels May 6, 2025
@coderabbitai
Copy link

coderabbitai bot commented May 6, 2025

Walkthrough

The pull request updates the vite development dependency versions in several package.json files across multiple packages. No other dependencies, scripts, or metadata are changed, and there are no alterations to exported or public entities.

Changes

File(s) Change Summary
packages/html/package.json Updated vite devDependency from ~5.4.17 to ~5.4.19.
packages/ts-example-selected-features/package.json
packages/ts-example/package.json
packages/ts-example-without-defaults/package.json
Updated vite devDependency from ~6.2.0 to ~6.3.5.

Possibly related PRs

  • maxGraph/maxGraph#697: Updates the vite package version in the same package.json files, but to a different version.
  • maxGraph/maxGraph#617: Updates vite versions in similar files and includes broader compatibility and dependency updates.
  • maxGraph/maxGraph#748: Updates vite in packages/html/package.json from an earlier version to ~5.4.17, overlapping with this PR's changes.

📜 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 7c7c899 and be57795.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (4)
  • packages/html/package.json (1 hunks)
  • packages/ts-example-selected-features/package.json (1 hunks)
  • packages/ts-example-without-defaults/package.json (1 hunks)
  • packages/ts-example/package.json (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
packages/html/package.json (1)
Learnt from: tbouffard
PR: maxGraph/maxGraph#617
File: packages/ts-example/package.json:12-12
Timestamp: 2025-01-05T15:35:57.645Z
Learning: We keep Vite 5 specifically in the package that uses Storybook (the "html" package), while the other packages can safely use a newer version of Vite without compatibility issues.
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: build
  • GitHub Check: build (ubuntu-22.04)
  • GitHub Check: build (windows-2022)
  • GitHub Check: build (macos-14)
🔇 Additional comments (4)
packages/html/package.json (1)

21-21: Maintain Vite v5 patch bump for Storybook compatibility.

Bumping Vite from ~5.4.17 to ~5.4.19 follows the project policy of keeping Vite v5 in the Storybook package (as noted in PR #617). This ensures continued compatibility with Storybook v7.

packages/ts-example-selected-features/package.json (1)

12-12: Update Vite devDependency to v6.3.5.

The bump from ~6.2.0 to ~6.3.5 brings this example in line with the latest Vite release used elsewhere. Please verify that the example still builds and runs correctly with this version.

packages/ts-example/package.json (1)

12-12: Align Vite version to v6.3.5 for custom-shapes example.

Updating to ~6.3.5 keeps this package consistent with the other TypeScript examples. Confirm the build (npm run build/vite) and dev flow remain unaffected.

packages/ts-example-without-defaults/package.json (1)

12-12: Bump Vite to v6.3.5 for defaults-free example.

The change to ~6.3.5 matches the version used in related example packages. Ensure there are no regressions in startup or build behavior after this upgrade.


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

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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 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.

@sonarqubecloud
Copy link

sonarqubecloud bot commented May 6, 2025

@tbouffard tbouffard merged commit e17a50d into main May 6, 2025
7 checks passed
@tbouffard tbouffard deleted the chore/deps_bump_vite branch May 6, 2025 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies javascript Pull requests that update Javascript code skip-changelog Do not include in Changelog and Release Notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant