mirror of
https://github.com/PR0M3TH3AN/bitvid.git
synced 2026-10-27 07:52:24 +00:00
[build] Drop the stale pnpm-lock.yaml that was failing deploys
Adding api/ made Vercel run a second install phase to bundle the serverless function. That phase auto-detects the lockfile and ignores the project's `installCommand: npm install`, so it picked pnpm and failed: ERR_PNPM_OUTDATED_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json The static build itself succeeded every time -- version injected, deploy artifact verified -- but the failed function install aborted the whole deployment, so unstable kept serving the last good build from two days prior. pnpm-lock.yaml has not been touched since 2026-02-08 and was already stale by 7 added and 4 mismatched dependencies BEFORE this branch (bitcoin-connect, blossom-client-sdk, cssnano, nostr-wasm, postcss-cli, postcss-import, esbuild, nostr-tools, jsdom, stylelint); hls.js merely joined the list. It never mattered because nothing installed from it until now. Nothing references pnpm: package.json scripts, .github/workflows and CONTRIBUTING all use npm, and vercel.json already pins `installCommand: npm install`. package-lock.json is the maintained lockfile. Keeping a second, unmaintained one only guarantees the two disagree again. Restore with `git revert` (and regenerate it with `pnpm install --lockfile-only`) if pnpm is ever adopted deliberately. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
1 parent
d141c316a9
commit
e5784893a8
1 file changed
-3357
Generated
-3357
File diff suppressed because it is too large.
Load diff
Reference in new issue
Block a user