a special purpose fast memoizing way to resolve a node modules package.json
[](https://github.com/rigor789/resolve-package-path/actions/workflows/ci.yml)
Resolve the path of a module like `require.resolve()` but from a given path
Offers a async require.resolve function. It's highly configurable.
Resolve a directory that is either local, global or in the user's home directory.
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
A better path.resolve() that normalizes paths on Windows
resolve like require.resolve() on behalf of files asynchronously and synchronously
Resolve URL pathnames using JavaScript
resolve which handles browser field support in package.json
Import a module like with `require()` but from a given path
A minimal path module to resolve Unix, Windows and URL paths alike.
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
Node default behavior import resolution plugin for eslint-plugin-import.
Resolve the path of a globally installed module
Resolve a path by walking parent directories.
Check if your package was installed globally
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
Universal filesystem path utils
Module resolution utilities based on Node.js upstream implementation.
Resole and parse `tsconfig.json`, replicating to TypeScript's behaviour