Skip to content

fix: avoid mojibake in Windows terminal status output#174

Open
Bortlesboat wants to merge 1 commit into
colbymchenry:mainfrom
Bortlesboat:fix/windows-safe-cli-status-markers
Open

fix: avoid mojibake in Windows terminal status output#174
Bortlesboat wants to merge 1 commit into
colbymchenry:mainfrom
Bortlesboat:fix/windows-safe-cli-status-markers

Conversation

@Bortlesboat
Copy link
Copy Markdown

Summary

  • replace unicode status glyphs with ASCII markers ([OK], [ERR], [INFO], [WARN]) in shared CLI helpers
  • replace em dash in verbose progress output with ASCII - for safer rendering across terminals
  • keep behavior unchanged except output formatting

Why

Issue #168 reports garbled output on Windows PowerShell. This keeps status text readable in non-UTF terminal paths and log collectors.

Validation

pm ci`n-
pm test (existing upstream failures in installer-target tests + Node OOM; unrelated to this formatting-only change)

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