Bump @vitejs/plugin-react from 5.1.2 to 6.1.0 - #49
Conversation
Bumps [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) from 5.1.2 to 6.1.0. - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.1.0/packages/plugin-react) --- updated-dependencies: - dependency-name: "@vitejs/plugin-react" dependency-version: 6.1.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
260cdb4 to
602e72e
Compare
|
Not merging — this PR and #50 (vite 7 → 8) are a mutually-blocking pair, and both are gated by This PR alone fails
Pairing them still does not resolve. The hard cap is in this PR's own trace:
Consequence: Generated by Claude Code |
#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 @vitejs/plugin-react from 5.1.2 to 6.1.0.
Release notes
Sourced from @vitejs/plugin-react's releases.
... (truncated)
Changelog
Sourced from @vitejs/plugin-react's changelog.
... (truncated)
Commits
39b3173release: plugin-react@6.1.0 (#1428)f1340b0feat(react): add native React Compiler support (#1419)9ab698efix(deps): update all non-major dependencies (#1375)68c0cb8release: plugin-react@6.0.5 (#1362)555cdbcfix(react): make the react compiler preset filter linear (#1353)a00a9f8fix(deps): update all non-major dependencies (#1327)f4b5498release: plugin-react@6.0.47a40659fix(react):$RefreshSig$ is not definedwith NODE_ENV=production vite dev ...98b32d4fix(deps): update react 19.2.8 (#1298)8ae5449fix: babel-plugin-react-compiler cannot be imported when used in a framework ...