TODOs in the codebase
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 89
- Avg merge
- 18h 46m
- Merged PRs (30d)
- 24
Description
TODO:
-
show more info with selected node
https://github.com/vitejs/devtools/blob/e0838a0e0e68ad9ec817437a06f8e2e234a75b5d/packages/devtools/src/app/components/flowmap/ModuleFlow.vue#L400 -
should we add filters for node_modules?
https://github.com/vitejs/devtools/blob/43fc5c576fea84614f63521bb0533e804b5b4b4e/packages/devtools/src/app/pages/session/%5Bsession%5D/graph/index.vue#L192 -
install @types/splitpanes once updated
https://github.com/vitejs/devtools/blob/0c5bdaaa3b38973dc7df8184278baff680f115db/packages/devtools/src/app/splitpanes.d.ts#L1
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
Review the linked locations in ModuleFlow.vue, graph/index.vue, splitpanes.d.ts, and ChunkDetails.vue, starting with the TODO in each file. Determine which TODOs are actionable and whether they belong together before making changes. Done means the selected TODO items have clear resolutions, with relevant checks run for any implemented changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100