mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-28 13:13:37 +08:00
This syncs our dependencies to the latest version. There is still a reported vulnerability in postcss, but we are luckily unaffected. However, we can't upgrade postcss yet, as stylelint requires it and can not use postcss 8 yet: https://github.com/stylelint/stylelint/issues/4942#issuecomment-823513767 Also updated manage_node_deps.py to not run the full install when running `ls`, to allow for easier inspection of our dependency graph. R=jacktfranklin@chromium.org Bug: none Change-Id: I1c9e4836fca25500e2e7277ec82b13bf2b881dca Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2887731 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
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