chore(crx-deps)(deps-dev): bump @vitejs/plugin-react from 5.2.0 to 6.0.3 in /chrome-crx - #288
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 35faecfae4
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@types/react": "^19.2.0", | ||
| "@types/react-dom": "^19.2.3", | ||
| "@vitejs/plugin-react": "^5.1.4", | ||
| "@vitejs/plugin-react": "^6.0.3", |
There was a problem hiding this comment.
Commit the Bun lockfile with this bump
This manifest now requires @vitejs/plugin-react ^6.0.3, but the tracked root bun.lock still records the chrome-crx workspace dependency as ^5.1.4 and resolves @vitejs/plugin-react@5.2.0 (bun.lock:75,672). The TS workflows install with bun install --frozen-lockfile (.github/workflows/lint-ts.yml:27-28), and Bun's frozen mode disallows lockfile changes, so a fresh CI install for this commit is forced to fail or remain on the old plugin. Please update and commit bun.lock together with the package.json change.
Useful? React with 👍 / 👎.
| "@types/react": "^19.2.0", | ||
| "@types/react-dom": "^19.2.3", | ||
| "@vitejs/plugin-react": "^5.1.4", | ||
| "@vitejs/plugin-react": "^6.0.3", |
There was a problem hiding this comment.
Keep plugin-react on a Vite-compatible major
This upgrades @vitejs/plugin-react to v6 while chrome-crx still depends on vite ^7.3.1 in the same file. The published @vitejs/plugin-react@6.0.3 package manifest declares peerDependencies.vite as ^8.0.0, so after the lockfile is refreshed this workspace installs an unsupported Vite/plugin pairing for every build. Please either upgrade Vite to 8 in the same change or keep the React plugin on 5.x.
Useful? React with 👍 / 👎.
Bumps [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) from 5.2.0 to 6.0.3. - [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.0.3/packages/plugin-react) --- updated-dependencies: - dependency-name: "@vitejs/plugin-react" dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
35faecf to
c028426
Compare
Bumps @vitejs/plugin-react from 5.2.0 to 6.0.3.
Release notes
Sourced from @vitejs/plugin-react's releases.
... (truncated)
Changelog
Sourced from @vitejs/plugin-react's changelog.
... (truncated)
Commits
640fd35release: plugin-react@6.0.3889efb0fix(deps): update all non-major dependencies (#1249)6c57dd4fix(plugin-react): use '/' base in bundledDev preamble to fix non-root base p...3cc33a7fix(deps): update react-related dependencies (#1245)c0f7c7fdocs: mention the Biome rule in the "Consistent components exports" section (...cd80f0ffix(deps): update all non-major dependencies (#1241)e38accafix(deps): update all non-major dependencies (#1227)9a9bb26perf(react): improve react compiler preset so that slightly more modules are ...6535b55release: plugin-react@6.0.2bf0e43bfeat(react): whitelist debugging-options (#1189)