OpeningDesign/ifc-language-server
8
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ifc-language-server/client/node_modules/is-fullwidth-code-point
History
Exact
Ryan Schultz 8afacf268a Implemented a working Language Server Protocol (LSP) for IFC files with: 
- 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."
2025-12-07 10:20:07 -06:00
..
index.d.ts Implemented a working Language Server Protocol (LSP) for IFC files with: 2025-12-07 10:20:07 -06:00
index.js Implemented a working Language Server Protocol (LSP) for IFC files with: 2025-12-07 10:20:07 -06:00
license Implemented a working Language Server Protocol (LSP) for IFC files with: 2025-12-07 10:20:07 -06:00
package.json Implemented a working Language Server Protocol (LSP) for IFC files with: 2025-12-07 10:20:07 -06:00
readme.md Implemented a working Language Server Protocol (LSP) for IFC files with: 2025-12-07 10:20:07 -06:00

readme.md

is-fullwidth-code-point Build Status

Check if the character represented by a given Unicode code point is fullwidth

Install

$ npm install is-fullwidth-code-point

Usage

const isFullwidthCodePoint = require('is-fullwidth-code-point');

isFullwidthCodePoint('谢'.codePointAt(0));
//=> true

isFullwidthCodePoint('a'.codePointAt(0));
//=> false

API

isFullwidthCodePoint(codePoint)

codePoint

Type: number

The code point of a character.

License

MIT © Sindre Sorhus