Files
zCode-CLI-X/~/.npm-cache/is-unicode-supported@2.1.0@@@1/readme.md
admin 875c7f9b91 feat: Complete zCode CLI X with Telegram bot integration
- Add full Telegram bot functionality with Z.AI API integration
- Implement 4 tools: Bash, FileEdit, WebSearch, Git
- Add 3 agents: Code Reviewer, Architect, DevOps Engineer
- Add 6 skills for common coding tasks
- Add systemd service file for 24/7 operation
- Add nginx configuration for HTTPS webhook
- Add comprehensive documentation
- Implement WebSocket server for real-time updates
- Add logging system with Winston
- Add environment validation

🤖 zCode CLI X - Agentic coder with Z.AI + Telegram integration
2026-05-05 09:01:26 +00:00

36 lines
1.1 KiB
Markdown

# is-unicode-supported
> Detect whether the terminal supports Unicode
This can be useful to decide whether to use Unicode characters or fallback ASCII characters in command-line output.
Note that the check is quite naive. It just assumes all non-Windows terminals support Unicode and hard-codes which Windows terminals that do support Unicode. However, I have been using this logic in some popular packages for years without problems.
## Install
```sh
npm install is-unicode-supported
```
## Usage
```js
import isUnicodeSupported from 'is-unicode-supported';
isUnicodeSupported();
//=> true
```
## API
### isUnicodeSupported()
Returns a `boolean` for whether the terminal supports Unicode.
## Related
- [is-interactive](https://github.com/sindresorhus/is-interactive) - Check if stdout or stderr is interactive
- [supports-color](https://github.com/chalk/supports-color) - Detect whether a terminal supports color
- [figures](https://github.com/sindresorhus/figures) - Unicode symbols with Windows fallbacks
- [log-symbols](https://github.com/sindresorhus/log-symbols) - Colored symbols for various log levels