Feature Request: Allow choosing to prefer esm entry or cjs entry

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, nodejs

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.

Description

es module makes sense.

I'd prefer to:

  • add an entry option to allow users to specify the entry point; or
  • add a preferCondition: "import" | "require" option and use enhanced-resolve to 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.

Dominant language
JavaScript
Stars
28
Forks
6
Avg merge
4h 25m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rstackjs/prebundle

All issues in rstackjs/prebundle

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.