fix: sync package-lock.json to unblock Vercel npm ci deploys - #421
Conversation
Vercel installs with `npm ci` (see vercel.json installCommand), which requires package.json and package-lock.json to be fully in sync. The lockfile committed in #413 (brace-expansion CVE bump) was missing several optional transitive deps (@emnapi/core, @emnapi/runtime, @emnapi/wasi-threads), so `npm ci` failed with EUSAGE before the build could run, erroring out every production deployment. Regenerated the lockfile with `npm install` so it is in sync again. Verified `npm ci` and `npm run build` both succeed. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR refreshes package-lock.json so it is consistent with package.json for Vercel's npm ci install path, adding the missing optional @emnapi transitive entries and updating lockfile peer metadata.
Concerns
- No blocking correctness, security, or spec-alignment concerns found in the annotated diff.
spec_context.mdreports no approved or repository spec context for this PR.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Problem
Production deployments on Vercel for the docs repo were erroring out.
Root cause
Vercel installs dependencies with
npm ci(installCommandinvercel.json).npm cirequirespackage.jsonandpackage-lock.jsonto be fully in sync and fails hard otherwise. The lockfile committed in #413 (the brace-expansion CVE bump) was missing several optional transitive dependencies, sonpm cifailed withEUSAGEat the install step — before the build ever ran:This was easy to miss locally because
astro buildon its own uses a loosenpm install, which silently repairs the lockfile. The strictnpm ciVercel uses does not.Fix
Regenerated
package-lock.jsonwithnpm installso it is in sync withpackage.jsonagain. Only the lockfile changes.Verification
npm ci— now exits0(previously failed withEUSAGE).npm run build— succeeds, 352 pages built,.vercel/outputproduced.Note (not blocking)
vercel.jsoncurrently has 1,976 redirects. Vercel's route limit is 2,048, so this is under the cap for now but worth keeping an eye on as redirects are added — the repo convention puts every redirect invercel.json.Conversation: https://staging.warp.dev/conversation/8d303aee-c883-4f1a-a25c-dbca722787f8
Run: https://oz.staging.warp.dev/runs/019faf3e-8107-757b-ae33-89846d9abd23
This PR was generated with Oz.