Bug: React logComponentRender breaks existing functionalities that utilise proxy (trpc client)
facebook/react 3 comments 1mo ago
mediumopenScope: somewhat clearSkill match: maybeReactJavaScriptTypeScript
Why this is a good first issue
Issue involves React's interaction with a third-party library (tRPC) and proxy functionality.
AI Summary
The issue describes a break in functionality when React's logComponentRender interacts with a tRPC client using proxy. The problem might be related to React's handling of proxy objects or tRPC's implementation. The maintainer has asked for more details and suggested checking the experimental version, indicating uncertainty about the root cause.
Issue Description
client[procedureType] is not a function
React version: 19.2.3
The current behavior
When trying to read properties of the object to show the diff in log, it breaks it.
The expected behavior
Should work.
I am not sure if this is to be fixed on React side or TRPC, but it worked in previous versions of React.
GitHub Labels
Status: Unconfirmed
Want to work on this?
Claim this issue to let others know you're working on it. You'll earn 10 points when you complete it!
Risk Flags
- proxy-related
- third-party integration
Loading labels...
Details
Points10 pts
Difficultymedium
Scopesomewhat clear
Skill Matchmaybe
Test Focusedno