resolve
npmv1.22.12resolve like require.resolve() on behalf of files asynchronously and synchronously
Adopt with care
resolve is usable, with caveats.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 151 days ago. 6 releases in the last 2 years.
- BWeight: grade B, Good.
Pulls in 6 transitive packages, about 265 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding resolve to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Licenses in the dependency tree
Every license you inherit by installing resolve, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >= 0.4
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
resolve vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| resolvethis page | 0 | 2 | MIT | 5 months ago |
| resolve-cwd | 0 | 1 | MIT | 1 day ago |
| import-meta-resolve | 0 | 3 | MIT | 1 day ago |
| resolve-from | 0 | 8 | MIT | 1 day ago |
| esm | 6.2M | 5 | MIT | 1 day ago |
| is-core-module | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by resolve v1.22.12. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (4)
Dev (17)
Used by
Popular packages that depend on resolve.
Relationship graph
Dependencies (left) and dependents (right) of resolve.
Frequently installed together
An AST-based pattern checker for JavaScript.
A comprehensive library for mime-type mapping
Find and load configuration from a package.json property, rc file, TypeScript module, and more!
Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
BDD/TDD assertion library for node.js and the browser. Test framework agnostic.
the most correct and second fastest glob implementation in JavaScript
Generates and consumes source maps
An optimised way to copy'ing an object. A small and simple integration
Turn node's process.version into something useful.
Display differences clearly so people can review changes confidently.
Make a directory and its parents if needed - Think `mkdir -p`
Bare bones Promises/A+ implementation
Release history
6 releases in the last two years, typically about 34 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.0.0-next.7 | 3 months ago | 274 KB | MIT |
| 1.22.12latest | 5 months ago | 162 KB | MIT |
| 2.0.0-next.6 | 6 months ago | 213 KB | MIT |
| 1.22.11 | 10 months ago | 151 KB | MIT |
| 1.22.10 | 1 year ago | 142 KB | MIT |
| 1.22.9 | 1 year ago | 2.9 MB | MIT |
| 2.0.0-next.5 | 2 years ago | 135 KB | MIT |
| 1.22.8 | 2 years ago | 142 KB | MIT |
| 1.22.7 | 2 years ago | 142 KB | MIT |
| 1.22.6 | 3 years ago | 141 KB | MIT |
| 1.22.5 | 3 years ago | 141 KB | MIT |
| 1.22.4 | 3 years ago | 141 KB | MIT |
| 1.22.3 | 3 years ago | 142 KB | MIT |
| 1.22.2 | 3 years ago | 141 KB | MIT |
| 2.0.0-next.4 | 4 years ago | 134 KB | MIT |
Overview
resolve is an npm package that resolve like require.resolve() on behalf of files asynchronously and synchronously. It has 2 known dependents in the graph. The latest version is 1.22.12, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need resolve like require.resolve() on behalf of files asynchronously and synchronously and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
Cons
- Large dependency tree (21 direct dependencies) increases install size and audit surface.
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use resolve?
resolve is usable, with caveats.
How do I install resolve?
Run `npm install resolve` to add resolve to your npm project.
How many dependencies does resolve have?
resolve declares 21 direct dependencies and pulls in 6 packages in total once its runtime tree is resolved totalling about 265 KB on disk.
What license is resolve released under?
resolve is distributed under the MIT license.
How popular is resolve?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on resolve.
Is resolve still maintained?
The most recent release of resolve (v1.22.12) was published 5 months ago.
Does resolve run install scripts?
No. resolve does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.