Skip to content
Closed
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 examples/react-nextjs/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
"@evolu/react-web": "latest",
"@tabler/icons-react": "^3.35.0",
"clsx": "^2.1.1",
"next": "^16.0.0",
"next": "^16.1.5",

Choose a reason for hiding this comment

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

P1 Badge Update pnpm-lock to match the new Next spec

This bumps next to ^16.1.5 in examples/react-nextjs/package.json, but pnpm-lock.yaml still records the importer specifier as ^16.0.0 and resolves to 16.0.7 (see pnpm-lock.yaml lines 462–464). Because the repo’s install action runs pnpm install --frozen-lockfile ( .github/actions/setup-node-pnpm-install/action.yaml line 17), installs will now fail with a lockfile mismatch. Regenerate and commit the lockfile so frozen installs succeed.

Useful? React with 👍 / 👎.

Copy link

Copilot AI Jan 31, 2026

Choose a reason for hiding this comment

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

The Next.js dependency is being upgraded to version 16.1.5, but the related eslint-config-next package in devDependencies remains at version ^16.0.0. These packages are typically versioned together by the Next.js team and should be kept in sync to ensure compatibility. Consider also updating eslint-config-next to ^16.1.5 to match the Next.js version.

Copilot uses AI. Check for mistakes.
"react": "19.1.0",
"react-dom": "19.1.0"
},
Expand Down
Loading