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

⬆️ Update dependency vite to v4.3.1 #171

Merged
merged 1 commit into from
Apr 22, 2023
Merged

⬆️ Update dependency vite to v4.3.1 #171

merged 1 commit into from
Apr 22, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 18, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) 4.2.1 -> 4.3.1 age adoption passing confidence

Release Notes

vitejs/vite

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.2

Compare Source

Please refer to CHANGELOG.md for details.


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.


  • 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 requested a review from gabe565 as a code owner April 18, 2023 14:08
@renovate renovate bot added dependencies Pull requests that update a dependency file npm patch labels Apr 18, 2023
@renovate renovate bot changed the title ⬆️ Update dependency vite to v4.2.2 ⬆️ Update dependency vite to v4.3.0 Apr 20, 2023
@renovate renovate bot force-pushed the renovate/vite-4.x branch 2 times, most recently from 7c7ea64 to 1f04304 Compare April 20, 2023 23:11
@renovate renovate bot changed the title ⬆️ Update dependency vite to v4.3.0 ⬆️ Update dependency vite to v4.3.1 Apr 20, 2023
@gabe565 gabe565 merged commit 0c4ad99 into main Apr 22, 2023
@gabe565 gabe565 deleted the renovate/vite-4.x branch April 22, 2023 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file npm patch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant