From 6555fb80fdd8f6a5d201efadec3189d1244830a0 Mon Sep 17 00:00:00 2001 From: Nevena Bojovic Date: Tue, 1 Mar 2022 22:05:25 +0100 Subject: Izbrisala bin, obj i node-modules. --- .../node_modules/is-unicode-supported/readme.md | 35 ---------------------- 1 file changed, 35 deletions(-) delete mode 100644 sandbox/testAppNevena/Front/node_modules/is-unicode-supported/readme.md (limited to 'sandbox/testAppNevena/Front/node_modules/is-unicode-supported/readme.md') diff --git a/sandbox/testAppNevena/Front/node_modules/is-unicode-supported/readme.md b/sandbox/testAppNevena/Front/node_modules/is-unicode-supported/readme.md deleted file mode 100644 index a82e34d4..00000000 --- a/sandbox/testAppNevena/Front/node_modules/is-unicode-supported/readme.md +++ /dev/null @@ -1,35 +0,0 @@ -# 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 - -```js -const isUnicodeSupported = require('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 -- cgit v1.2.3