Skip to content

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

Closed
renovate[bot] wants to merge 2 commits intomainfrom
renovate/vite-8.x
Closed

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 12, 2026

This PR contains the following updates:

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

Release Notes

vitejs/vite (vite)

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 12, 2026

⚠️ 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: frontend/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.3
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.9.0" from the root project
npm error     peer @sveltejs/kit@"^2.0.0" from @sveltejs/adapter-static@3.0.10
npm error     node_modules/@sveltejs/adapter-static
npm error       dev @sveltejs/adapter-static@"^3.0.6" from the root project
npm error     1 more (runed)
npm error   1 more (@tailwindcss/vite)
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.0.0" 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.9.0" from the root project
npm error     2 more (@sveltejs/adapter-static, runed)
npm error   1 more (@sveltejs/vite-plugin-svelte-inspector)
npm error
npm error Conflicting peer dependency: vite@7.3.1
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.0.0" 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.9.0" from the root project
npm error       2 more (@sveltejs/adapter-static, runed)
npm error     1 more (@sveltejs/vite-plugin-svelte-inspector)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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-03-28T05_51_19_048Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-28T05_51_19_048Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vite-8.x branch 10 times, most recently from 65660cb to c9d5320 Compare March 18, 2026 21:50
@renovate renovate bot force-pushed the renovate/vite-8.x branch 10 times, most recently from 161bc96 to 7c4608f Compare March 28, 2026 05:50
@renovate renovate bot force-pushed the renovate/vite-8.x branch from 7c4608f to 24e5ba8 Compare March 28, 2026 05:51
@rajsinghtech
Copy link
Copy Markdown
Owner

Closing: @sveltejs/vite-plugin-svelte v6 doesn't support vite 8 yet. Renovate will reopen when upstream is compatible.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 28, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 8.x releases. But if you manually upgrade to 8.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/vite-8.x branch March 28, 2026 05: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.

1 participant