microsoft / microsoft/react-native-windows
Implement captureStackTrace
Open
Nobody has claimed this yet.
Area: Debug Infrastructure
Area: JavaScript Engine
enhancement
Integration Follow-up
Workstream: Developer Experience
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Summary
#13255 brings in this change from upstream: https://github.com/facebook/react-native/commit/4fbc1f2ef8bef00d6577e44fbbe505dca3eba691
Currently, the overrides return an empty StackTrace.
Motivation
It would improve the debugging story.
Basic Example
No response
Open Questions
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 by reading upstream commit 4fbc1f2ef8bef00d6577e44fbbe505dca3eba691 and locating the Windows overrides that currently return an empty StackTrace. Determine the relevant implementation and test entry points from that comparison. Done means captureStackTrace produces useful stack traces and the debugging behavior is covered by the available tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100