-
Notifications
You must be signed in to change notification settings - Fork 17
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
chore(deps): update dependency @vitejs/plugin-react to v4 #599
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/vitejs-plugin-react-4.x
base: master
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 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
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
4 times, most recently
from
April 26, 2023 19:25
0b8677b
to
7570816
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
3 times, most recently
from
May 5, 2023 10:35
3b57435
to
aaa100c
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
2 times, most recently
from
May 15, 2023 15:07
281d3ff
to
52c3190
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
3 times, most recently
from
May 18, 2023 12:55
b6a3b4d
to
6bf9a9d
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
3 times, most recently
from
May 29, 2023 17:34
4e1c957
to
09fbc86
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
June 5, 2023 19:27
09fbc86
to
ea00153
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
June 14, 2023 18:31
ea00153
to
94a4d19
Compare
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@vitejs/plugin-react@3.1.0 |
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
3 times, most recently
from
June 26, 2023 18:26
700c773
to
3b36783
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
5 times, most recently
from
July 10, 2023 08:29
86cc999
to
d62501f
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
3 times, most recently
from
July 14, 2023 11:06
94fdafd
to
e52cce9
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
3 times, most recently
from
July 24, 2023 16:20
df3aee4
to
0d98ed4
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
3 times, most recently
from
August 7, 2023 09:25
17914bf
to
20ced04
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
August 13, 2023 19:25
20ced04
to
2427008
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
2 times, most recently
from
September 24, 2023 19:09
f3786c5
to
00687ff
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
2 times, most recently
from
October 5, 2023 09:05
4ba0e25
to
a5cd4c4
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
2 times, most recently
from
October 20, 2023 23:23
db6ec59
to
caa65ed
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
November 2, 2023 11:28
caa65ed
to
4d264fe
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
November 16, 2023 14:36
4d264fe
to
139c7af
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
December 4, 2023 19:57
139c7af
to
646072f
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
May 4, 2024 09:56
646072f
to
eaa193c
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
May 22, 2024 22:03
eaa193c
to
2997db9
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
June 10, 2024 00:49
2997db9
to
0603179
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
September 29, 2024 22:19
0603179
to
56624df
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
October 19, 2024 18:07
56624df
to
6f94295
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
October 29, 2024 12:56
6f94295
to
1f9e4cd
Compare
renovate
bot
force-pushed
the
renovate/vitejs-plugin-react-4.x
branch
from
November 26, 2024 15:03
1f9e4cd
to
eee184a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
3.1.0
->4.3.4
Release Notes
vitejs/vite-plugin-react (@vitejs/plugin-react)
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'
.v4.3.0
Compare Source
Fix support for React compiler
Don't set
retainLines: true
when 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.
v4.2.1
Compare Source
Remove generic parameter on
Plugin
to avoid type error with Rollup 4/Vite 5 andskipLibCheck: false
.I expect very few people to currently use this feature, but if you are extending the React plugin via
api
object, you can get back the typing of the hook by importingViteReactPluginApi
:v4.2.0
Compare Source
Update peer dependency range to target Vite 5
There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.
Align jsx runtime for optimized dependencies
This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have
React
in the scope.Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.
v4.1.1
Compare Source
v4.1.0
Compare Source
@types/babel__cores
to dependencies (fix #211)@babel/core
#212index.d.cts
file so you don't get types errors when settingmoduleResolution
tonode16
ornodenext
in your tsconfig (we recommend usingbundler
which is more close to how Vite works)v4.0.4
Compare Source
v4.0.3
Compare Source
v4.0.2
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
This major version include a revamp of options:
include
/exclude
now allow to completely override the files processed by the plugin (#122). This is more in line with other Rollup/Vite plugins and simplify the setup of enabling Fast Refresh for.mdx
files. This can be done like this:These changes also allow to apply Babel plugins on files outside Vite root (expect in node_modules), which improve support for monorepo (fix #16).
With these changes, only the file extensions is used for filtering processed files and the query param fallback is removed.
fastRefresh
is removed (#122). This should be correctly activated by plugin without configuration.jsxPure
is removed. This is a niche use case that was just passing down the boolean to esbuild.jsxSideEffects. (#129)The support for React auto import whe using classic runtime is removed. This was prone to errors and added complexity for no good reason given the very wide support of automatic runtime nowadays. This migration path should be as simple as removing the runtime option from the config.
This release goes in hand with the upcoming Vite 4.3 release focusing on performances:
Other notable changes:
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 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.