Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion chrome-crx/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@
"@types/react": "^19.2.0",
"@types/react-dom": "^19.2.3",
"@types/react-syntax-highlighter": "15.5.13",
"@vitejs/plugin-react": "^5.1.4",
"@vitejs/plugin-react": "^6.0.3",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge 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 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge 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 👍 / 👎.

"@vitest/coverage-v8": "^4.1.5",
"eslint": "^10.0.2",
"eslint-config-prettier": "^10.1.8",
Expand Down
Loading