foolish-bandit/gary#3: Remove frontend/bun.lock so Cloudflare uses npm

Remove frontend/bun.lock so Cloudflare uses npm

✅ merged · #3 · foolish-bandit/gary ← foolish-bandit/gary · opened 19d ago by foolish-bandit · merged 19d ago by foolish-bandit · self · -4,165 across 1 file · ↗ on GitHub

From the PR description

Summary

Delete frontend/bun.lock so Cloudflare's framework auto-detection picks npm instead of Bun.
frontend/package-lock.json is unchanged - npm install reports up to date.

Why

Cloudflare's build agent prefers Bun whenever a Bun lockfile is present, but this project is npm-managed and the existing package-lock.json is the source of truth. With bun.lock removed, Cloudflare falls back to npm clean-install (the same behavior we already see in PR #2 build logs).

Verification

npm install - up to date, audited 1114 packages in 10s
npm ci - clean install succeeds, lockfile consistent
npm run build (Next.js production build) - passes, all 13 routes generate
npx opennextjs-cloudflare build - passes, Worker saved in .open-next/worker.js

Test plan

Cloudflare deploy uses npm (no Bun in build logs)
OpenNext build artifacts produced as before

https://claude.ai/code/session_01McEfVnpbGdMs5TgeTM7P3R

Generated by Claude Code

Our analysis

Remove Bun lockfile so Cloudflare builds with npm — read the full analysis →

Think the analysis missed something the PR description covers?

Commits in this PR (1)

SHA Subject Author Date

9de83b4a Remove frontend/bun.lock so Cloudflare uses npm Claude 2026-05-07 ↗ GitHub

SHA	Subject	Author	Date
`9de83b4a`	Remove frontend/bun.lock so Cloudflare uses npm	Claude	2026-05-07	↗ GitHub
commit body Cloudflare's framework auto-detection picks Bun whenever a Bun lockfile is present, even though the project is npm-managed and ships with package-lock.json. Removing bun.lock makes the build agent fall back to npm. package-lock.json is unchanged (npm install reports "up to date"). https://claude.ai/code/session_01McEfVnpbGdMs5TgeTM7P3R

commit body

Cloudflare's framework auto-detection picks Bun whenever a Bun
lockfile is present, even though the project is npm-managed and
ships with package-lock.json. Removing bun.lock makes the build
agent fall back to npm. package-lock.json is unchanged
(npm install reports "up to date").

https://claude.ai/code/session_01McEfVnpbGdMs5TgeTM7P3R

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-3.md from inside the repo you want the changes in.

⬇ Download capture-pull-3.md