Skip to content

Bump vite from 7.3.5 to 8.2.2 - #50

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vite-8.2.2
Closed

Bump vite from 7.3.5 to 8.2.2#50
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vite-8.2.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 28, 2026

Copy link
Copy Markdown
Contributor

Bumps vite from 7.3.5 to 8.2.2.

Release notes

Sourced from vite's releases.

plugin-legacy@8.2.2

Please refer to CHANGELOG.md for details.

v8.2.2

Please refer to CHANGELOG.md for details.

plugin-legacy@8.2.1

Please refer to CHANGELOG.md for details.

v8.2.1

Please refer to CHANGELOG.md for details.

create-vite@8.2.0

Please refer to CHANGELOG.md for details.

plugin-legacy@8.2.0

Please refer to CHANGELOG.md for details.

v8.2.0

Please refer to CHANGELOG.md for details.

v8.2.0-beta.0

Please refer to CHANGELOG.md for details.

v8.1.5

Please refer to CHANGELOG.md for details.

v8.1.4

Please refer to CHANGELOG.md for details.

v8.1.3

Please refer to CHANGELOG.md for details.

v8.1.2

Please refer to CHANGELOG.md for details.

v8.1.1

Please refer to CHANGELOG.md for details.

create-vite@8.1.0

Please refer to CHANGELOG.md for details.

plugin-legacy@8.1.0

Please refer to CHANGELOG.md for details.

v8.1.0

Please refer to CHANGELOG.md for details.

plugin-legacy@8.1.0-beta.0

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

Sourced from vite's changelog.

8.2.2 (2026-08-20)

