[ops] Regenerate package-lock.json - fixes Railway npm ci failure
Lock file was out of sync with package.json. canvas@^3.2.3 was added in the auth-RLS hardening commit but the lock file wasn't regenerated, so prod build failed on `npm ci` with "Missing: canvas@3.2.3 from lock file" plus all of canvas's transitive deps. Local dev worked because bun.lock is up to date - bun and npm lock files drifted apart silently. Ran `npm install --package-lock-only` and verified with `npm ci --dry-run` which now succeeds. No package.json changes; only the lock catches up. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
| Repository | nwhitehouse/mike |
|---|---|
| Author | Nick Whitehouse <nick.whitehouse@mccarthyfinch.com> |
| Authored | |
| Parents | a663f8df |
| Stats | 1 file changed , +388 |
| Part of | Launch-week hosting and CI ops |
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-0d9be7cb.md
from inside the repo you want the change in.