npm ci needs an existing package-lock.json

What this error means

npm ci only installs from a package-lock.json. Projects made in Lovable or Bolt often have a bun.lockb, or no lockfile at all.

Why it happens

npm ci will not resolve versions itself. It only installs when package-lock.json or npm-shrinkwrap.json is already in the repo.

The message tools print

npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1.

How to fix it

1. Run npm install locally and commit the package-lock.json it creates.
2. Or switch the build to the package manager your lockfile belongs to (bun install, pnpm install).

Check a log that shows this

Paste the failing step into the build error explainer. It matches this message, and any others in the same log, in your browser. Nothing is uploaded.

Other Web build errors

• npm ci: lockfile is out of sync with package.json
• npm ERESOLVE unable to resolve dependency tree
• JavaScript heap out of memory
• Rollup failed to resolve import
• error TS: TypeScript errors stop the build
• Could not find the web assets directory
• Capacitor: Invalid App ID