microsoft / microsoft/react-native-windows
RNW instances using Hermes should support direct debugging in release builds
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Summary
Today, Hermes integration in RNW uses build-time switches to exclude direct debugging features in RNW release builds. Direct debugging should work in both debug and release builds.
Motivation
Assuming RNW releases are build-flavor-paired with RNW host apps (e.g. Word, Excel), the current limitation prohibits direct debugging in release versions of RNW host apps and thus diminishes the dev experience which could be particularly relevant for service-delivered (out-of-box) packages.
Basic Example
No response
Open Questions
Direct debugging requires inclusion of Hermes inspector components which are bound to increase the size of the binary. We should measure the size increase and decide whether that's an acceptable perf hit.
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
No files, tests, or entry points are named in the issue. Start by measuring the binary-size impact of including Hermes inspector components in release builds, then determine whether the increase is acceptable and how direct debugging should work across debug and release configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100