Fix CI: remove stray package-lock.json, reformat setup.ts
Fixes both failures from the 1.23.0 release push (npm publish itself succeeded — 1.23.0 is live).
Release Binaries failure: #206 accidentally committed a package-lock.json (an npm-install artifact; the repo is pnpm-managed). bun prefers package-lock.json over pnpm-lock.yaml when both exist, and migrating the stale npm lockfile fails under --frozen-lockfile. The passing 1.22.0 run migrated from pnpm-lock.yaml; the failing 1.23.0 run from package-lock.json — same bun 1.4.0. Removed and gitignored.
Test failure: setup.ts had been formatted by prettier 3.9.6 (from that same npm node_modules) while CI pins 3.7.4 via pnpm-lock.yaml. Reformatted with the pinned 3.7.4; format:check now passes on the whole tree.
Verified locally: bun install --frozen-lockfile completes, prettier --check clean, 431/431 tests pass.
After merging: Release Binaries won't auto-trigger (its path filter watches package.json) — dispatch it once to build the 1.23.0 binaries:
gh workflow run release-binaries.yml --repo firecrawl/cli
🤖 Generated with Claude Code
Summary by cubic
Fixes CI by removing an accidental package-lock.json, adding it to .gitignore, and reformatting src/commands/setup.ts with the pinned prettier@3.7.4. bun previously preferred package-lock.json over pnpm-lock.yaml and failed --frozen-lockfile migration; now it migrates from pnpm-lock.yaml and format:check passes.
- Release Binaries will not auto-trigger for this change. Run:
gh workflow run release-binaries.yml --repo firecrawl/clito build the 1.23.0 binaries.