resolve-pkg

Resolve the path of a package regardless of it having an entry point

by sindresorhus

Star on GitHub Forknpm

JavaScript

55 stars 6 forks 4 contributorsActive · 1mo agoSince 2015 v3.0.1MIT

Meet the team

See all 4 on GitHub →

sindresorhus19 contributions

BendingBender1 contribution

madjam0021 contribution

Richienb1 contribution

Languages

View on GitHub →

JavaScript96.4%

TypeScript3.6%

Commit activity

Last 12 weeks · 1 commit

Full graph →

Community health

4 of 6 standards met

Community profile →

✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template

Recent fixes

View closed PRs →

Package not being resolved by resolve-pkg but found by require.resolve() and import.metaClosedIssue

I'm working currenly in on project that uses a dep that is not being resolved correctly.

ommeirelles · 8mo ago

Doesn't work with ESM modulesClosedIssue

We found out that this doesn't work with ESM modules. Do you have a similar package that works with ESM modules?

effektsvk · 8mo ago

Does not work with package exportsClosedIssue

Given a package that has in its , like this: When trying to resolve that package, a error is thrown with Basically the assumption here that you can always resolve the of a package using node does not hold true anymore in this case. Still I'd like to be able to get the root path of that package, using node module resolution rules. 🤔

simonihmig · 8mo ago

Structured data for AI agents

Repository: sindresorhus/resolve-pkg. Description: Resolve the path of a package regardless of it having an entry point Stars: 55, Forks: 6. Primary language: JavaScript. Languages: JavaScript (96.4%), TypeScript (3.6%). License: MIT. Latest release: v3.0.1 (8mo ago). Open PRs: 0, open issues: 0. Last activity: 1mo ago. Community health: 85%. Top contributors: sindresorhus, BendingBender, madjam002, Richienb.