Fixes · Deploys that break
Works on my computer, breaks on deploy: no lockfile, or two of them
Without one committed lockfile, the host installs different package versions from the ones you tested, and an app that ran yesterday fails to build today.
What you see
A deploy fails, or the live app misbehaves, though nothing in your code changed and it works on your computer.
Why it happens
package.json allows a range of versions. A lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock) pins the exact ones you installed. With none committed, each deploy picks the newest it's allowed. With two from different package managers, the host chooses one by its own rules, which may not be yours.
How to fix it
- Pick the package manager you actually use, run its install, and commit the lockfile it writes.
- Delete the other managers' lockfiles from the repository.
- If your host installs with a different manager, set it to yours (Vercel and most hosts follow the lockfile they find).
Or ask your AI tool to fix it
Paste this into Lovable, Bolt, v0, Replit or Cursor, and let it make the change.
Make this repository use a single package manager: keep and commit only its lockfile, delete the lockfiles of any other package manager, and make sure installing from the lockfile builds the app.
Don't change what the app does.
Never put a secret key or password in the code: read it from an environment variable.
If a step has to be done outside the code, like revoking a key in a provider's dashboard, list it for me at the end instead of skipping it.How Launchpad helps
The launch check flags a missing lockfile, and more than one. Launchpad's deploys install from the lockfile you commit.
Check your app for this, freeStart free