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 - autoclosed #102

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 9, 2022

Mend Renovate logo banner

This PR contains the following updates:

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

Release Notes

vitejs/vite (vite)

v4.5.0

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.11

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.10

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.9

Compare Source

v4.4.8

Compare Source

v4.4.7

Compare Source

v4.4.6

Compare Source

v4.4.5

Compare Source

v4.4.4

Compare Source

v4.4.3

Compare Source

v4.4.2

Compare Source

v4.4.1

Compare Source

v4.4.0

Compare Source

Experimental support for Lightning CSS

Starting from Vite 4.4, there is experimental support for Lightning CSS. You can opt into it by adding css.transformer: 'lightningcss' to your config file and install the optional lightningcss dev dependency. If enabled, CSS files will be processed by Lightning CSS instead of PostCSS.

Lightning CSS can also be used as the CSS minifier with build.cssMinify: 'lightningcss'.

See beta docs at the Lighting CSS guide.

esbuild 0.18 update

esbuild 0.18 contains backwards-incompatible changes to esbuild's handling of tsconfig.json files. We think they shouldn't affect Vite users, you can review #​13525 for more information.

Templates for Solid and Qwik in create-vite

New starter templates have been added to create-vite for Solid and Qwik. Try them online at vite.new/solid-ts and vite.new/qwik-ts.

Korean Translation

Vite's docs are now translated to Korean, available at ko.vitejs.dev.

Features
Bug Fixes
Previous Changelogs
4.4.0-beta.4 (2023-07-03)

See 4.4.0-beta.4 changelog

4.4.0-beta.3 (2023-06-25)

See 4.4.0-beta.3 changelog

4.4.0-beta.2 (2023-06-22)

See 4.4.0-beta.2 changelog

4.4.0-beta.1 (2023-06-21)

See 4.4.0-beta.1 changelog

4.4.0-beta.0 (2023-06-20)

See 4.4.0-beta.0 changelog

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

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
Copy link
Contributor Author

renovate bot commented Dec 9, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vitejs/plugin-react@2.2.0
npm ERR! Found: vite@4.5.0
npm ERR! node_modules/vite
npm ERR!   dev vite@"4.5.0" from the root project
npm ERR!   vite@"^3.0.0 || ^4.0.0" from vite-node@0.33.0
npm ERR!   node_modules/vite-node
npm ERR!     vite-node@"0.33.0" from vitest@0.33.0
npm ERR!     node_modules/vitest
npm ERR!       dev vitest@"0.33.0" from the root project
npm ERR!   1 more (vitest)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^3.0.0" from @vitejs/plugin-react@2.2.0
npm ERR! node_modules/@vitejs/plugin-react
npm ERR!   dev @vitejs/plugin-react@"2.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: vite@3.2.7
npm ERR! node_modules/vite
npm ERR!   peer vite@"^3.0.0" from @vitejs/plugin-react@2.2.0
npm ERR!   node_modules/@vitejs/plugin-react
npm ERR!     dev @vitejs/plugin-react@"2.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/032e02/c22deb/cache/others/npm/_logs/2023-10-18T11_56_06_591Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/032e02/c22deb/cache/others/npm/_logs/2023-10-18T11_56_06_591Z-debug-0.log

@vercel
Copy link

vercel bot commented Dec 9, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
colorado-budget ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 18, 2023 11:56am

@renovate renovate bot force-pushed the renovate/vite-4.x branch from ca6b4de to 46b7b54 Compare December 12, 2022 21:00
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 46b7b54 to 17fc29d Compare December 18, 2022 13:00
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 17fc29d to c8a62c5 Compare December 21, 2022 16:00
@renovate renovate bot force-pushed the renovate/vite-4.x branch from c8a62c5 to 19c6edf Compare December 29, 2022 04:00
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 19c6edf to f55b760 Compare December 29, 2022 04:20
@renovate renovate bot force-pushed the renovate/vite-4.x branch from f55b760 to 6f64d05 Compare January 3, 2023 11:57
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 6f64d05 to cf877e0 Compare January 28, 2023 17:14
@renovate renovate bot force-pushed the renovate/vite-4.x branch from cf877e0 to 980ba0b Compare February 2, 2023 13:56
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 980ba0b to 4a34316 Compare February 2, 2023 17:59
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 4a34316 to 31b7c9e Compare February 8, 2023 03:32
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 31b7c9e to 0141f03 Compare February 8, 2023 03:36
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 0141f03 to 5f86ac7 Compare February 17, 2023 10:10
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 5f86ac7 to 9e87f55 Compare February 20, 2023 09:14
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 9e87f55 to b195bd2 Compare February 21, 2023 20:26
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 5eadd45 to 59909a9 Compare July 6, 2023 16:50
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 59909a9 to 147d2e8 Compare July 7, 2023 10:48
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 147d2e8 to 6e53f05 Compare July 11, 2023 14:59
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 6e53f05 to 8f892e2 Compare July 11, 2023 18:16
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 8f892e2 to 22c89a3 Compare July 14, 2023 07:17
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 22c89a3 to 5b06a44 Compare July 20, 2023 16:51
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 5b06a44 to 5c69a5f Compare July 21, 2023 10:47
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 5c69a5f to 684e263 Compare July 24, 2023 15:33
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 684e263 to f2f28fb Compare August 1, 2023 14:00
@renovate renovate bot force-pushed the renovate/vite-4.x branch from f2f28fb to 3c8ba5e Compare August 7, 2023 11:29
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 3c8ba5e to 79e6ab5 Compare October 3, 2023 18:23
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 79e6ab5 to 5bdd121 Compare October 5, 2023 09:27
@renovate renovate bot force-pushed the renovate/vite-4.x branch from 5bdd121 to 99e4718 Compare October 18, 2023 11:56
@renovate renovate bot changed the title Update dependency vite to v4 Update dependency vite to v4 - autoclosed Nov 16, 2023
@renovate renovate bot closed this Nov 16, 2023
@renovate renovate bot deleted the renovate/vite-4.x branch November 16, 2023 11:54
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.

0 participants