Skip to content

Update dependency @vitejs/plugin-react to v6#622

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitejs-plugin-react-6.x
Open

Update dependency @vitejs/plugin-react to v6#622
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitejs-plugin-react-6.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 12, 2026

This PR contains the following updates:

Package Change Age Confidence
@vitejs/plugin-react (source) ^4.7.0^6.0.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.0.1

Compare Source

Expand @rolldown/plugin-babel peer dep range (#​1146)

Expanded @rolldown/plugin-babel peer dep range to include ^0.2.0.

v6.0.0

Compare Source

v5.2.0

Compare Source

v5.1.4

Compare Source

Fix canSkipBabel not accounting for babel.overrides (#​1098)

When configuring babel.overrides without top-level plugins or presets, Babel was incorrectly skipped. The canSkipBabel function now checks for overrides.length to ensure override configurations are processed.

v5.1.3

Compare Source

v5.1.2

Compare Source

v5.1.1

Compare Source

Update code to support newer rolldown-vite (#​976)

rolldown-vite will remove optimizeDeps.rollupOptions in favor of optimizeDeps.rolldownOptions soon. This plugin now uses optimizeDeps.rolldownOptions to support newer rolldown-vite. Please update rolldown-vite to the latest version if you are using an older version.

v5.1.0

Compare Source

Add @vitejs/plugin-react/preamble virtual module for SSR HMR (#​890)

SSR applications can now initialize HMR runtime by importing @vitejs/plugin-react/preamble at the top of their client entry instead of manually calling transformIndexHtml. This simplifies SSR setup for applications that don't use the transformIndexHtml API.

Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#​930)

Rolldown 1.0.0-beta.44+ removed the top-level jsx option in favor of transform.jsx. This plugin now uses the transform.jsx option to support Rolldown 1.0.0-beta.44+.

v5.0.4

Compare Source

Perf: use native refresh wrapper plugin in rolldown-vite (#​881)

v5.0.3

Compare Source

HMR did not work for components imported with queries with rolldown-vite (#​872)
Perf: simplify refresh wrapper generation (#​835)

v5.0.2

Compare Source

Skip transform hook completely in rolldown-vite in dev if possible (#​783)

v5.0.1

Compare Source

Set optimizeDeps.rollupOptions.transform.jsx instead of optimizeDeps.rollupOptions.jsx for rolldown-vite (#​735)

optimizeDeps.rollupOptions.jsx is going to be deprecated in favor of optimizeDeps.rollupOptions.transform.jsx.

Perf: skip babel-plugin-react-compiler if code has no "use memo" when { compilationMode: "annotation" } (#​734)
Respect tsconfig jsxImportSource (#​726)
Fix reactRefreshHost option on rolldown-vite (#​716)
Fix RefreshRuntime being injected twice for class components on rolldown-vite (#​708)
Skip babel-plugin-react-compiler on non client environment (689)

v5.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

@renovate renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from 4e411bb to a25405d Compare April 29, 2026 13:24
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 new potential issue.

View 1 additional finding in Devin Review.

Open in Devin Review

"@types/react": "^19.2.14",
"@types/react-dom": "^19.2.3",
"@vitejs/plugin-react": "^4.7.0",
"@vitejs/plugin-react": "^6.0.0",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Peer dependency mismatch: @vitejs/plugin-react@6 requires vite ^8.0.0 but project uses vite ^6.4.1

The @vitejs/plugin-react was bumped from ^4.7.0 to ^6.0.0, which resolves to v6.0.1. However, this version declares a peer dependency of vite: ^8.0.0 (visible in the pnpm-lock.yaml), while the project's package.json:30 still specifies vite: ^6.4.1 (resolved to 6.4.2). This peer dependency mismatch means the plugin is not tested or guaranteed to work with vite 6, and could cause build failures or subtle runtime issues. The vite dependency should also be bumped to ^8.0.0 to match, or @vitejs/plugin-react should be kept at a version compatible with vite 6.

Prompt for agents
The @vitejs/plugin-react was bumped from ^4.7.0 to ^6.0.0, but @vitejs/plugin-react@6.x declares a peer dependency of vite: ^8.0.0. The project still uses vite: ^6.4.1 on line 30 of package.json. Either:
1. Also bump vite to ^8.0.0 (and verify all other vite plugins like vite-plugin-singlefile are compatible with vite 8), OR
2. Keep @vitejs/plugin-react at a version compatible with vite 6 (e.g., ^4.7.0 or whichever major version supports vite 6).

The pnpm-lock.yaml confirms the mismatch: @vitejs/plugin-react@6.0.1 lists peerDependencies vite: ^8.0.0 but resolves with vite@6.4.2.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants