list-exports
Given a package name and a version number, or a path to a package.json, what specifiers does it expose?
by ljharbJavaScript
Commit activity
Last 12 weeks · 4 commits
Community health
4 of 6 standards met
Recent PRs & issues
### What Updated index.js to follow Node’s subpath export rules: Only the first is treated as a wildcard. Mismatched or extra stars are treated as literal or not exported. RHS patterns expanded with fast-glob@3.2.11. Flattened star-handling logic to satisfy ESLint rules. Added tests in ex-stars-basic.test.js: hooks/useA resolves multi, mismatch not exported rhs-extra → MODULE_NOT_FOUND literal/ resolves as literal file Added fixture + expected snapshots in tests/fixtures/ex-stars-basic. ### Why Node only supports the first in subpath patterns. Our tool previously treated later stars incorrectly. Using ensures RHS patterns like expand to real files instead of being treated as a literal filename. Added tests provide clear parity with Node’s actual resolution behavior. ### Verification Confirmed with Node in a sandbox: outcomes ( vs ) match Node behavior. All tests (, ) and lint pass locally.
Summary Improved and updated the README.md with: Clear installation instructions CLI usage example Running tests guide Contributing guide Cleaner formatting with all original information preserved Fixed linting errors by adjusting the ESLint configuration and running --fix Resolved test syntax errors and ensured tests pass locally Verified code style compliance with Prettier and ESLint Changes ✅ Updated ✅ Fixed to be CommonJS compatible and cleaned up ✅ Fixed lint script in to avoid missing path errors () ✅ Ran tests and verified they pass with Node.js
It would be great if we could have a better README explaining the purpose and usefulness of the project. It would also be nice to have some common commands explained/showcased, such as running tests And a contributing to guide with things to know for future contributors!
Recent fixes
Running ls-exports against my react-utils package, it's telling me it can't resolve any of the subpath exports I've defined. Example: https://github.com/Twipped/react-utils/blob/1d81497bd08b9b7450ac66880f6c3f2e58b8b6a3/package.json#L50 Am I defining these wrong, or is this a bug?
As shown by #40 , there are some outdated dependencies. The versions of those dependencies should be updated and test ran to make sure nothing broke I suggest updating as many dependencies as possible in one PR (skip the ones that may be breaking code). Keep in mind that it may not be as easy to just update versions in package.json. Some dependencies need code changed as well
Update eslint from 8.8.0 to 8.57.1 across all packages Update @npmcli/arborist from ^7.5.4 to ^9.1.2 Update npm-packlist from ^8.0.2 to ^10.0.0 Update semver from ^7.6.3 to ^7.7.2 in list-exports Update semver from ^6.3.1 to ^7.7.2 in tests Update npm-package-arg from ^11.0.3 to ^12.0.2 Update pacote from ^18.0.6 to ^21.0.0 in ls-exports Update pacote from ^17.0.7 to ^21.0.0 in tests Update strip-ansi from ^6.0.1 to ^7.1.0 Update yargs from ^17.7.2 to ^18.0.0 Update jackspeak from =2.1.1 to =4.1.1 Update resolve from ^2.0.0-next.4 to ^1.22.10 All tests continue to pass with updated dependencies.
Repository: ljharb/list-exports. Description: Given a package name and a version number, or a path to a package.json, what specifiers does it expose? Stars: 14, Forks: 6. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Open PRs: 2, open issues: 2. Last activity: 2mo ago. Community health: 85%. Top contributors: ljharb, bgotink, renovate-bot.