fix: swap bun install for npm ci to fix integrity check failures

Browse Source

Known Bun bug (oven-sh/bun#1590, #26879, #18864) causes
IntegrityCheckFailed during tarball extraction in Docker/CI.
This is a 3+ year old issue with no fix in sight.

Changes:
- Generate package-lock.json via npm install --package-lock-only
- Dockerfile: add nodejs npm to all stages, replace bun install
  with npm ci --legacy-peer-deps (peer dep conflict exists for
  eslint@8 with eslint-config-next@16)
- Keep bun as runtime (bun test, bun run build, bun run start)
- pr.yml: npm ci, npx prisma generate, npx playwright
- release.yml: node scripts, npm test
- build-ci-images.yml: add package-lock.json trigger path

...

This commit is contained in:

David Gwilliam

2026-05-17 03:05:57 -07:00

parent baeab0fbe5

commit 4a09bd044a

5 changed files with 10495 additions and 20 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

package-lock.json

Generated

+10473

File diff suppressed because it is too large Load Diff