- 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." |
||
|---|---|---|
| .. | ||
| index.js | ||
| license | ||
| package.json | ||
| readme.md | ||
resolve-from 
Resolve the path of a module like
require.resolve()but from a given path
Install
$ npm install resolve-from
Usage
const resolveFrom = require('resolve-from');
// There is a file at `./foo/bar.js`
resolveFrom('foo', './bar');
//=> '/Users/sindresorhus/dev/test/foo/bar.js'
API
resolveFrom(fromDir, moduleId)
Like require(), throws when the module can't be found.
resolveFrom.silent(fromDir, moduleId)
Returns null instead of throwing when the module can't be found.
fromDir
Type: string
Directory to resolve from.
moduleId
Type: string
What you would use in require().
Tip
Create a partial using a bound function if you want to resolve from the same fromDir multiple times:
const resolveFromFoo = resolveFrom.bind(null, 'foo');
resolveFromFoo('./bar');
resolveFromFoo('./baz');
Related
- resolve-cwd - Resolve the path of a module from the current working directory
- import-from - Import a module from a given path
- import-cwd - Import a module from the current working directory
- resolve-pkg - Resolve the path of a package regardless of it having an entry point
- import-lazy - Import a module lazily
- resolve-global - Resolve the path of a globally installed module
License
MIT © Sindre Sorhus