Skip to content

fix(deps): Update dependency vite to v8#780

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-8-node.js-dependencies
Open

fix(deps): Update dependency vite to v8#780
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-8-node.js-dependencies

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Mar 12, 2026

This PR contains the following updates:

Package Change Age Confidence
vite (source) ^7.0.6^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 - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC).

🚦 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 renovate bot added dependencies Pull requests that update a dependency file node npm labels Mar 12, 2026
@renovate
Copy link
Copy Markdown
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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: static-landing@2.8.1
npm warn Found: eslint@9.39.4
npm warn node_modules/eslint
npm warn   dev eslint@"^10.0.0" from the root project
npm warn   16 more (@eslint-community/eslint-utils, @eslint/compat, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9" from eslint-plugin-import@2.32.0
npm warn node_modules/eslint-plugin-import
npm warn   dev eslint-plugin-import@"^2.32.0" from the root project
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: static-landing@2.8.1
npm warn Found: eslint@9.39.4
npm warn node_modules/eslint
npm warn   dev eslint@"^10.0.0" from the root project
npm warn   16 more (@eslint-community/eslint-utils, @eslint/compat, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9" from eslint-plugin-jsx-a11y@6.10.2
npm warn node_modules/eslint-plugin-jsx-a11y
npm warn   dev eslint-plugin-jsx-a11y@"^6.10.2" from the root project
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: static-landing@2.8.1
npm warn Found: eslint@9.39.4
npm warn node_modules/eslint
npm warn   dev eslint@"^10.0.0" from the root project
npm warn   16 more (@eslint-community/eslint-utils, @eslint/compat, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7" from eslint-plugin-react@7.37.5
npm warn node_modules/eslint-plugin-react
npm warn   dev eslint-plugin-react@"^7.37.5" from the root project
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @tailwindcss/vite@4.2.1
npm error Found: vite@8.0.3
npm error node_modules/vite
npm error   vite@"^8.0.0" from the root project
npm error   peer vite@"^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0" from @vitejs/plugin-react@5.2.0
npm error   node_modules/@vitejs/plugin-react
npm error     @vitejs/plugin-react@"^5.1.4" from @astrojs/react@5.0.0
npm error     node_modules/@astrojs/react
npm error       @astrojs/react@"5.0.0" from the root project
npm error   1 more (vitefu)
npm error
npm error Could not resolve dependency:
npm error peer vite@"^5.2.0 || ^6 || ^7" from @tailwindcss/vite@4.2.1
npm error node_modules/@tailwindcss/vite
npm error   dev @tailwindcss/vite@"^4.1.11" from the root project
npm error
npm error Conflicting peer dependency: vite@7.3.1
npm error node_modules/vite
npm error   peer vite@"^5.2.0 || ^6 || ^7" from @tailwindcss/vite@4.2.1
npm error   node_modules/@tailwindcss/vite
npm error     dev @tailwindcss/vite@"^4.1.11" from the root project
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-04-01T19_37_05_576Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-01T19_37_05_576Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-8-node.js-dependencies branch from 3c959a2 to 4fda4b6 Compare March 12, 2026 22:00
@renovate renovate bot force-pushed the renovate/major-8-node.js-dependencies branch from 4fda4b6 to 2fd6477 Compare March 13, 2026 01:14
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 node npm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants