Should use the field `exports`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 119
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
https://nodejs.org/api/packages.html#packages_subpath_exports
Should look at the `package.json` field `exports` to determine the file to import.
* https://nodejs.org/api/packages.html#package-entry-points
* https://webpack.js.org/guides/package-exports/
* https://github.com/jkrems/proposal-pkg-exports/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the Node.js package entry-points and subpath exports documentation linked in the issue, then trace how esmify currently determines which package file to import. Compare that behavior with the linked webpack guidance and proposal. Done means package.json's exports field determines the imported file correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100