feat(rolldown): visualize output generation hooks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- devtools
Research direction
Start by tracing how the module graph tab displays transform hooks and how chunks are represented in the chunks tab. Read the output-generation hooks context, especially renderChunk, and follow the existing build flow page entry point. Done means each chunk can expose its output-generation transformations in the same way module transforms are visualized.
Written by the indexing model from the issue text.
Description
Clear and concise description of the problem
In the module graph tab, I can see the transforms happened by the transform hook for each modules. But for the transforms happened against the chunks by output generation hooks like renderChunk is not visualized. It would be nice if that is shown as well.
Suggested solution
Add the build flow page to each chunk in chunks tab like the module graph tab.
Alternative
No response
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 89
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 21
Getting set up
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.
More from vitejs/devtools
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vitejs/devtools#589 · 1 comment ·
Maintainers usually reply within 1 day
-
Rolldown "Run build with devtools" produces a development build (inherits the dev server's NODE_ENV)Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vitejs/devtools#261 · 1 comment ·
Maintainers usually reply within 1 day
-
feat(oxc): add rule timing stats to the lint inspectorPossibly taken @yuyinws claimed this 6 days ago. Openenhancement
vitejs/devtools#584 · 1 assignee ·
Maintainers usually reply within 1 day
-
pending triage
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
diegosouzapw/OmniRoute#14869 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
Maintainers usually reply within 1 day
-
status: waiting triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
freeCodeCamp/freeCodeCamp#70412 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability untriaged
Difficulty 1/5 Under an hour Newbie friendliness 88/100
opensearch-project/OpenSearch-Dashboards#12816 ·
Maintainers usually reply within 1 day