[v2] drop support for legacy CommonJS
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13k
- Forks
- 1.4k
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 3
Description
We only need to support ES Modules these days. All major JS engines (Node, Deno, and all browsers) support native ES Modules.
To make maintenance simpler, we can simply output the source as ES modules and leave it at that.
Anyone who really needs CommonJS (f.e. they are stuck with some really old build tool for some reason) can get Rollup and compile a CommonJS bundle that they can use in their case. These days, those people are in a minority, and quickly dwindling away.
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
The issue names no files or tests. Start by locating the build configuration and current CommonJS and ES Module entry points, then assess the compatibility impact and scope. Done means the project outputs ES Modules only and the relevant build checks or consumer expectations are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, javascript, node.js
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100