build(take): Update Next.js version to 15.2.8 in package.json#212
build(take): Update Next.js version to 15.2.8 in package.json#212dmitrii-parshenkov merged 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| "resolved": "https://registry.npmjs.org/next/-/next-15.2.8.tgz", | ||
| "integrity": "sha512-pe2trLKZTdaCuvNER0S9Wp+SP2APf7SfFmyUP9/w1SFA2UqmW0u+IsxCKkiky3n6um7mryaQIlgiDnKrf1ZwIw==", | ||
| "license": "MIT", | ||
| "peer": true, |
There was a problem hiding this comment.
Bug: Critical dependencies incorrectly marked as peer dependencies
The lockfile incorrectly marks next, react, react-dom, nextra, and @types/node with "peer": true even though these are direct dependencies in package.json. This corrupted lockfile state can cause npm ci or fresh installs to fail or behave unexpectedly, as npm may not properly install these packages assuming they'll be provided by a parent package. The lockfile needs to be regenerated correctly.
Additional Locations (2)
1 participant
Note
Upgrade Next.js to 15.2.8 with corresponding lockfile updates.
nextto15.2.8inpackage.json.@next/env).Written by Cursor Bugbot for commit 1fd21f5. This will update automatically on new commits. Configure here.