Skip to content

Fix cross-target bundled CLI startup - #2379

Merged
chubes4 merged 1 commit into
mainfrom
fix/1250-portable-bundled-cli
Aug 25, 2026
Merged

Fix cross-target bundled CLI startup#2379
chubes4 merged 1 commit into
mainfrom
fix/1250-portable-bundled-cli

Conversation

@chubes4

@chubes4 chubes4 commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • defer loading Sharp until visual comparison actually normalizes animated media
  • prove extracted release CLIs can run --version and commands with native Sharp packages unavailable
  • canonicalize provenance source paths so macOS /var and /private/var aliases hash identically

Refs #1250.

Testing

Passed:

  • npm run build
  • npm run test:cli-build-freshness
  • npm run test:release-target
  • npm run test:sharp-release-runtime
  • npm run test:prepare-declaration-rebuild
  • npm run test:release-package-coverage (initial complete run)

The full package smoke reaches an unrelated existing failure in native-mariadb-runtime-service.test.ts: the loopback collision fixture allocates once instead of twice (1 !== 2). A repeated 430+ MB release-package run later timed out after the initial successful run.

AI Assistance

OpenAI gpt-5.6-sol through OpenCode reproduced the packaged CLI failure, implemented the lazy native dependency boundary and macOS provenance normalization, and ran the listed verification. Chris Huber reviewed and remains responsible for the change.

@chubes4
chubes4 merged commit a60ba4b into main Aug 25, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant