Ryan Schultz
8afacf268a
- 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."
28 lines
1 KiB
JavaScript
28 lines
1 KiB
JavaScript
/**
|
|
* Utility for resolving a module relative to another module
|
|
* @author Teddy Katz
|
|
*/
|
|
|
|
"use strict";
|
|
|
|
const Module = require("node:module");
|
|
|
|
/*
|
|
* `Module.createRequire` is added in v12.2.0. It supports URL as well.
|
|
* We only support the case where the argument is a filepath, not a URL.
|
|
*/
|
|
const createRequire = Module.createRequire;
|
|
|
|
/**
|
|
* Resolves a Node module relative to another module
|
|
* @param {string} moduleName The name of a Node module, or a path to a Node module.
|
|
* @param {string} relativeToPath An absolute path indicating the module that `moduleName` should be resolved relative to. This must be
|
|
* a file rather than a directory, but the file need not actually exist.
|
|
* @returns {string} The absolute path that would result from calling `require.resolve(moduleName)` in a file located at `relativeToPath`
|
|
* @throws {Error} When the module cannot be resolved.
|
|
*/
|
|
function resolve(moduleName, relativeToPath) {
|
|
return createRequire(relativeToPath).resolve(moduleName);
|
|
}
|
|
|
|
exports.resolve = resolve;
|