sidequestjs / sidequestjs/sidequest
Singular export bloats sidequest dependencies
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 25
- Avg merge
- 12h 17m
- Merged PRs (30d)
- 5
Description
Exporting everything as a singular sidequest dependency has quite a big impact on dependencies. Have you considered not bundling everything together? The dashboard for example, seems quite optional?
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
Trace the singular sidequest export and inspect how it pulls in the optional dashboard and other dependencies. The work is complete when the dashboard is no longer bundled by that dependency and the resulting dependency footprint is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100