Repository navigation
fix: Vercel installs the docs from package-lock.json (npm ci) - #278
Merged
Merged
Conversation
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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sonpiaz
marked this pull request as ready for review
November 14, 2026 00:29
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Vercel now installs the docs from
package-lock.json, the lockfile CI tests.yarn.lockis removed;package-lock.jsonis the one lockfile.vercel.jsonsetsinstallCommandtonpm ci, and nothing else.Why
Production docs today run a dependency set no one tested.
yarn.lockand installs with yarn, but that file was last updated in March and lacks most of today's tree: 473 entries againstpackage-lock.json's 557, and nofumadocs-ui.fumadocs-ui16.19.0, which pullsmotion14, while CI runsnpm cionpackage-lock.json:fumadocs-ui16.7.11,motion12.38.0.motion14.14.0 was published at 14:49:15 UTC and its dependencyframer-motion14.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.jsonstill carries a yarn-onlyresolutionsfield. npm ignores it, andpackage-lock.jsonalready pins those two packages (compute-scroll-into-view3.1.1,scroll-into-view-if-needed3.1.0), so it changes nothing here.Proof
1bda2d4) installs with npm, then builds green:npm cifrom the registry and an empty cache:package-lock.jsonentry for entry (443 entries; 113 optional or platform-only packages are absent), withfumadocs-ui16.7.11 andmotion12.38.0;npm run buildpasses;check-agent-surface.mjs,check-docs-host.mjsandcheck-docs-host-http.mjs.Order
This merges before the blog index twin PR (#277). After it deploys, the production docs must be READY and
/docsmust answer 200 before #277 merges.🤖 Generated with Claude Code