Features

  • deps: widen @vitejs/devtools peer range to v0.5.0 (#23302) (495d9ff)

Bug Fixes

  • bundled-dev: handle lazy request error (#23291) (3ba026d)
  • bundled-dev: hot update through circular imports instead of reloading (#23259) (3dbddef)
  • config: resolve sourcemap paths against sourcemap location (#23239) (05a003e)
  • css: don't pass empty targets to lightningcss (#23295) (2804636)
  • define: fix match escaped dots to support $-prefixed define keys (#23249) (dcf88bd)
  • deps: update all non-major dependencies (#23217) (ba958bd)
  • deps: update rolldown-related dependencies (#23218) (83ecb2c)
  • module-runner: exclude completed modules from in-flight cycle detection (fix #22999) (#23009) (d9b10a9)
  • optimizer: close custom extension analysis bundles (#23207) (8fb7675)
  • reduce Windows 8.3-short-name detection false-positives (#23066) (02cffa9)
  • respect resolve.preserveSymlinks when resolving root (fix #23197) (#23198) (8413052)
  • ssr: rewrite computed key of destructing parameter (#23307) (9db0b61)
  • vite: update outdated upstream file links in license comments (#23285) (c0f2fc6)

Documentation

Miscellaneous Chores

Code Refactoring

  • use JSON import attributes instead of readFileSync in constants (#23258) (1d9fa39)
  • use named regex constants over inline literals (#22964) (5c1c6c6)

Tests

  • define: close rolldown bundler after generate (#23231) (b4d66fe)
  • module-runner: add TLA circular import case (#23299) (4a261f2)
  • module-runner: simplify server-hmr tests (#23300) (599b44b)
  • ssr: add destructing assignment case for moduleRunnerTransform (#23308) (cb77e2a)

Build System

  • use JSON import attributes instead of readFIleSync in rolldown configs (#23251) (d615bcd)

8.2.1 (2026-08-06)

Bug Fixes

  • build: make client chunkImportMap work with sharedPlugins: true (#23184) (15f0307)
  • bundled-dev: inject client script tag before chunk scripts (#23161) (eac0cc8)

... (truncated)

Commits
  • de1111a release: v8.2.2
  • cb77e2a test(ssr): add destructing assignment case for moduleRunnerTransform (#23308)
  • 9db0b61 fix(ssr): rewrite computed key of destructing parameter (#23307)
  • 8413052 fix: respect resolve.preserveSymlinks when resolving root (fix #23197) (#23...
  • 05a003e fix(config): resolve sourcemap paths against sourcemap location (#23239)
  • 495d9ff feat(deps): widen @vitejs/devtools peer range to v0.5.0 (#23302)
  • 1d9fa39 refactor: use JSON import attributes instead of readFileSync in constants (#2...
  • 2804636 fix(css): don't pass empty targets to lightningcss (#23295)
  • 599b44b test(module-runner): simplify server-hmr tests (#23300)
  • 4a261f2 test(module-runner): add TLA circular import case (#23299)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 28, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vite-8.2.2 branch from 89f8742 to acb7b1b Compare August 31, 2026 06:15

Copy link
Copy Markdown
Contributor

Not merging — vite 8 cannot land in this repo yet, and this PR and #49 are a mutually-blocking pair.

This PR alone fails npm ci:

$ npm ci
npm error Found: vite@8.2.2
npm error Could not resolve dependency:
npm error peer vite@"^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from @vitejs/plugin-react@5.1.2

#49 alone fails the mirror image of it:

npm error peer vite@"^8.0.0" from @vitejs/plugin-react@6.1.0
npm error Found: vite@7.3.5

So neither is mergeable on its own. That is why both ci checks are red — npm ci is CI's first step and dies in ~13s.

But pairing them does not fix it either. The hard blocker is electron-vite, visible in #49's resolution trace:

npm error   peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0" from electron-vite@5.0.0

From the npm registry, electron-vite@5.0.0 is the latest stable release and caps vite at ^7. vite 8 support first appears in electron-vite@6.0.0-beta.0 (peer ^6.0.0 || ^7.0.0 || ^8.0.0), which is still a beta.

Consequence: #50 and #49 are both blocked until electron-vite@6 ships stable, at which point all three (electron-vite 6, vite 8, @vitejs/plugin-react 6) need to move in one PR. Bumping any one of them alone will always leave npm ci unresolvable.

Recommend leaving both open and parking them behind an electron-vite@6 stable release rather than forcing them through with --legacy-peer-deps — this is the bundler, and CI does not run npm run build, so a forced resolution would not be caught here. (I verified separately that npm run build is absent from ci.yml; only typecheck and vitest run.)


Generated by Claude Code

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 7.3.5 to 8.2.2.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.2.2/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-version: 8.2.2
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vite-8.2.2 branch from acb7b1b to ef6e21d Compare September 3, 2026 18:06
BernardJen added a commit that referenced this pull request Sep 3, 2026
#64)

`npm run lint` has never worked (#63). The script existed from the start but
no config ever did, so eslint exited non-zero on every invocation, and nothing
caught it because no workflow ran it.

Fixing that also unblocks #51. Dependabot's eslint 9 -> 10 bump was failing at
`npm ci` with ERESOLVE, not at any check step: eslint-plugin-react@7.37.5 peers
`eslint ^3 || ... || ^9.7` and has no release that accepts 10 (the `next` tag is
a stale 7.8.0-rc.0 peering ^3 || ^4). The plugin was also dead weight - with no
config, nothing had ever referenced it. Dropping it and moving
@typescript-eslint to ^8.69.0, the first line peering `^8.57 || ^9 || ^10`,
leaves nothing in the tree capping eslint's major.

The new config is deliberately not built on @eslint/js, which peers a single
eslint major and would recreate this exact failure on the next bump.

Getting to a clean run needed some dead code removed: unused imports, two catch
bindings that were never read, and `currentPresentationPath` in both Windows
backends, which was written twice and read never (macos.ts genuinely reads it
as a fallback, so it stays there). `require-atomic-updates` is set to 'warn'
rather than disabled - it flags seven pre-existing interleaving hazards in the
automation backends that need a real PowerPoint install to fix safely.

CI runs lint now, between install and typecheck. A lint script no job runs is
how this went unnoticed for the life of the repo.

Finally, dependabot grouping, because #51 was one of four PRs failing the same
way: a solo bump of a package whose peers are pinned to a sibling's major can
never resolve alone. #49 and #50 are the clearest case - one bumps vite to 8,
the other bumps @vitejs/plugin-react to a version requiring vite 8, and each
fails precisely because the other is a separate PR.

Two of the four remain blocked upstream and are not addressed here: #47
(typescript 7) waits on @typescript-eslint, which still peers `<6.1.0`, and
#49/#50 wait on electron-vite 6 leaving beta, since 5.0.0 peers `vite ^5 ||
^6 || ^7`. Grouped, those now sit still instead of failing every week.

Refs #63, #51

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #66.

@dependabot dependabot Bot closed this Sep 3, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/vite-8.2.2 branch September 3, 2026 19:52
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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant