Bump vite from 7.3.5 to 8.2.2 - #50
Conversation
89f8742 to
acb7b1b
Compare
|
Not merging — vite 8 cannot land in this repo yet, and this PR and #49 are a mutually-blocking pair. This PR alone fails #49 alone fails the mirror image of it: So neither is mergeable on its own. That is why both But pairing them does not fix it either. The hard blocker is From the npm registry, Consequence: #50 and #49 are both blocked until Recommend leaving both open and parking them behind an 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>
acb7b1b to
ef6e21d
Compare
#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>
|
Superseded by #66. |
Bumps vite from 7.3.5 to 8.2.2.
Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
de1111arelease: v8.2.2cb77e2atest(ssr): add destructing assignment case for moduleRunnerTransform (#23308)9db0b61fix(ssr): rewrite computed key of destructing parameter (#23307)8413052fix: respectresolve.preserveSymlinkswhen resolving root (fix #23197) (#23...05a003efix(config): resolve sourcemap paths against sourcemap location (#23239)495d9fffeat(deps): widen@vitejs/devtoolspeer range to v0.5.0 (#23302)1d9fa39refactor: use JSON import attributes instead of readFileSync in constants (#2...2804636fix(css): don't pass empty targets to lightningcss (#23295)599b44btest(module-runner): simplify server-hmr tests (#23300)4a261f2test(module-runner): add TLA circular import case (#23299)