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
..
globals.json	Implemented a working Language Server Protocol (LSP) for IFC files with:	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

globals

Global identifiers from different JavaScript environments

It's just a JSON file, so use it in any environment.

This package is used by ESLint.

This package no longer accepts new environments. If you need it for ESLint, just create a plugin.

Install

npm install globals

Usage

const globals = require('globals');

console.log(globals.browser);
/*
{
	addEventListener: false,
	applicationCache: false,
	ArrayBuffer: false,
	atob: false,
	…
}
*/

Each global is given a value of true or false. A value of true indicates that the variable may be overwritten. A value of false indicates that the variable should be considered read-only. This information is used by static analysis tools to flag incorrect behavior. We assume all variables should be false unless we hear otherwise.

For Node.js this package provides two sets of globals:

globals.nodeBuiltin: Globals available to all code running in Node.js. These will usually be available as properties on the global object and include process, Buffer, but not CommonJS arguments like require. See: https://nodejs.org/api/globals.html
globals.node: A combination of the globals from nodeBuiltin plus all CommonJS arguments ("CommonJS module scope"). See: https://nodejs.org/api/modules.html#modules_the_module_scope

When analyzing code that is known to run outside of a CommonJS wrapper, for example, JavaScript modules, nodeBuiltin can find accidental CommonJS references.