Implements the Node.js `require.resolve()` algorithm, letting you resolve a module specifier to the corresponding file path asynchronously or synchronously. It is useful when you need to determine where a module would resolve from a given `basedir`, including handling package `main` fields and `exports`-based resolution.
Project status
- Actively maintained, with the latest upstream push on 2026-05-15 and a new published update on 2026-05-15 (v2.0.0-next.7), followed by earlier updates in 2026.
- Update cadence appears active in 2026, roughly every 1 to 2 months (2026-02-16, 2026-04-11, 2026-05-15), suggesting an evolving development track rather than a long quiet period.
AI summary generated
Recent updates
v2.0.0-next.7
Release v2.0.0-next.7 has no publisher release notes provided. The diff indicates new TypeScript declaration entry points and new runtime behavior around resolving package exports using a moduleSystem option (require vs import), plus several error-handling and environment-homedir edge-case fixes.
Featuresv1.22.12
Release v1.22.12 has no publisher release notes. The code diff shows primarily internal refactors plus behavior fixes around error construction (switching to es-errors), Windows homedir fallback logic, and preventing callback re-entry in package loading. It also adds a new runtime dependency on es-errors.
Breakingv2.0.0-next.6
Release v2.0.0-next.6 contains no publisher-provided release notes. The code diff shows a major internal change: new exports-resolution logic (including condition handling and exports-category selection) was added along with extensive new tests.
Featuresv1.22.11
v1.22.11 includes internal refactors to the path-resolution logic, plus updates to Node core module metadata and dependency versions. The release notes were not provided, so the practical impact must be inferred from the code diff.
SecurityFeaturesv1.22.10
This release (v1.22.10) only changes package metadata in package.json, with no application code changes shown in the diff. The update bumps the package version, adjusts the npm ignore list to exclude an additional test file, and adds an engines field for Node.js compatibility.
Breakingv1.22.9
Release v1.22.9 contains only small metadata, dependency, and CI-related changes. There were no release notes provided, so the practical impact must be inferred from the code diff.
SecurityFeaturesv2.0.0-next.5
This release is version v2.0.0-next.5, but no release notes were provided by the publisher. As a result, there is insufficient information to identify new features, breaking changes, bug fixes, security updates, or other upgrade-impacting modifications from the release notes alone.
v1.22.8
Release v1.22.8 (notes not provided by the publisher) includes a package version bump and changes limited to lint/test infrastructure. The only behavioral adjustment visible in the diff is in test logic to avoid assertions on specific Node.js versions where default `require.resolve` paths are known to be broken.
v1.22.7
Release v1.22.7 contains no documented release notes (none provided). The diff shows only package metadata and test/publish housekeeping changes, with a small dev dependency bump for the test runner.
v1.22.6
Release v1.22.6 was published on 2023-09-15, but no release notes were provided. Without documented changes, developers should not assume compatibility fixes or new features and should verify the upgrade by reviewing the tag diff/changelog in the repository.
v2.0.0-next.4
Release v2.0.0-next.4 (published 2022-06-18) includes substantial changes to how module resolution determines default search paths, plus updates to error handling for malformed package.json files. It also adds new entry points and a CLI executable, and expands the package exports map. No release notes were provided by the publisher, so the behavior changes below are effectively undocumented.
BreakingFeaturesv2.0.0-next.3
Release v2.0.0-next.3 makes substantial changes to the module resolution logic in both the async and sync resolvers, mainly around how package.json is read and how core modules are treated. It also adds new option hooks for custom package.json parsing and introduces a standardized error code (INCORRECT_PACKAGE_MAIN) for invalid or non-resolvable package.json main entries.
Featuresv2.0.0-next.2
v2.0.0-next.2 (release notes not provided) makes internal resolver changes around symlink realpath handling and core module detection. It also removes the previously exported core module metadata and isCore helpers, while keeping core module resolution working internally.
Featuresv2.0.0-next.1
No release notes were provided for v2.0.0-next.1. The code diff shows several public surface changes, including a new resolution hook option (opts.packageIterator), addition of an ESM entrypoint (index.mjs) plus a package.json exports map, and updated module-resolution iteration logic.
BreakingFeaturesv2.0.0-next.0
This release (v2.0.0-next.0) does not include any publisher-provided release notes, so there is no documented information about new features, bug fixes, or breaking changes. Developers should not assume behavioral stability and may need to inspect the changelog, commits, or diff against the prior version to identify upgrade risks.