mirror of https://github.com/facebook/react-native.git synced 2025-11-01 09:14:26 +00:00

Files

T

History

generatedunixname1395667395051502 5735bb5955 Update React Native DevTools binaries

Summary:
Automated update of React Native DevTools binaries
bypass-github-export-checks
Changelog: [Internal]

Reviewed By: motiz88

Differential Revision: D83233752

fbshipit-source-id: 4f87b05e552d728314d3c7be1d28267d58b8f19c

2025-09-25 06:17:47 -07:00

__tests__

Demote electron to devDependency (#53438 )

2025-08-27 02:50:05 -07:00

bin

Update React Native DevTools binaries

2025-09-25 06:17:47 -07:00

src

Fix custom prebuilt binary handling in unstable_prepareDebuggerShell (#53927 )

2025-09-25 02:29:11 -07:00

package.json

Backout D82236159: [RN][debugger-shell] Implement saved window positioning per target (#53816 )

2025-09-19 02:38:00 -07:00

README.md

…

README.md

@react-native/debugger-shell

Experimental Electron-based shell for React Native DevTools. This package is not part of React Native's public API.

Why Electron?

The React Native DevTools frontend is based on Chrome DevTools, which is a web app, but is not particularly portable: it's designed to run in Chromium, and Chromium only. Prior to @react-native/debugger-shell, we would run it in hosted mode in an instance of Chrome or Edge.

Relying on hosted mode presents a variety of UX issues in the debugging workflow, such as the need to ask developers to install a particular browser before they can debug in React Native, and the inability to foreground/reuse existing debugger windows when relaunching the debugger for the same app. In order to address these issues effectively, we fundamentally need to leave the browser sandbox and run the debugger in a shell we can bundle with React Native, and whose behavior we can control.

Electron is a tried-and-tested framework for the specific task of embedding a Chromium browser in a portable, customized shell. As a rule we'll hold a high bar for performance and reliability, and we'll only add features to the shell if they are strictly necessary to complement the DevTools frontend's built-in capabilities.