Skip to content
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 ^4.3.9 #419

Open
wants to merge 12 commits into
base: v2
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 21, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) ^4.0.0 -> ^4.3.9 age adoption passing confidence

Release Notes

vitejs/vite

v4.3.9

Compare Source

v4.3.8

Compare Source

v4.3.7

Compare Source

v4.3.6

Compare Source

v4.3.5

Compare Source

v4.3.4

Compare Source

v4.3.3

Compare Source

v4.3.2

Compare Source

v4.3.1

Compare Source

v4.3.0

Compare Source

Vite 4.3 is out! Read the announcement blog post here

Vite 4.3, It's Fast

In this minor, we focused on improving the dev server performance. The resolve logic got streamlined, improving hot paths and implementing smarter caching for finding package.json, TS config files, and resolved URL in general.

You can read a detailed walkthrough of the performance work done in this blog post by one of Vite Contributors: How we made Vite 4.3 faaaaster 🚀.

This sprint resulted in speed improvements across the board compared to Vite 4.2.

These are the performance improvements as measured by sapphi-red/performance-compare, which tests an app with 1000 React Components cold and warm dev server startup time as well as HMR times for a root and a leaf component:

Vite (babel) Vite 4.2 Vite 4.3 Improvement
dev cold start 17249.0ms 5132.4ms -70.2%
dev warm start 6027.8ms 4536.1ms -24.7%
Root HMR 46.8ms 26.7ms -42.9%
Leaf HMR 27.0ms 12.9ms -52.2%
Vite (swc) Vite 4.2 Vite 4.3 Improvement
dev cold start 13552.5ms 3201.0ms -76.4%
dev warm start 4625.5ms 2834.4ms -38.7%
Root HMR 30.5ms 24.0ms -21.3%
Leaf HMR 16.9ms 10.0ms -40.8%

You can read more information about the benchmark here

Features
Performance
Bug Fixes
Clean up
Previous Changelogs
4.3.0-beta.8 (2023-04-19)

See 4.3.0-beta.8 changelog

4.3.0-beta.7 (2023-04-17)

See 4.3.0-beta.7 changelog

4.3.0-beta.6 (2023-04-14)

See 4.3.0-beta.6 changelog

4.3.0-beta.5 (2023-04-11)

See 4.3.0-beta.5 changelog

4.3.0-beta.4 (2023-04-09)

See 4.3.0-beta.4 changelog

4.3.0-beta.3 (2023-04-07)

See 4.3.0-beta.3 changelog

4.3.0-beta.2 (2023-04-05)

See 4.3.0-beta.2 changelog

4.3.0-beta.1 (2023-03-29)

See 4.3.0-beta.1 changelog

4.3.0-beta.0 (2023-03-23)

See 4.3.0-beta.0 changelog

v4.2.3

Compare Source

Please refer to CHANGELOG.md for details.

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.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:

<h1>Vite is running in %MODE%</h1>
<p>Using data from %VITE_API_URL%</p>
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 and build.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).

import type { Rollup } from 'vite'
Português Docs Translation

The Vite documentation is now translated to Português at pt.vitejs.dev thanks to Nazaré Da Piedade .

Features

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 06a9816 to 0942e99 Compare November 27, 2022 18:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 9a5456a to 59d3c22 Compare December 8, 2022 01:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 2033316 to f68829a Compare December 15, 2022 05:44
@renovate renovate bot changed the title chore(deps): update all non-major dependencies Update all non-major dependencies Dec 17, 2022
@renovate renovate bot changed the title Update all non-major dependencies chore(deps): update all non-major dependencies Dec 17, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 4a97e4a to 80b7be3 Compare December 21, 2022 16:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 4dd5448 to 67c65b3 Compare January 7, 2023 13:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from d6b4588 to 542ca2d Compare January 14, 2023 05:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 98aa778 to da329cd Compare January 25, 2023 11:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e558a04 to bfde9e3 Compare March 10, 2023 13:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 871f528 to 6ecdd43 Compare March 22, 2023 23:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6ecdd43 to 18371ee Compare March 24, 2023 10:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 7f0cdf4 to 3e02f0a Compare April 7, 2023 14:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3e02f0a to c091885 Compare April 11, 2023 22:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c091885 to ef12642 Compare May 26, 2023 11:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ef12642 to 92ba17b Compare May 26, 2023 15:14
@renovate renovate bot changed the title chore(deps): update all non-major dependencies chore(deps): update dependency vite to ^4.3.9 May 26, 2023
@codecov
Copy link

codecov bot commented May 26, 2023

Codecov Report

Merging #419 (92ba17b) into v2 (e103aed) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##                v2      #419    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files            2         2            
  Lines           58       169   +111     
  Branches        20        33    +13     
==========================================
+ Hits            58       169   +111     
Impacted Files Coverage Δ
src/usePromise.ts 100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

@renovate
Copy link
Contributor Author

renovate bot commented May 26, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant