liangjiahao
8f813121f8
添加查看按钮的窗口
|
%!s(int64=3) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| index.d.ts | %!s(int64=3) %!d(string=hai) anos | |
| index.js | %!s(int64=3) %!d(string=hai) anos | |
| license | %!s(int64=3) %!d(string=hai) anos | |
| package.json | %!s(int64=3) %!d(string=hai) anos | |
| readme.md | %!s(int64=3) %!d(string=hai) anos | |
readme.md
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
$ npm install is-unicode-supported
Usage
const isUnicodeSupported = require('is-unicode-supported');
isUnicodeSupported();
//=> true
API
isUnicodeSupported()
Returns a boolean for whether the terminal supports Unicode.
Related
- is-interactive - Check if stdout or stderr is interactive
- supports-color - Detect whether a terminal supports color
- figures - Unicode symbols with Windows fallbacks
- log-symbols - Colored symbols for various log levels