sindresorhus

is-unicode-supported

export default function isUnicodeSupported() {

		return process.env.TERM !== 'linux'; // Linux console (kernel)

		Boolean(process.env.WT_SESSION) || // Windows Terminal

		process.env.ConEmuTask === '{cmd::Cmder}' || // ConEmu and cmder

		process.env.TERM_PROGRAM === 'vscode' ||

		process.env.TERM === 'xterm-256color' ||

		|| Boolean(process.env.WT_SESSION) // Windows Terminal

		|| process.env.ConEmuTask === '{cmd::Cmder}' // ConEmu and cmder

		|| process.env.TERM_PROGRAM === 'vscode'

		|| process.env.TERM === 'xterm-256color'

		|| process.env.TERMINAL_EMULATOR === 'JetBrains-JediTerm';

	"description": "Detect whether the terminal supports Unicode",

	"repository": "sindresorhus/is-unicode-supported",

	"funding": "https://github.com/sponsors/sindresorhus",

> 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.

import isUnicodeSupported from 'is-unicode-supported';

Returns a `boolean` for whether the terminal supports Unicode.

- [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

		{
		"name": "is-unicode-supported",
		"version": "1.1.0",
		"version": "1.2.0",
		"description": "Detect whether the terminal supports Unicode",
		@@ -39,6 +39,6 @@ "license": "MIT",
		"devDependencies": {
		"ava": "^3.15.0",
		"tsd": "^0.14.0",
		"xo": "^0.38.2"
		"ava": "^4.0.1",
		"tsd": "^0.19.1",
		"xo": "^0.47.0"
		}
		}

		@@ -11,5 +11,5 @@ # is-unicode-supported

		```sh
		npm install is-unicode-supported
		```
		$ npm install is-unicode-supported
		```

		@@ -16,0 +16,0 @@ ## Usage

New alerts

Improved metrics

Worsened metrics

		@@ -0,1 +1,3 @@
		import process from 'node:process';

		export default function isUnicodeSupported() {
		@@ -6,8 +8,9 @@ if (process.platform !== 'win32') {

		return Boolean(process.env.CI) \|\|
		Boolean(process.env.WT_SESSION) \|\| // Windows Terminal
		process.env.ConEmuTask === '{cmd::Cmder}' \|\| // ConEmu and cmder
		process.env.TERM_PROGRAM === 'vscode' \|\|
		process.env.TERM === 'xterm-256color' \|\|
		process.env.TERM === 'alacritty';
		return Boolean(process.env.CI)
		\|\| Boolean(process.env.WT_SESSION) // Windows Terminal
		\|\| process.env.ConEmuTask === '{cmd::Cmder}' // ConEmu and cmder
		\|\| process.env.TERM_PROGRAM === 'vscode'
		\|\| process.env.TERM === 'xterm-256color'
		\|\| process.env.TERM === 'alacritty'
		\|\| process.env.TERMINAL_EMULATOR === 'JetBrains-JediTerm';
		}