A better path.resolve() that normalizes paths on Windows
Offers a async require.resolve function. It's highly configurable.
Resolve the path of a module like `require.resolve()` but from a given path
Node's path builtin module exposed as dual ESM/CJS and browser-compatible out of the box.
JSON.parse with context information on error
Resolve a directory that is either local, global or in the user's home directory.
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 the path of a module like `require.resolve()` but from the current working directory
Convert a dependency path into a filepath
Resolve a relative path against a root path with validation
resolve which handles browser field support in package.json
Import a module like with `require()` but from a given path
Resolve URL pathnames using JavaScript
Resolve the path of a globally installed module
a special purpose fast memoizing way to resolve a node modules package.json
resolve like require.resolve() on behalf of files asynchronously and synchronously
Resolve the path of a package regardless of it having an entry point
Read a protobuf schema from the disk, parse it and resolve all imports
Resolve a path by walking parent directories.
A minimal path module to resolve Unix, Windows and URL paths alike.
Fast and almost Gaussian blur by Mario Klingemann
A wrapper for the "resolve" module that targets GLSL shaders instead of JavaScript
Module resolution utilities based on Node.js upstream implementation.
Resole and parse `tsconfig.json`, replicating to TypeScript's behaviour