Skip to content

fix: Normalize inquirer signal-exit compatibility on Windows#645

Open
arjankowski wants to merge 1 commit intomainfrom
SDK-5758
Open

fix: Normalize inquirer signal-exit compatibility on Windows#645
arjankowski wants to merge 1 commit intomainfrom
SDK-5758

Conversation

@arjankowski
Copy link
Contributor

This PR fixes a Windows packaging issue where inquirer could crash with signalExit is not a function during oclif pack:win because restore-cursor may resolve to signal-exit@4 (object export) instead of the older function-style export.

I've added a small compatibility shim in src/inquirer.js that wraps object-style signal-exit into a callable function before loading inquirer, and we updated test/inquirer.test.js to cover both behaviors (wrap object export, keep function export unchanged). I've also added signal-exit as an explicit dev dependency to keep test imports clear and lint-safe.

This started appearing in v4.5.0 after dependency changes.

@arjankowski arjankowski requested a review from a team March 13, 2026 18:32
@arjankowski arjankowski changed the title fix: normalize inquirer signal-exit compatibility on Windows fix: Normalize inquirer signal-exit compatibility on Windows Mar 13, 2026
@coveralls
Copy link

Pull Request Test Coverage Report for Build 23065163996

Details

  • 23 of 27 (85.19%) changed or added relevant lines in 13 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.02%) to 84.083%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/commands/ai/ask.js 0 1 0.0%
src/commands/ai/extract-structured.js 0 1 0.0%
src/commands/ai/extract.js 0 1 0.0%
src/commands/files/upload.js 5 6 83.33%
Totals Coverage Status
Change from base Build 23046684263: 0.02%
Covered Lines: 4912
Relevant Lines: 5593

💛 - Coveralls

Copy link
Collaborator

@Pask423 Pask423 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make seans IMHO 👍

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.

3 participants