Skip to content

fix: Vercel installs the docs from package-lock.json (npm ci) - #278

Merged
sonpiaz merged 1 commit into
mainfrom
fix/docs-npm-ci-admin
Nov 14, 2026
Merged

sonpiaz merged 1 commit into
mainfrom
fix/docs-npm-ci-admin

Conversation

@sonpiaz

@sonpiaz sonpiaz commented Nov 13, 2026 •

Copy link
Copy Markdown
Member

What

Vercel now installs the docs from package-lock.json, the lockfile CI tests.

  • yarn.lock is removed; package-lock.json is the one lockfile.
  • vercel.json sets installCommand to npm ci, and nothing else.

Why

Production docs today run a dependency set no one tested.

  • Vercel sees yarn.lock and installs with yarn, but that file was last updated in March and lacks most of today's tree: 473 entries against package-lock.json's 557, and no fumadocs-ui.
  • So every deploy resolves those packages fresh, within their ranges. Today that is fumadocs-ui 16.19.0, which pulls motion 14, while CI runs npm ci on package-lock.json: fumadocs-ui 16.7.11, motion 12.38.0.
  • On 13/11 a preview build failed in that install. motion 14.14.0 was published at 14:49:15 UTC and its dependency framer-motion 14.14.0 at 14:51:13 UTC, and the install ran between the two.

This PR brings production back to the tested set, and makes every deploy install exactly what CI checks.

package.json still carries a yarn-only resolutions field. npm ignores it, and package-lock.json already pins those two packages (compute-scroll-into-view 3.1.1, scroll-into-view-if-needed 3.1.0), so it changes nothing here.

Proof

  • This PR's Vercel preview (commit 1bda2d4) installs with npm, then builds green:
    Running "install" command: `npm ci`...
    added 445 packages, and audited 446 packages in 16s
    Build Completed in /vercel/output [55s]
    
  • A clean tree of this commit, with npm ci from the registry and an empty cache:
    • the installed tree equals package-lock.json entry for entry (443 entries; 113 optional or platform-only packages are absent), with fumadocs-ui 16.7.11 and motion 12.38.0;
    • npm run build passes;
    • the three checks CI runs all pass: check-agent-surface.mjs, check-docs-host.mjs and check-docs-host-http.mjs.

Order

This merges before the blog index twin PR (#277). After it deploys, the production docs must be READY and /docs must answer 200 before #277 merges.

🤖 Generated with Claude Code

Vercel saw yarn.lock and installed with yarn. That lockfile was last updated in
March and lacks most of today's tree (473 entries against package-lock.json's
557; no fumadocs-ui), so every deploy resolved those packages fresh: production
docs ran a newer, untested dependency set (fumadocs-ui 16.19.0 pulls motion 14)
than CI, which runs npm ci on package-lock.json (fumadocs-ui 16.7.11, motion
12.38.0). A preview on 13/11/2026 failed in that install, between the motion and
framer-motion 14.14.0 publishes.

- yarn.lock removed; package-lock.json is the one lockfile.
- vercel.json sets installCommand to npm ci, so a deploy installs exactly what CI tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
affitor-docs Ready Ready Preview Nov 13, 2026 3:07pm UTC

Request Review

@sonpiaz
sonpiaz marked this pull request as ready for review November 14, 2026 00:29
@sonpiaz
sonpiaz merged commit 74d376d into main Nov 14, 2026
5 checks passed

This branch was successfully deployed

1 active deployment
Preview — 1bda2d45 Deployed Nov 13, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant