Resolve-from helps you find the filesystem path of a module similarly to Node.js require.resolve(), but using a specified starting directory. It throws an error when the module can’t be found (or returns undefined via resolveFrom.silent). Useful when you need deterministic module path resolution relative to a particular directory.
Project status
- The GitHub source (sindresorhus/resolve-from) appears inactive, with the last upstream push dated 2021-01-23 and no evidence of updates since then, so it is best described as dormant or in maintenance mode rather than actively maintained.
- The apparent update cadence is historical, with the most recent recorded updates in 2019 (v5.0.0), 2017 (v4.0.0), and 2017 (v3.0.0), followed by a long gap relative to today (2026-09-10).
AI summary generated
Recent updates
v5.0.0
v5.0.0 introduces a TypeScript definition and changes runtime behavior for missing modules. It also requires a newer Node.js version, and it modifies the return value when a module cannot be found.
BreakingFeaturesv4.0.0
Release v4.0.0 contains no provided release notes. The code diff shows functional changes centered on how `resolve-from` determines the base directory for module resolution, plus some repo/tooling configuration updates.
BreakingFeaturesv3.0.0
This release is v3.0.0, but the publisher did not provide any release notes describing changes. As a result, developers should assume the upgrade may include breaking or behavior changes and review the code diff and changelog history before upgrading.