Break up npm into components to reduce size and dependencies
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
Please check if your Feature Request has not been already raised in the Discussions Tab, as we would like to reduce duplicates. If it has been already raised, simply upvote it 🔼.
Is your proposal related to a problem?
(Write your answer here.)
Describe the solution you'd like
(Describe your proposed solution here.)
Describe alternatives you've considered
(Write your answer here.)
Additional context
(Write your answer here.)
Contributor guide
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, tests, or entry points are named, and the issue body contains no proposal details. Start by mapping the npm package components and their dependency relationships. Done would mean the package is split into smaller components with reduced size and dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100