You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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 and vitejs/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 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 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.
In Vite 3, importing the default export of a .css file could introduce a double loading of CSS.
importcssStringfrom'./global.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.
importstufffrom'./global.css?inline'
Other features
Support for patch-package when pre bundling dependencies (#10286)
Cleaner build logs output (#10895) and switch to kB to align with browser dev tools (#10982)
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
dependenciesPull requests that update a dependency file
1 participant
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.
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
dependencies
This PR contains the following updates:
^3.2.5->^4.1.4Release Notes
vitejs/vite
v4.1.4Compare Source
v4.1.3Compare Source
<noscript>(#11764) (1dba285), closes #11764v4.1.2Compare Source
crossOriginattribute (#12023) (6a0d356), closes #12023ssrTransformparse error (#12060) (19f39f7), closes #12060import.meta.hot?.accept(#12053) (081c27f), closes #12053v4.1.1Compare Source
v4.1.0Compare 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:
targetsdefault.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.4Compare Source
v4.0.3Compare Source
v4.0.2Compare Source
toOutputFilePathWithoutRuntimefunction (#11367) (8820f75), closes #11367vite optimizeprebundle for dev (#11387) (b4ced0f), closes #11387v4.0.1Compare Source
u(#11319) (8c0bb7b), closes #11319useDefineForClassFieldsvalue 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.0Compare 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-vueand@vitejs/plugin-reacthave 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-vueandvitejs/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
safari14by default for wider ES2020 compatibility (https://github.com/vitejs/vite/issues/9063). This means that modern builds can now useBigIntand that the nullish coallessing operator isn't transpiled anymore. If you need to support older browsers, you can add@vitejs/plugin-legacyas usual.Importing CSS as a string
In Vite 3, importing the default export of a
.cssfile could introduce a double loading of CSS.This double loading could occur since a
.cssfile 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.cssdefault export has been deprecated. The?inlinequery suffix modifier needs to be used in this case, as that doesn't emit the imported.cssstyles.Other features
kBto align with browser dev tools (#10982)Features
expand(#11141) (825c793), closes #11141safari14by default for wider ES2020 compatibility (#9063) (3cc65d7), closes #9063transformIndexHtmlhook (#9669) (1db52bf), closes #9669Bug Fixes
\0to virtual files id (#11261) (02cdfa9), closes #11261NODE_ENVmore predictable (#10996) (8148af7), closes #10996addWatchFile()work (fix #7024) (#9723) (34db08b), closes #7024 #9723nullfromCSSModulesOptions.localsConvention(#10904) (a9978dd), closes #10904baseinresolveConfigand 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/vi
Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), 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.