mirror-rhinstaller-node-cache/is-unicode-supported
2026-10-07 13:11:38 +00:00
..
index.d.ts 8986ea02568055672e1beddb78d7e5aed90251028babf76ed1d8d56afb5edf35 package.json 2026-10-07 13:11:38 +00:00
index.js 8986ea02568055672e1beddb78d7e5aed90251028babf76ed1d8d56afb5edf35 package.json 2026-10-07 13:11:38 +00:00
license 8986ea02568055672e1beddb78d7e5aed90251028babf76ed1d8d56afb5edf35 package.json 2026-10-07 13:11:38 +00:00
package.json 8986ea02568055672e1beddb78d7e5aed90251028babf76ed1d8d56afb5edf35 package.json 2026-10-07 13:11:38 +00:00
readme.md 8986ea02568055672e1beddb78d7e5aed90251028babf76ed1d8d56afb5edf35 package.json 2026-10-07 13:11:38 +00:00

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

import isUnicodeSupported from 'is-unicode-supported';

isUnicodeSupported();
//=> true

API

isUnicodeSupported()

Returns a boolean for whether the terminal supports Unicode.