History

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

escape-string-regexp

Escape RegExp special characters

Install

$ npm install escape-string-regexp

Usage

const escapeStringRegexp = require('escape-string-regexp');

const escapedString = escapeStringRegexp('How much $ for a 🦄?');
//=> 'How much \\$ for a 🦄\\?'

new RegExp(escapedString);

You can also use this to escape a string that is inserted into the middle of a regex, for example, into a character class.

Get professional support for this package with a Tidelift subscription
_{Tidelift helps make open source sustainable for maintainers while giving companies
assurances about security, maintenance, and licensing for their dependencies.}