[0.73] Remote JS Debugging deprecation

[huntie]

Introduction

In React Native 0.73, we are deprecating Remote JavaScript Debugging via Chrome (docs).

Remote JavaScript Debugging was previously the default debugging experience for apps using JavaScriptCore (JSC). It involves switching JavaScript execution into an external V8 process, to debug in the Chrome browser.

Motivation

• The model of switching JS execution into a separate V8 process is inconsistent with how users' apps actually run. Things such as interactions with Native Modules were in a broken state. In particular, we noticed Remote JS Debugging being incompatible with the New Architecture.
• As the React Native team continues to invest in improving debugging, we want to reduce the surface area of debugging modes that we support.

We are focusing future debugging efforts into providing a first-class experience for Hermes.

Alternatives

• We recommend using Hermes for a consistent debugging experience on all platforms. See all supported debugging methods under Opening the Debugger.
• We recommend Safari Developer Tools (direct JSC debugging) instead, for iOS apps using JSC.

Discussion points

• How does this impact third party tooling (which might inform our removal timeline).
• General feedback.

[thymikee]

I welcome this change very much! Many developers I interacted with didn't even realize that "remote debugging" is running V8 instead of the device's JS engine (I guess the notion of a "JS engine" is also foreign to many developers). And they only learned the difference after bumping into a date issue between JSC and V8 to something of that sort

[jamonholmgren]

I agree; I think the new RN JS Inspector will be a much better DX than the remote JS Debugger.

But -- I did appreciate having the Remote JS Debugger as an option. It did help me solve some things in the past! Just time for it to go I think.