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
..
.travis.yml	Implemented a working Language Server Protocol (LSP) for IFC files with:	2025-12-07 10:20:07 -06:00
.zuul.yml	Implemented a working Language Server Protocol (LSP) for IFC files with:	2025-12-07 10:20:07 -06:00
browser.js	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
test.js	Implemented a working Language Server Protocol (LSP) for IFC files with:	2025-12-07 10:20:07 -06:00

README.md

randombytes

randombytes from node that works in the browser. In node you just get crypto.randomBytes, but in the browser it uses .crypto/msCrypto.getRandomValues

var randomBytes = require('randombytes');
randomBytes(16);//get 16 random bytes
randomBytes(16, function (err, resp) {
  // resp is 16 random bytes
});