Deep resolve promises in objects.

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 a directory that is either local, global or in the user's home directory.

resolve which handles browser field support in package.json

Resolve a relative path against a root path with validation

resolve like require.resolve() on behalf of files asynchronously and synchronously

A wrapper for the "resolve" module that targets GLSL shaders instead of JavaScript

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

Resole and parse `tsconfig.json`, replicating to TypeScript's behaviour

Resolve a URI relative to an optional base URI

Resolve URL pathnames using JavaScript

Read a protobuf schema from the disk, parse it and resolve all imports

micromark utility to resolve subtokens

Resolve things like Node.js — ponyfill for `import.meta.resolve`

Require and resolve global modules like a boss

Resolve an absolute file path from local directories, local node_modules or global node_modules.

Webpack loader that resolves relative paths in url() statements based on the original source file

Offers a async require.resolve function. It's highly configurable.