Skip to content

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

Merged
brianhelba merged 7 commits intomasterfrom
renovate/vite-8.x
Mar 20, 2026
Merged

chore(deps): update dependency vite to v8#340
brianhelba merged 7 commits intomasterfrom
renovate/vite-8.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 12, 2026

This PR contains the following updates:

Package Change Age Confidence
vite (source) 7.3.18.0.1 age confidence

Release Notes

vitejs/vite (vite)

v8.0.1

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.0

Compare Source

Features
Bug Fixes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Mar 12, 2026

Deploying geodatalytics with  Cloudflare Pages  Cloudflare Pages

Latest commit: c732508
Status: ✅  Deploy successful!
Preview URL: https://5e24a3f9.geodatalytics.pages.dev
Branch Preview URL: https://renovate-vite-8-x.geodatalytics.pages.dev

View logs

@renovate
Copy link
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: web/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: vite-plugin-node-polyfills@0.24.0
npm error Found: vite@8.0.1
npm error node_modules/vite
npm error   dev vite@"8.0.1" from the root project
npm error   peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0" from @vitejs/plugin-vue@6.0.5
npm error   node_modules/@vitejs/plugin-vue
npm error     dev @vitejs/plugin-vue@"6.0.5" from the root project
npm error   1 more (vite-plugin-vuetify)
npm error
npm error Could not resolve dependency:
npm error peer vite@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from vite-plugin-node-polyfills@0.24.0
npm error node_modules/vite-plugin-node-polyfills
npm error   dev vite-plugin-node-polyfills@"0.24.0" from the root project
npm error
npm error Conflicting peer dependency: vite@7.3.1
npm error node_modules/vite
npm error   peer vite@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from vite-plugin-node-polyfills@0.24.0
npm error   node_modules/vite-plugin-node-polyfills
npm error     dev vite-plugin-node-polyfills@"0.24.0" 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-03-20T13_53_20_685Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-20T13_53_20_685Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vite-8.x branch 5 times, most recently from 0382675 to 4f5548f Compare March 19, 2026 05:32
@renovate
Copy link
Contributor Author

renovate bot commented Mar 19, 2026

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.

@brianhelba brianhelba force-pushed the renovate/vite-8.x branch 2 times, most recently from daf551b to 0382675 Compare March 20, 2026 13:50
@renovate renovate bot force-pushed the renovate/vite-8.x branch from 0382675 to dd902e9 Compare March 20, 2026 13:53
@brianhelba
Copy link
Collaborator

@annehaley Please take a look. This makes the build time much faster and simplifies the config.

@brianhelba brianhelba requested a review from annehaley March 20, 2026 14:18
Copy link
Collaborator

@annehaley annehaley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I run this locally, there are some additional changes made to package-lock.json removing several libc clauses. Does the same happen for you? If so, those changes should be committed.

@brianhelba
Copy link
Collaborator

No, it was clean for me. You're running npm install in Docker?

@brianhelba
Copy link
Collaborator

Oh, I found the issue. This change is part of npm 11.11.0 (which I was running), but not 11.9.0 (which is running in Docker).

@brianhelba
Copy link
Collaborator

@annehaley Ok, I've fixed it by regenerating package-lock.json under the older 11.9.0.

@brianhelba brianhelba requested a review from annehaley March 20, 2026 15:15
Copy link
Collaborator

@annehaley annehaley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing that. This works well now.

@brianhelba brianhelba merged commit 4fe067d into master Mar 20, 2026
3 checks passed
@brianhelba brianhelba deleted the renovate/vite-8.x branch March 20, 2026 15:16
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.

2 participants