Skip to content
This repository has been archived by the owner on Dec 10, 2023. It is now read-only.

Update dependency vite to v5 #471

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update dependency vite to v5 #471

wants to merge 2 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 16, 2023

Mend Renovate logo banner

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) ^2.8.0 || ^3.0.0 || ^4.0.0 -> ^2.8.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 age adoption passing confidence

Release Notes

vitejs/vite (vite)

v5.0.0

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


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.

Copy link
Contributor Author

renovate bot commented Nov 16, 2023

⚠ 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: demo/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @mantine/core@6.0.4
npm ERR! Found: @mantine/hooks@6.0.8
npm ERR! node_modules/@mantine/hooks
npm ERR!   @mantine/hooks@"^4.0 || ^5.0.0 || ^6.0.0" from the root project
npm ERR!   peer @mantine/hooks@"6.0.8" from @mantine/prism@6.0.8
npm ERR!   node_modules/@mantine/prism
npm ERR!     @mantine/prism@"^4.0 || ^5.0.0 || ^6.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @mantine/hooks@"6.0.4" from @mantine/core@6.0.4
npm ERR! node_modules/@mantine/core
npm ERR!   @mantine/core@"^4.0 || ^5.0.0 || ^6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @mantine/hooks@6.0.4
npm ERR! node_modules/@mantine/hooks
npm ERR!   peer @mantine/hooks@"6.0.4" from @mantine/core@6.0.4
npm ERR!   node_modules/@mantine/core
npm ERR!     @mantine/core@"^4.0 || ^5.0.0 || ^6.0.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/268956/92c7f3/cache/others/npm/_logs/2023-11-16T14_28_12_416Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/268956/92c7f3/cache/others/npm/_logs/2023-11-16T14_28_12_416Z-debug-0.log

Copy link

codecov bot commented Nov 16, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (edd2705) 100.00% compared to head (e34334d) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #471   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           83        83           
  Branches        25        25           
=========================================
  Hits            83        83           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor Author

renovate bot commented Nov 16, 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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants