This repository was archived by the owner on Apr 15, 2026. It is now read-only.
chore(deps): update dependency @vitejs/plugin-react to v4.7.0 - #125
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency @vitejs/plugin-react to v4.7.0#125renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
4 times, most recently
from
November 24, 2024 18:16
24f7226 to
cd0aaaa
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
3 times, most recently
from
January 30, 2025 17:26
1295bbd to
d4ca3fe
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
February 9, 2025 13:49
d4ca3fe to
3e47212
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
March 3, 2025 12:20
3e47212 to
03b62eb
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
3 times, most recently
from
March 17, 2025 17:49
1165b03 to
da1227b
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 1, 2025 12:25
da1227b to
c7b483f
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 15, 2025 12:33
c7b483f to
0a622bb
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 24, 2025 08:04
0a622bb to
3a45aa3
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
May 23, 2025 01:58
29cb512 to
e008cb4
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
May 28, 2025 13:59
e008cb4 to
6305156
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
June 6, 2025 01:40
6305156 to
4c70778
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
July 2, 2025 18:46
4c70778 to
2465c0b
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
July 18, 2025 07:33
2465c0b to
5b9ad4e
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
August 13, 2025 11:45
7c2dabb to
38f254c
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
August 19, 2025 16:42
38f254c to
057d3c4
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
August 31, 2025 12:44
057d3c4 to
ad9e4f3
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
September 25, 2025 15:56
ad9e4f3 to
588f82e
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
October 21, 2025 10:50
588f82e to
fb8a1ec
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
November 19, 2025 23:55
fb8a1ec to
171621d
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
December 3, 2025 19:26
171621d to
196f781
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
December 31, 2025 15:52
196f781 to
61ee990
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
January 8, 2026 20:03
61ee990 to
3ff0d65
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
January 23, 2026 17:10
5e8c3d5 to
7c36fd3
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
February 2, 2026 21:55
7c36fd3 to
040ac07
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
February 12, 2026 11:12
040ac07 to
0583a90
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
February 19, 2026 11:17
0583a90 to
34a0ce1
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
March 13, 2026 16:42
5205cc1 to
77079c4
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 1, 2026 18:59
77079c4 to
c8ff5e4
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 8, 2026 20:53
c8ff5e4 to
73ed54a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.2.1→4.7.0Release Notes
vitejs/vite-plugin-react (@vitejs/plugin-react)
v4.7.0Compare Source
Add HMR support for compound components (#518)
HMR now works for compound components like this:
Return
Plugin[]instead ofPluginOption[](#537)The return type has changed from
react(): PluginOption[]to more specialized typereact(): Plugin[]. This allows for type-safe manipulation of plugins, for example:v4.6.0Compare Source
Add raw Rolldown support
This plugin only worked with Vite. But now it can also be used with raw Rolldown. The main purpose for using this plugin with Rolldown is to use react compiler.
v4.5.2Compare Source
Suggest
@vitejs/plugin-react-oxcif rolldown-vite is detected #491Emit a log which recommends
@vitejs/plugin-react-oxcwhenrolldown-viteis detected to improve performance and use Oxc under the hood. The warning can be disabled by settingdisableOxcRecommendation: truein the plugin options.Use
optimizeDeps.rollupOptionsinstead ofoptimizeDeps.esbuildOptionsfor rolldown-vite #489This suppresses the warning about
optimizeDeps.esbuildOptionsbeing deprecated in rolldown-vite.Add Vite 7-beta to peerDependencies range #497
React plugins are compatible with Vite 7, this removes the warning when testing the beta.
v4.5.1Compare Source
Add explicit semicolon in preambleCode #485
This fixes an edge case when using HTML minifiers that strips line breaks aggressively.
v4.5.0Compare Source
Add
filterfor rolldown-vite #470Added
filterso that it is more performant when running this plugin with rolldown-powered version of Vite.Skip HMR for JSX files with hooks #480
This removes the HMR warning for hooks with JSX.
v4.4.1Compare Source
Fix type issue when using
moduleResolution: "node"in tsconfig #462v4.4.0Compare Source
Make compatible with rolldown-vite
This plugin is now compatible with rolldown-powered version of Vite.
Note that currently the
__sourceproperty value position might be incorrect. This will be fixed in the near future.v4.3.4Compare Source
Add Vite 6 to peerDependencies range
Vite 6 is highly backward compatible, not much to add!
Force Babel to output spec compliant import attributes #386
The default was an old spec (
with type: "json"). We now enforce spec compliant (with { type: "json" })v4.3.3Compare Source
React Compiler runtimeModule option removed
React Compiler was updated to accept a
targetoption andruntimeModulewas removed. vite-plugin-react will still detectruntimeModulefor backwards compatibility.When using a custom
runtimeModuleortarget !== '19', the plugin will not try to pre-optimizereact/compiler-runtimedependency.The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.
Here is the configuration to use the compiler with React 18 and correct source maps in development:
v4.3.2Compare Source
Ignore directive sourcemap error #369
v4.3.1Compare Source
Fix support for React Compiler with React 18
The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom
runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43When using a custom
runtimeModule, the plugin will not try to pre-optimizereact/compiler-runtimedependency.Reminder: Vite expect code outside of
node_modulesto be ESM, so you will need to update the gist withimport React from 'react'.v4.3.0Compare Source
Fix support for React compiler
Don't set
retainLines: truewhen the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:Support HMR for class components
This is a long overdue and should fix some issues people had with HMR when migrating from CRA.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.