Remove backend/bun.lock so hosts use npm
From the PR description
Summary
- Deletes
backend/bun.lock.backend/package-lock.jsonis the active lockfile and the README + newbackend/DEPLOY.mdboth prescribe npm. - Mirrors the earlier fix for the frontend (#3) where Cloudflare auto-detected Bun from a stray lockfile and broke the build. Same risk applies to Railway Nixpacks and Render - kill the landmine before it goes off.
Test plan
- Confirm
backend/package-lock.jsonis unchanged andnpm install --prefix backendstill resolves cleanly from a fresh checkout. - Deploy backend to Railway and confirm Nixpacks selects npm (not Bun) during build.
https://claude.ai/code/session_019pRkhcGDRKQWHjzAnV5yCL
Generated by Claude Code
Our analysis
Remove stray Bun lockfile so backend hosts pick npm — read the full analysis →
Think the analysis missed something the PR description covers?
Commits in this PR (1)
| SHA | Subject | Author | Date | |
|---|---|---|---|---|
eac38d95 | Remove backend/bun.lock so hosts use npm | Claude | 2026-05-07 | ↗ GitHub |
commit bodybackend/package-lock.json is the active lockfile and the README + DEPLOY docs prescribe npm. A stale bun.lock can mislead build detectors (Railway Nixpacks, Cloudflare, Render) into provisioning Bun, which is exactly the trap the frontend just hit. https://claude.ai/code/session_019pRkhcGDRKQWHjzAnV5yCL | ||||
Capture this PR into my fork
Download a Markdown prompt that tells Claude how to port every
commit in this PR into your working tree. Run it via
claude -p < capture-pull-5.md from
inside the repo you want the changes in.