mirror of https://github.com/react/react-native.git synced 2026-10-23 06:45:23 +08:00

Files

T

Rob Hogan 783f45746e Bump packages to 0.87.0-main following 0.86 cut (#56716 )

Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/56716

Now that we've cut 0.86, bump all versions on `main` ready for the 0.87 cut.

Changelog: [Internal]

Reviewed By: cortinico, fabriziocucci

Differential Revision: D104219534

fbshipit-source-id: 86f2ebe5b44f67608a7a9495bf9840f2cdd52e5b

2026-05-07 07:23:06 -07:00

__tests__

Fixing typos (#55047 )

2026-01-06 03:23:09 -08:00

bin

Update React Native DevTools binaries

2026-03-28 05:43:31 -07:00

src

Change all remaining flow legacy casting syntax to modern one (#56259 )

2026-03-27 17:58:15 -07:00

.gitignore

Fix gitignore paths for debugger-frontend (#54756 )

2025-12-02 11:13:53 -08:00

package.json

Bump packages to 0.87.0-main following 0.86 cut (#56716 )

2026-05-07 07:23:06 -07:00

README.md

Scaffold debugger-shell package (#51688 )

2025-05-30 02:23:12 -07:00

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.