Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR bumps
@vercel/nccto^0.45.0in package.json, but package-lock.json was not changed. Its root entry still declares"@vercel/ncc": "^0.38.3"(line 16) andnode_modules/@vercel/nccstill resolves to 0.38.4 (lines 2241-2244). For 0.x versions a caret range only allows patch updates, so 0.38.4 does not satisfy^0.45.0. That meansnpm ciwill fail with a 'package.json and package-lock.json are not in sync' error, andnpm installwill quietly rewrite the lockfile. The committed ncc bundles (*/dist/index.js, which CLAUDE.md says must be rebuilt and committed) were also not rebuilt with the new ncc version, so the upgrade is never actually used. Fix: runnpm installto regenerate package-lock.json, runnpm run build, and commit both the lockfile and the rebuilt dist bundles.Regenerate the lockfile and rebuild the bundles with ncc 0.45.0:
Check the box to apply the fix or reply for a change | Was this helpful? React with 👍 / 👎