payload size warning and breakdown
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.3k
- Forks
- 214
- Avg merge
- 13h 22m
- Merged PRs (30d)
- 18
Description
when payloads are (or will be) big would be nice to highlight this in devtools and show a breakdown of where that data is coming from
also, with regard to nuxt data, we should show origin (client/server) rather than just locating it in the payload
cc: @vladh
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
Start by finding the existing devtools payload view and its Nuxt data display. Trace how payload entries are currently located, then clarify the size warning, source breakdown, and client/server origin requested in the issue. Done means these details are visible together in devtools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100