[DevTools Feature Request]: Full support for RSC server elements (component tree, props, inspect)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 251k
- Forks
- 51.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 53
Description
Website or app
All Next.js 13/14 Apps
Repro steps
RSC elements created on the server and sent over the network are not supported by React DevTools. Both _debugOwner and _debugSource are null, which breaks the component tree, props view, and the inspect feature.
According to this thread, https://twitter.com/alvarlagerlof/status/1716927277295120429, it's been considered, but no concrete plans yet.
From the official server components RFC:
How often does this bug happen?
Every time
DevTools package (automated)
No response
DevTools version (automated)
No response
Error message (automated)
No response
Error call stack (automated)
No response
Error component stack (automated)
No response
GitHub query string (automated)
No response
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 with the linked server components RFC and reproduce the issue in a Next.js 13/14 app using React DevTools. Trace how server-created RSC elements appear when _debugOwner and _debugSource are null; done means the component tree, props view, and inspect feature work for those elements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js, react
- Domain
- devtools, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100