Cloudflare Pages npm ci fails claiming package-lock.json mismatch, but lockfile is valid
❓Other (read rules)
I am seeing a reproducible Cloudflare Pages build failure that I cannot explain, and I suspect a Pages bug or environment issue.
Context
- Frontend: React + Vite
- Node: 22.16.0
- npm: 10.9.2
- Package manager: npm
- CI command: npm ci && npm run build
- Same repo and commands work on Netlify
- Fails only on Cloudflare Pages
Error
Cloudflare Pages fails during dependency install:
Why this is confusing
- My package.json does not include Ant Design at all
- npm ls antd returns (empty)
- I removed node_modules and package-lock.json
- Ran npm install, which regenerated package-lock.json
- npm ci passes locally
- Git shows no changes to package-lock.json
- Same commit builds successfully on Netlify
What I tried
- Clearing Cloudflare Pages build cache
- Disabling/enabling cache
- Deleting and recreating the Pages project
- Verifying Node/npm versions match local
- Fresh git clone locally + npm ci (passes)
Observation
Cloudflare Pages consistently reports missing dependencies (Ant Design / rc-* packages) that are not present in my dependency graph and have not existed in the repo for some time.
Has anyone seen Pages hold onto stale dependency metadata or mis-handle npm ci like this? Any way to force a truly cold install?
Context
- Frontend: React + Vite
- Node: 22.16.0
- npm: 10.9.2
- Package manager: npm
- CI command: npm ci && npm run build
- Same repo and commands work on Netlify
- Fails only on Cloudflare Pages
Error
Cloudflare Pages fails during dependency install:
Why this is confusing
- My package.json does not include Ant Design at all
- npm ls antd returns (empty)
- I removed node_modules and package-lock.json
- Ran npm install, which regenerated package-lock.json
- npm ci passes locally
- Git shows no changes to package-lock.json
- Same commit builds successfully on Netlify
What I tried
- Clearing Cloudflare Pages build cache
- Disabling/enabling cache
- Deleting and recreating the Pages project
- Verifying Node/npm versions match local
- Fresh git clone locally + npm ci (passes)
Observation
Cloudflare Pages consistently reports missing dependencies (Ant Design / rc-* packages) that are not present in my dependency graph and have not existed in the repo for some time.
Has anyone seen Pages hold onto stale dependency metadata or mis-handle npm ci like this? Any way to force a truly cold install?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Was this page helpful?
