Permalink
Cannot retrieve contributors at this time
35 lines (22 sloc)
1.1 KB
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
codeql-action/node_modules/is-unicode-supported/readme.md
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# 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 |