Package
resolve-package
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
Key numbers
As of 25 Sept 2026
- Weekly downloads
- 357k
- +283% over 12 months
- Gzip bundle size
- -
- No Bundlephobia data
- Dependencies
- 1
- Direct, from package.json
- Last release
- 9 years ago
- v1.0.1
- GitHub stars
- 3
- 0 forks
- Open issues / PRs
- 4 / 21
- Contributors
- -
- Commits, last 52 weeks
- 0
Downloads
Last week 2026-09-15 to 2026-09-21
357,041 downloads last week, 1,649,279 in the last month. The 12-month change of +283% compares the average of the last 4 weeks with the first 4 weeks of the series.
- Releases, last 12 months
- 06 in total
- Latest version
- 1.0.1, 13 Dec 20169 years ago
- First published
- 11 Dec 2016
- Last push to GitHub
- 9 Dec 20221,385 days before the snapshot
- Repository archived
- No
- Open issues
- 4
- Open pull requests
- 21
- Commits, last 52 weeks
- 0
- Dependents on npm
- 15
Major versions
- v1 first release 1.0.0, 13 Dec 2016
- v0 first release 0.1.0, 11 Dec 2016
Recent releases
| Version | Published |
|---|---|
| 1.0.1 | 13 Dec 2016 |
| 1.0.0 | 13 Dec 2016 |
| 0.2.2 | 13 Dec 2016 |
| 0.2.1 | 13 Dec 2016 |
| 0.2.0 | 11 Dec 2016 |
| 0.1.0 | 11 Dec 2016 |
- Module format
- CommonJSFrom package.json type, main and exports fields
- TypeScript types
- None
- Node.js engine range
- >=4
- Runtimes
- -
- Unpacked size (npm)
- -
- Dependencies (1)
get-installed-path
npm install resolve-package- jsDelivr
https://cdn.jsdelivr.net/npm/resolve-package@1.0.1/ - unpkg
https://unpkg.com/resolve-package@1.0.1/ - esm.sh
https://esm.sh/resolve-package@1.0.1
Indexability: Indexed.