-
Notifications
You must be signed in to change notification settings - Fork 1
Update dependency @vitejs/plugin-react to v4.5.1 #285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/vitejs-plugin-react-4.x-lockfile
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
a41cca4
to
5b9ed3c
Compare
adce17c
to
23fe0f4
Compare
905fc01
to
f344082
Compare
f344082
to
cda719a
Compare
cda719a
to
5e34427
Compare
5e34427
to
f328ceb
Compare
f328ceb
to
b70a2d4
Compare
b70a2d4
to
c109f17
Compare
c109f17
to
69e95b2
Compare
69e95b2
to
a59b7d6
Compare
a59b7d6
to
87a8513
Compare
b71aaaf
to
3e9a161
Compare
3e9a161
to
36c0976
Compare
36c0976
to
91c152a
Compare
91c152a
to
cc49ec5
Compare
cc49ec5
to
283d036
Compare
283d036
to
3eeb6e4
Compare
3eeb6e4
to
285309d
Compare
285309d
to
a048c49
Compare
a048c49
to
d352432
Compare
d352432
to
5aee2e9
Compare
5aee2e9
to
f981555
Compare
f981555
to
1ea5332
Compare
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.3.0
->4.5.1
Release Notes
vitejs/vite-plugin-react (@vitejs/plugin-react)
v4.5.1
Compare Source
Add explicit semicolon in preambleCode #485
This fixes an edge case when using HTML minifiers that strips line breaks aggressively.
v4.5.0
Compare Source
Add
filter
for rolldown-vite #470Added
filter
so 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.1
Compare Source
Fix type issue when using
moduleResolution: "node"
in tsconfig #462v4.4.0
Compare Source
Make compatible with rolldown-vite
This plugin is now compatible with rolldown-powered version of Vite.
Note that currently the
__source
property value position might be incorrect. This will be fixed in the near future.v4.3.4
Compare 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.3
Compare Source
React Compiler runtimeModule option removed
React Compiler was updated to accept a
target
option andruntimeModule
was removed. vite-plugin-react will still detectruntimeModule
for backwards compatibility.When using a custom
runtimeModule
ortarget !== '19'
, the plugin will not try to pre-optimizereact/compiler-runtime
dependency.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.2
Compare Source
Ignore directive sourcemap error #369
v4.3.1
Compare 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-runtime
dependency.Reminder: Vite expect code outside of
node_modules
to be ESM, so you will need to update the gist withimport React from 'react'
.Configuration
📅 Schedule: 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 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.