-
Notifications
You must be signed in to change notification settings - Fork 12
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 #1057
Closed
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
renovate
bot
added
📝 dependencies 📦
Pull requests that update a dependency file
deps: javascript
deps: vite
labels
May 30, 2023
⚠ Artifact update problemRenovate 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:
The artifact failure details are included below: File name: frontend/package-lock.json
|
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
2 times, most recently
from
June 26, 2023 10:41
ebaec92
to
0234b3f
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
5 times, most recently
from
July 10, 2023 07:33
ebb6f6a
to
9775bc2
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
from
July 12, 2023 07:01
9775bc2
to
ecc6f6d
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
from
July 21, 2023 01:38
ecc6f6d
to
4a35f5d
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
2 times, most recently
from
July 31, 2023 17:26
a64dee2
to
29a1af6
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
from
August 15, 2023 14:12
29a1af6
to
5c4d098
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
4 times, most recently
from
September 26, 2023 02:33
b63954e
to
82ac55d
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
5 times, most recently
from
September 30, 2023 16:23
8b292a6
to
30de7ba
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
2 times, most recently
from
October 9, 2023 07:42
7c173ec
to
9d72b45
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
from
October 23, 2023 08:08
9d72b45
to
ede6e3f
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
from
November 2, 2023 10:57
ede6e3f
to
d19a94b
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
from
November 16, 2023 16:31
d19a94b
to
6662eba
Compare
renovate
bot
force-pushed
the
renovate/major-vite-and-plugins
branch
from
December 4, 2023 18:52
6662eba
to
bc01061
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.0.0
->4.2.1
Release Notes
vitejs/vite-plugin-react (@vitejs/plugin-react)
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:
v3.1.0
Compare Source
v3.0.1
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.