This repository has been archived by the owner on Apr 16, 2023. It is now read-only.
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.2.1
Release Notes
vitejs/vite
v4.2.1
Compare Source
virtual:
to virtual module source map ignore (#12444) (c4aa28f), closes #12444v4.2.0
Compare Source
Vite 4.2 is out!
Support env variables replacement in HTML files
Vite now supports replacing env variables in HTML files. Any properties in
import.meta.env
can be used in HTML files with a special%ENV_NAME%
syntax:Sourcemaps improvements
The Chrome Dev Tools team has been working to improve the DX of Vite and Vite-powered frameworks in the dev tools. Vite 4.2 brings an improved experience and tools for framework authors to hide 3rd party code and build artifacts from the user from console log traces using
server.sourcemapIgnoreList
andbuild.rollupOptions.output.sourcemapIgnoreList
.ESM subpath imports
Vite 4.2 now supports subpath imports, thanks to @lukeed05's resolve.exports library.
TypeScript 5 support
Vite 4.2 also supports TypeScript 5's
tsconfig
extends
array format, thanks to tsconfck.esbuild 0.17
esbuild v0.17.0 improved the design of its incremental, watch, and serve APIs. Check out #11908 for the rationale of why we didn't consider the backward-incompatible changes breaking for our use cases. The updated esbuild design now allows Vite to properly cancel in-fly builds and improve server restarts.
Use Rollup types from the vite package
Expose Rollup types as a namespace. This is helpful to avoid type conflicts because of different versions of Rollup types in environments like vite-ecosystem-ci (#12316).
Português Docs Translation
The Vite documentation is now translated to Português at pt.vitejs.dev thanks to Nazaré Da Piedade .
Features
build.cssMinify
(#12207) (90431f2), closes #12207sourcemapIgnoreList
configuration option (#12174) (f875580), closes #12174build.target
if terser is 5.16.0+ (#12197) (9885f6f), closes #12197this.load
in plugin container context (#11469) (abfa804), closes #11469Bug Fixes
server.sourcemapIgnoreList
(#12251) (209c3bd), closes #12251resolve.exports
to2.0.1
to fix*
resolution issue (#12314) (523d6f7), closes #12314sources
for transformed source maps (#12079) (bcbc582), closes #12079Previous Changelogs
4.2.0-beta.2 (2023-03-13)
See 4.2.0-beta.2 changelog
4.2.0-beta.1 (2023-03-07)
See 4.2.0-beta.1 changelog
4.2.0-beta.0 (2023-02-27)
See 4.2.0-beta.0 changelog
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 #9669Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (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.