-
Notifications
You must be signed in to change notification settings - Fork 0
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 vite to v4 #37
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/vite-4.x
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 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 ↗︎
|
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
December 9, 2022 19:29
34e80bc
to
238011c
Compare
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
December 12, 2022 19:57
238011c
to
5bb296a
Compare
renovate
bot
changed the title
chore(deps): update dependency vite to v4
Update dependency vite to v4
Dec 17, 2022
renovate
bot
changed the title
Update dependency vite to v4
chore(deps): update dependency vite to v4
Dec 17, 2022
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
December 18, 2022 11:35
5bb296a
to
bfe16f1
Compare
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
December 21, 2022 14:06
bfe16f1
to
c98633f
Compare
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
January 3, 2023 12:03
c98633f
to
dc092f6
Compare
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
February 2, 2023 12:07
dc092f6
to
a2ffc36
Compare
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
February 2, 2023 14:57
a2ffc36
to
0434d4c
Compare
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
February 22, 2023 08:54
0434d4c
to
de6657f
Compare
renovate
bot
force-pushed
the
renovate/vite-4.x
branch
from
February 22, 2023 09:41
de6657f
to
8954e0b
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.2.5
->^4.1.4
Release Notes
vitejs/vite
v4.1.4
Compare Source
v4.1.3
Compare Source
<noscript>
(#11764) (1dba285), closes #11764v4.1.2
Compare Source
crossOrigin
attribute (#12023) (6a0d356), closes #12023ssrTransform
parse error (#12060) (19f39f7), closes #12060import.meta.hot?.accept
(#12053) (081c27f), closes #12053v4.1.1
Compare Source
v4.1.0
Compare Source
Vite 4.1 updates to the latest versions of Rollup and esbuild. Check out the new Rollup docs, that are now powered by VitePress making the navigation between Vite and Rollup docs easier for users.
Vite docs got a theme update migrating to the latest version of VitePress.
As part of Vite 4, the Vue and React plugins have been extracted out of the monorepo. Although their release cycle will no longer follow Vite releases moving forward, Vite 4.1 is released in parallel with new versions of @vitejs/plugin-react and @vitejs/plugin-react-swc. @vitejs/plugin-react 3.1.0 reworks the way HMR is handled fixing many edge cases and @vitejs/plugin-react-swc 3.1.0 adds support for SWC plugins.
There is also a new major for @vitejs/plugin-legacy, see changelog for v4.0.0. This version contains breaking changes:
targets
default.Features
Bug Fixes
Previous Changelogs
4.1.0-beta.2 (2023-02-01)
See 4.1.0-beta.2 changelog
4.1.0-beta.1 (2023-01-26)
See 4.1.0-beta.1 changelog
4.1.0-beta.0 (2023-01-09)
See 4.1.0-beta.0 changelog
v4.0.4
Compare Source
v4.0.3
Compare Source
v4.0.2
Compare Source
toOutputFilePathWithoutRuntime
function (#11367) (8820f75), closes #11367vite optimize
prebundle for dev (#11387) (b4ced0f), closes #11387v4.0.1
Compare Source
u
(#11319) (8c0bb7b), closes #11319useDefineForClassFields
value fromtsconfig.compilerOptions.target
(fixes #10296) (# (42976d8), closes #10296 #11301/__open-in-editor
(#11337) (8856c2e), closes #11337@typescript-eslint/ban-ts-comment
(#11326) (e58a4f0), closes #11326v4.0.0
Compare Source
Read the announcement blog post: Announcing Vite 4
Quick links:
Docs in other languages:
Main Changes
This major is smaller in scope compared to Vite 3, with the main objective of upgrading to Rollup 3. We've worked with the ecosystem to ensure a smooth upgrade path for this new major.
Rollup 3
Vite is now using Rollup 3, which allowed us to simplify Vite's internal asset handling and has many improvements. See the Rollup 3 release notes here.
Framework Plugins out of the Vite core monorepo
@vitejs/plugin-vue
and@vitejs/plugin-react
have been part of Vite core monorepo since the first versions of Vite. This helped us to get a close feedback loop when making changes as we were getting both Core and the plugins tested and released together. With vite-ecosystem-ci we can get this feedback with these plugins developed on independent repositories, so from Vite 4, they have been moved out of the Vite core monorepo. This is meaningful for Vite's framework-agnostic story, and will allow us to build independent teams to maintain each of the plugins. If you have bugs to report or features to request, please create issues on the new repositories moving forward:vitejs/vite-plugin-vue
andvitejs/vite-plugin-react
.New React plugin using SWC during development
SWC is now a mature replacement for Babel, especially in the context of React projects. SWC's React Fast Refresh implementation is a lot faster than Babel, and for some projects, it is now a better alternative. From Vite 4, two plugins are available for React projects with different tradeoffs. We believe that both approaches are worth supporting at this point, and we'll continue to explore improvements to both plugins in the future.
@vitejs/plugin-react
@vitejs/plugin-react is a plugin that uses esbuild and Babel, achieving fast HMR with a small package footprint and the flexibility of being able to use the babel transform pipeline.
@vitejs/plugin-react-swc (new)
@vitejs/plugin-react-swc is a new plugin that uses esbuild during build, but replaces Babel with SWC during development. For big projects that don't require non-standard React extensions, cold start and Hot Module Replacement (HMR) can be significantly faster.
Compatibility
The modern browser build now targets
safari14
by default for wider ES2020 compatibility (https://github.com/vitejs/vite/issues/9063). This means that modern builds can now useBigInt
and that the nullish coallessing operator isn't transpiled anymore. If you need to support older browsers, you can add@vitejs/plugin-legacy
as usual.Importing CSS as a string
In Vite 3, importing the default export of a
.css
file could introduce a double loading of CSS.This double loading could occur since a
.css
file will be emitted and it's likely that the CSS string will also be used by the application code — for example, injected by the framework runtime. From Vite 4, the.css
default export has been deprecated. The?inline
query suffix modifier needs to be used in this case, as that doesn't emit the imported.css
styles.Other features
kB
to align with browser dev tools (#10982)Features
expand
(#11141) (825c793), closes #11141safari14
by default for wider ES2020 compatibility (#9063) (3cc65d7), closes #9063transformIndexHtml
hook (#9669) (1db52bf), closes #9669Bug Fixes
\0
to virtual files id (#11261) (02cdfa9), closes #11261NODE_ENV
more predictable (#10996) (8148af7), closes #10996addWatchFile()
work (fix #7024) (#9723) (34db08b), closes #7024 #9723null
fromCSSModulesOptions.localsConvention
(#10904) (a9978dd), closes #10904base
inresolveConfig
and dev server (#10247) (16e4123), closes #10247Previous Changelogs
4.0.0-beta.7 (2022-12-08)
See 4.0.0-beta.7 changelog
4.0.0-beta.6 (2022-12-08)
See 4.0.0-beta.6 changelog
4.0.0-beta.5 (2022-12-08)
See 4.0.0-beta.5 changelog
4.0.0-beta.4 (2022-12-07)
See 4.0.0-beta.4 changelog
4.0.0-beta.3 (2022-12-07)
See 4.0.0-beta.3 changelog
4.0.0-beta.2 (2022-12-07)
See 4.0.0-beta.2 changelog
4.0.0-beta.1 (2022-12-06)
See 4.0.0-beta.1 changelog
4.0.0-beta.0 (2022-12-05)
See 4.0.0-beta.0 changelog
4.0.0-alpha.6 (2022-11-30)
See [4.0.0-alpha.6 changelog](https://togithub.com/vitejs/vite/blob/v4.0.0-alp
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 has been generated by Mend Renovate. View repository job log here.