Update dependency @vitejs/plugin-react to v4.7.0 - #13
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
July 16, 2024 09:39
b53627f to
126c43c
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
September 30, 2024 02:20
126c43c to
dfae43a
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
October 20, 2024 02:52
dfae43a to
3623b53
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
November 26, 2024 20:23
3623b53 to
fc97882
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
January 31, 2025 16:03
ace2632 to
ec4cec7
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
February 11, 2025 06:20
ec4cec7 to
e3c700d
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
March 4, 2025 04:09
e3c700d to
8e2afbe
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
3 times, most recently
from
March 19, 2025 08:09
a1cba20 to
21e174c
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 4, 2025 00:18
21e174c to
c69fe66
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 12, 2025 07:33
c69fe66 to
58f4759
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 17, 2025 00:07
58f4759 to
8d8c44a
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
April 26, 2025 07:51
6228f64 to
57050d9
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
May 24, 2025 08:12
57050d9 to
70a3af1
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
May 31, 2025 11:52
70a3af1 to
07dcb93
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
June 6, 2025 17:01
500a1ef to
d825fa5
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
June 14, 2025 16:02
d825fa5 to
4b83071
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
August 15, 2025 20:13
c6d0658 to
9d502de
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
August 23, 2025 11:12
9d502de to
2f6c32e
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
September 1, 2025 01:57
2f6c32e to
1c46f61
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
September 26, 2025 19:45
1c46f61 to
a255d6e
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
October 23, 2025 06:57
a255d6e to
84b79a2
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
November 19, 2025 08:05
1459cb4 to
d0ba556
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
December 4, 2025 23:40
d0ba556 to
e881259
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
January 1, 2026 19:51
e881259 to
918d95d
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
January 9, 2026 04:05
918d95d to
97d0030
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
January 24, 2026 11:38
1ec0e78 to
58fdd15
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
February 3, 2026 12:13
58fdd15 to
0b2d580
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
February 18, 2026 04:05
f8f0025 to
7db3979
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
March 14, 2026 05:15
600406f to
5bcd51e
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 15, 2026 18:09
5bcd51e to
5e54c13
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
April 30, 2026 03:42
5e54c13 to
260ab49
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
May 13, 2026 03:53
260ab49 to
490fb8b
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
May 22, 2026 00:09
490fb8b to
7e6d502
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
June 5, 2026 03:30
a5c7570 to
6218375
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
June 12, 2026 15:55
6218375 to
762fd2f
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
2 times, most recently
from
July 18, 2026 11:42
c6a1c07 to
4b15f38
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
July 25, 2026 03:59
4b15f38 to
eb27434
Compare
renovate
Bot
force-pushed
the
renovate/vitejs-plugin-react-4.x-lockfile
branch
from
August 1, 2026 12:08
eb27434 to
7bca1e4
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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 becomes conflicted, 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.