Skip to content

fix(cli): ASCII fallback for emoji/box-drawing when NO_COLOR is set#45

Open
sharma2464 wants to merge 2 commits into
nitrocloudofficial:mainfrom
sharma2464:fix/cli-no-color-ascii-fallback
Open

fix(cli): ASCII fallback for emoji/box-drawing when NO_COLOR is set#45
sharma2464 wants to merge 2 commits into
nitrocloudofficial:mainfrom
sharma2464:fix/cli-no-color-ascii-fallback

Conversation

@sharma2464

Copy link
Copy Markdown

Summary

  • Adds ASCII fallback for box-drawing chars and emoji/icons in CLI output when NO_COLOR env var is set
  • Wires fallback through branding.ts (icons, box chars, banner) and into dev.ts, init.ts, start.ts

Test plan

  • tsc --noEmit clean
  • npm run build succeeds
  • Ran built CLI output with/without NO_COLOR=1, confirmed icons/banners/boxes switch to plain ASCII and stay aligned

Fixes #25

🤖 Generated with Claude Code

Terminals without unicode/emoji support render garbled CLI output.
Add icons/BOX char maps in branding.ts gated on NO_COLOR env var,
wire through dev/init/start commands.

Fixes nitrocloudofficial#25
ora's succeed/fail/info/warn always prepend their own unicode symbol
regardless of NO_COLOR, so prefixing icons.ok etc as text produced
duplicate symbols (e.g. "✔ [ok] done"). Use stopAndPersist with an
explicit symbol instead so only one symbol renders, ASCII or unicode.
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.

[CLI] Emoji in success messages vs NO_COLOR / weak terminals (discussion)

1 participant