Resolve the path of a module through a sequence of packages
Resolve the path of a module like `require.resolve()` but from a given path
Resolve the path of a module like `require.resolve()` but from the current working directory
resolve which handles browser field support in package.json
Resolve a directory that is either local, global or in the user's home directory.
Resolve URL pathnames using JavaScript
Read a protobuf schema from the disk, parse it and resolve all imports
Resolve a relative path against a root path with validation
CSS color - Resolve and convert CSS colors.
Resolves a given package if it is installed locally, then tries to resolve it from global registry, using battle-tested [global-modules][] package. Better approach than internal `require.resolve`, so you can trust. You just get absolute filepath to some p
resolve like require.resolve() on behalf of files asynchronously and synchronously
A wrapper for the "resolve" module that targets GLSL shaders instead of JavaScript
Resolve a URI relative to an optional base URI
Offers a async require.resolve function. It's highly configurable.
TypeScript definitions for resolve
Resolve package.json exports & imports maps
Missing ECMAScript module utils for Node.js
Import a module like with `require()` but from a given path
Resole and parse `tsconfig.json`, replicating to TypeScript's behaviour
Module resolution utilities based on Node.js upstream implementation.
Resolve things like Node.js — ponyfill for `import.meta.resolve`
Resolve the path of a globally installed module
Resolve an absolute file path from local directories, local node_modules or global node_modules.
Locate and bundle third-party dependencies in node_modules