Fix pnpm lockfile mismatch for react peerDependency specifier#416
Fix pnpm lockfile mismatch for react peerDependency specifier#416
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
github-actions
bot
added
dependencies
| specifier: '>=18.0.0' | ||
| version: 19.2.3 |
There was a problem hiding this comment.
The React runtime has been upgraded to version 19.2.3, but the @types/react package is still at version 18.3.27 (defined as ^18.0.0 in devDependencies at line 367). This creates a type mismatch where the TypeScript types don't match the actual React runtime version being used. You should update the @types/react specifier to ^19.0.0 or similar to ensure type definitions match the React version.
| specifier: '>=18.0.0' | ||
| version: 19.2.3 |
There was a problem hiding this comment.
The PR title mentions "improve output clarity" but the actual changes are about updating React dependencies and fixing a pnpm lockfile mismatch. The title should be updated to accurately reflect that this PR is updating React from version 18 to 19, or the changes should align with the stated purpose of improving output clarity.
Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
github-actions
bot
added
the
documentation
Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>
CI was failing at dependency installation due to specifier mismatch between
pnpm-lock.yamlandpackages/client-react/package.json.Changes
pnpm-lock.yamlreact specifier:^18.0.0→>=18.0.0(aligns with peerDependency declaration)18.3.1→19.2.3Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.