Skip to content

chore(deps): update dependency vite to v8#38

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/vite-8.x
Open

chore(deps): update dependency vite to v8#38
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/vite-8.x

Conversation

@renovate

@renovate renovate Bot commented Mar 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
vite (source) ^7.2.6^8.0.0 age confidence

Release Notes

vitejs/vite (vite)

v8.0.8

Compare Source

Features
Bug Fixes

v8.0.7

Compare Source

Bug Fixes
  • use sync dns.getDefaultResultOrder instead of dns.promises (#​22185) (5c05b04)

v8.0.6

Compare Source

Features
Bug Fixes
Performance Improvements
  • early return in getLocalhostAddressIfDiffersFromDNS when DNS order is verbatim (#​22151) (56ec256)
Miscellaneous Chores

v8.0.5

Compare Source

Bug Fixes

v8.0.4

Compare Source

Features
Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring

v8.0.3

Compare Source

Features
Bug Fixes
  • html: cache unfiltered CSS list to prevent missing styles across entries (#​22017) (5464190)
  • module-runner: handle non-ascii characters in base64 sourcemaps (#​21985) (77c95bf)
  • module-runner: skip re-import if the runner is closed (#​22020) (ee2c2cd)
  • optimizer: scan is not resolving sub path import if used in a glob import (#​22018) (ddfe20d)
  • ssr: ssrTransform incorrectly rewrites meta identifier inside import.meta when a binding named meta exists (#​22019) (cff5f0c)
Miscellaneous Chores
Tests

v8.0.2

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.1

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.0

Compare Source

Features
Bug Fixes

v7.3.2

Compare Source

Please refer to CHANGELOG.md for details.


Configuration

📅 Schedule: (UTC)

  • 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 was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Mar 27, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sveltejs/vite-plugin-svelte@6.2.4
npm error Found: vite@8.0.8
npm error node_modules/vite
npm error   dev vite@"^8.0.0" from the root project
npm error   peer vite@"^5.0.3 || ^6.0.0 || ^7.0.0-beta.0 || ^8.0.0" from @sveltejs/kit@2.55.0
npm error   node_modules/@sveltejs/kit
npm error     dev @sveltejs/kit@"^2.49.1" from the root project
npm error     peer @sveltejs/kit@"^1.0.0 || ^2.0.0" from @auth/sveltekit@1.11.1
npm error     node_modules/@auth/sveltekit
npm error       @auth/sveltekit@"^1.11.1" from the root project
npm error     1 more (@sveltejs/adapter-node)
npm error   5 more (@tailwindcss/vite, @testing-library/svelte, ...)
npm error
npm error Could not resolve dependency:
npm error peer vite@"^6.3.0 || ^7.0.0" from @sveltejs/vite-plugin-svelte@6.2.4
npm error node_modules/@sveltejs/vite-plugin-svelte
npm error   dev @sveltejs/vite-plugin-svelte@"^6.2.1" from the root project
npm error   peer @sveltejs/vite-plugin-svelte@"^3.0.0 || ^4.0.0-next.1 || ^5.0.0 || ^6.0.0-next.0 || ^7.0.0" from @sveltejs/kit@2.55.0
npm error   node_modules/@sveltejs/kit
npm error     dev @sveltejs/kit@"^2.49.1" from the root project
npm error     2 more (@auth/sveltekit, @sveltejs/adapter-node)
npm error   1 more (@sveltejs/vite-plugin-svelte-inspector)
npm error
npm error Conflicting peer dependency: vite@7.3.2
npm error node_modules/vite
npm error   peer vite@"^6.3.0 || ^7.0.0" from @sveltejs/vite-plugin-svelte@6.2.4
npm error   node_modules/@sveltejs/vite-plugin-svelte
npm error     dev @sveltejs/vite-plugin-svelte@"^6.2.1" from the root project
npm error     peer @sveltejs/vite-plugin-svelte@"^3.0.0 || ^4.0.0-next.1 || ^5.0.0 || ^6.0.0-next.0 || ^7.0.0" from @sveltejs/kit@2.55.0
npm error     node_modules/@sveltejs/kit
npm error       dev @sveltejs/kit@"^2.49.1" from the root project
npm error       2 more (@auth/sveltekit, @sveltejs/adapter-node)
npm error     1 more (@sveltejs/vite-plugin-svelte-inspector)
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-09T10_08_07_615Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-09T10_08_07_615Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/vite-8.x branch 3 times, most recently from 4df356b to 6e2d5f3 Compare April 1, 2026 18:53
@renovate renovate Bot force-pushed the renovate/vite-8.x branch from 6e2d5f3 to 79aba6e Compare April 8, 2026 19:36
@renovate

renovate Bot commented Apr 19, 2026

Copy link
Copy Markdown
Contributor Author

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