Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Apr 7, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

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

Release Notes

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

v6.1.2

Compare Source

Fix HMR for compound components (#​1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#​1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #​1478) (#​1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

v6.1.1

Compare Source

Add compiler.logDiagnostics option

Recoverable React Compiler diagnostics are no longer logged by default. Set compiler.logDiagnostics to true to log them through Vite. Fatal diagnostics are always logged and fail the transform.

Respect environment sourcemap option for React Compiler transform when builder.sharedPlugins is enabled (#​1439)

The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental builder.sharedPlugins was enabled.

v6.1.0

Compare Source

Add experimental native React Compiler support (#​1419)

Add experimental native React Compiler support.

You can use it by installing oxc-transform-react and enabling it via the compiler option:

npm install -D oxc-transform-react
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

export default defineConfig({
  plugins: [
     react({ compiler: true })
  ]
})

v6.0.5

Compare Source

Fixed the react compiler preset filter to be linear (#​1353)

The improved filter in v6.0.3 was non-linear and caused a performance regression (#​1349). The filter was changed to be linear to avoid that.

v6.0.4

Compare Source

Fixed $RefreshSig$ is not defined error when running vite dev with NODE_ENV=production

When running vite dev with NODE_ENV=production, the app errored with $RefreshSig$ is not defined.
This error is now fixed.

v6.0.3

Compare Source

Improve the react compiler preset filter to reduce false-positives (#​1138)

Improved the filter in the react compiler babel preset to reduce the false-positives so that less modules are processed by the react compiler.

v6.0.2

Compare Source

Allow all options in reactCompilerPreset (#​1189)

This is a type only change. Only compilationMode and target options were available for reactCompilerPreset.

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.


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • Monday through Friday (* * * * 1-5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

@renovate

renovate Bot commented Apr 7, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @convex-dev/launchdarkly@0.4.0
npm error Found: vite@7.3.7
npm error node_modules/vite
npm error   dev vite@"^7.1.12" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^8.0.0" from @vitejs/plugin-react@6.1.2
npm error node_modules/@vitejs/plugin-react
npm error   dev @vitejs/plugin-react@"^6.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-15T04_36_39_055Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-15T04_36_39_055Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from efa9ed0 to a7c53d2 Compare April 7, 2026 05:57
@renovate renovate Bot changed the title chore(deps): update dependency @vitejs/plugin-react to v6 Update dependency @vitejs/plugin-react to v6 Apr 8, 2026
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from a7c53d2 to 8a565f4 Compare April 15, 2026 05:26
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from 8a565f4 to 4e90687 Compare April 27, 2026 23:47
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from 4e90687 to 8d479b1 Compare May 22, 2026 21:49
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from 8d479b1 to 9c025ed Compare June 19, 2026 23:41
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from 9c025ed to b477e2b Compare July 2, 2026 01:03
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from b477e2b to 2ac5a0d Compare July 13, 2026 18:33
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from 2ac5a0d to 6098a0c Compare October 9, 2026 11:16
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch 2 times, most recently from 8739c44 to 0fc02ad Compare October 14, 2026 23:48
@renovate
renovate Bot force-pushed the renovate/vitejs-plugin-react-6.x branch from 0fc02ad to 50ce67d Compare October 15, 2026 04:36
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