- Hover provider showing entity information and type - Go-to-definition (F12) for entity references - Basic IFC file validation (ISO-10303-21 header check) - Entity parsing with regex-based detection - Proper CommonJS module system (avoiding ES module issues) This replaces the broken baseline from ifc-developer-tools which had: - Non-functional ES module configuration - Circular dependency issues - Parser crashes - Non-working PositionVisitor Built on Microsoft's LSP example template for a clean, maintainable foundation. Next: Add hierarchical entity dependency tree in hover tooltip." |
||
|---|---|---|
| .. | ||
| index.d.ts | ||
| index.js | ||
| license | ||
| package.json | ||
| readme.md | ||
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