Remove frontend/bun.lock so Railpack uses npm + package-lock.json

↗ view on GitHub · Jason Walkow · 2026-05-03 · 99375788

Railpack prefers bun when bun.lock is present, but the file was stale
relative to package.json after the Next.js bump and failed
--frozen-lockfile. The repo standardizes on npm per the README, so the
bun lockfile is unused - removing it lets Railpack fall back to npm and
the up-to-date package-lock.json.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Repository jsw324/law-llm
Author Jason Walkow <jason.walkow@gmail.com>
Authored
Parents 492dd408
Stats 1 file changed , -4165
Part of Next.js 16 upgrade and "unburdn law" rebrand

Capture this commit into my fork

Download a Markdown prompt that tells Claude how to port this exact commit into your working tree. Run it via claude -p < capture-commit-99375788.md from inside the repo you want the change in.

⬇ Download capture-commit-99375788.md