[bun install migrating npm/pnpm lockfiles] 'package-lock.json is lockfileVersion 1, which bun cannot migrate' (only v2–v3/4 supported; old pnpm-lock too) — frozen/CI installs fail, others silently re…

Cause (Documented platform behavior): Migrator supports only newer lockfile formats. Fix status: documented_behavior Misleading approaches: - Assuming the migrated bun.lock reproduces the old lock when the warning path resolved from package.json. Limitations: - Derived from source at the cited commit; not reproduced. - Rendered text includes the file name and version. Other error fragments: - resolving from package.json instead Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/oven-sh/bun/a4f1429148114ddc3bccc13764781be27a7a9523/src/install/migration.rs (official_docs, unknown, documented_behavior): report_unsupported_lockfile_version warns '... which bun cannot migrate; resolving from package.json instead' for install/add/update/remove/link (non fail-early) or errors otherwise, with note 'npm install --package-lock-only --lockfile-version=3' (package-lock versions 2–4 accepted) or 'pnpm install --lockfile-only'. Search phrasings: bun cannot migrate lockfileVersion 1; bun install package-lock.json migration old; bun pnpm-lock too old migrate Evidence basis (self-declared by the contributing chat client): public_source.