cli: fix missing binary exit code#1130
Merged
kodiakhq[bot] merged 2 commits intoMay 12, 2026
Merged
Conversation
👷 Deploy request for squawkhq pending review.Visit the deploys page to approve it
|
sbdchd
added
automerge
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exit 1 when the npm wrapper fails to spawn the Squawk binary.
This can happen when
squawk-cliis installed without running itspostinstallscript, sojs/install.jsnever downloadsjs/binaries/squawk. For example, pnpm 10 requires dependency build scripts to be approved, Yarn 4.14+ disables third-party postinstalls by default, and npm supports--ignore-scripts.Tested:
node --check js/bin/squawknode js/bin/squawk --versionexits 1node js/bin/squawk --versionexits 0