Feature Request: Allow choosing to prefer esm entry or cjs entry
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 6
- Avg merge
- 4h 25m
- Merged PRs (30d)
- 6
Description
es module makes sense.
I'd prefer to:
- add an
entryoption to allow users to specify the entry point; or - add a
preferCondition: "import" | "require"option and useenhanced-resolveto resolve the entry.
Once we add a resolver library to the codebase, we can also use it to resolve the type declaration file more reliably.
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
No files or tests are named. Start by tracing how the package currently chooses between ESM and CJS entries and how it resolves type declaration files, then compare the proposed entry and preferCondition interfaces. Done requires a decided option design and reliable entry and declaration resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100