262 Commits
Author SHA1 Message Date
React Native Bot 10644a0cc5 Release 0.85.0
#publish-packages-to-npm&latest
2026-04-07 16:18:20 +00:00
React Native Bot b2839b1d62 Release 0.85.0-rc.7
#publish-packages-to-npm&next
2026-03-30 16:14:50 +00:00
React Native Bot 8f22bbd225 Release 0.85.0-rc.6
#publish-packages-to-npm&next
2026-03-23 17:43:41 +00:00
React Native Bot eae2c5f89d Release 0.85.0-rc.5
#publish-packages-to-npm&next
2026-03-18 16:02:12 +00:00
React Native Bot e2e415fd58 Release 0.85.0-rc.4
#publish-packages-to-npm&next
2026-03-18 09:37:27 +00:00
React Native Bot 1c7c810e94 Release 0.85.0-rc.3
#publish-packages-to-npm&next
2026-03-17 17:53:15 +00:00
React Native Bot 715336c6e1 Release 0.85.0-rc.2
#publish-packages-to-npm&next
2026-03-16 20:34:12 +00:00
React Native Bot 6be3604ab6 Release 0.85.0-rc.1
#publish-packages-to-npm&next
2026-03-09 17:20:48 +00:00
React Native Bot 3e2367c58d Release 0.85.0-rc.0
#publish-packages-to-npm&next
2026-03-03 22:48:45 +00:00
Fabrizio Duroni e5d720d98d Added missing tests for Standalone fusebox shell (#55460)
Summary:
This PR adds the missing test coverage for the standalone Fusebox debugger shell in `StandaloneFuseboxShell-test`.
First, I added some missing expectation for the success case (`enableStandaloneFuseboxShell=true` and no errors) already present:

- the assertion that `unstable_prepareFuseboxShell` is called just one time during middleware initialization
- the assertion that `launchDebuggerAppWindow` is never called when the standalone shell is available

Then, I added the missing test for the case when `unstable_prepareFuseboxShell` returns one of the error code like eg. `platform_not_supported` (as reported also in the TODO that I removed).
In this way now the test is verifying the full behaviour for the new standalone mode for debugger/dev tools.

## Changelog:

[GENERAL] [CHANGED] - Added missing tests for Standalone fusebox shell

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

Test Plan:
- Ran `StandaloneFuseboxShell-test` and verify all tests cases passed
- Ran the full React Native test suite to ensure all tests pass.
- Verified test correctness by intentionally breaking production code:
  - removing the calls to the `DefaultBrowserLauncher` in `openDebuggerMiddleware` to verify that the tests were correctly failing

Reviewed By: Abbondanzo

Differential Revision: D93157076

Pulled By: huntie

fbshipit-source-id: 51c12ad67dd929035f779b53add9163a6619cf41
2026-02-27 07:22:16 -08:00
Alex Hunt 703fe8b222 Add module mock for DefaultToolLauncher and apply in tests (#55728)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55728

Fixes unwanted side effect launches of the debugger shell in tests (likely introduced in D88161573!).

Also adds error guard on `DefaultAppLauncher` to ensure that the implementation is always mocked.

Changelog: [Internal]

Reviewed By: vzaidman

Differential Revision: D94230761

fbshipit-source-id: 966f6f09c38aa55594091bd7d34a5c78dc6eee93
2026-02-26 12:12:16 -08:00
Alex Hunt 4206c12180 Rename BrowserLauncher interface and implementations
Summary:
Renames the **"BrowserLauncher"** concept (`unstable_browserLauncher`) to **"DevToolLauncher"** (`unstable_toolLauncher`), since the scope is now widened to open the desktop debugger shell by default.

Also rename and remove `unstable_` prefixes for `launchDebuggerShell` and `prepareDebuggerShell` methods (APIs remain unstable on the root option key).

**Why not `DebuggerLauncher`?**

This naming remains wide enough to cover other host process delegation in future (e.g. opening other secondary tools, or opening a generic URL in the browser). Debugger launching methods remain specifically named to match their intent.

Changelog: [Internal]

Reviewed By: vzaidman

Differential Revision: D94218654

fbshipit-source-id: e59d5465f200666cd0f1a189414f2223f5e46f69
2026-02-26 12:12:16 -08:00
Vitali Zaidman 8915d81a5b make metro accept tls server config (#55701)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55701

X-link: https://github.com/facebook/metro/pull/1657

Changelog: [Feature] `config.server.tls` now sets Metro to be exposed as an https server

Reviewed By: robhogan, huntie

Differential Revision: D93857257

fbshipit-source-id: 56ff661c4ddf9cd5d4bb32756b9cb600bb032a1c
2026-02-24 00:57:54 -08:00
Alex Hunt 8250db6ae9 Remove prefersFuseboxFrontend from event reporter (#55549)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55549

**Context**

Clean up the legacy `rn_inspector.html` entry point. React Native DevTools has been the default since 0.76, and we have now removed all internal dependencies at Meta.

**This diff**

- Remove `prefersFuseboxFrontend` metadata from `unstable_eventReporter` API.

Changelog: [Internal]

Reviewed By: vzaidman

Differential Revision: D93247602

fbshipit-source-id: 278f847433259c98deb121562e34a12ff59058a2
2026-02-23 09:39:22 -08:00
Alex Hunt 755895e167 Remove legacy debugger entry point selection (#55548)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55548

**Context**

Clean up the legacy `rn_inspector.html` entry point. React Native DevTools has been the default since 0.76, and we have now removed all internal dependencies at Meta.

We've verified that Reanimated (`react-native-worklets`) also do not depend on this workflow, and documents `chrome://inspect` instead.

**This diff**

- Launching the debugger will no longer check for the `prefersFuseboxFrontend` capability flag (internal contract with the debugger server).
- The modern `rn_fusebox.html` entry point will always be used.

Changelog: [Internal]

Reviewed By: vzaidman

Differential Revision: D93247604

fbshipit-source-id: 1c7b6838d9105c9206ffc0030374dc1ee559a6dd
2026-02-23 09:39:22 -08:00
Phillip Pan 4dfefd1a21 upgrade undici from 5.29.0 to 6.23.0 (#55574)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55574

Upgrade the undici devDependency in react-native/dev-middleware from ^5.29.0 to ^6.23.0 to address security vulnerabilities. undici v6 drops the fastify/busboy dependency and requires Node.js >= 18, which is already satisfied by the engine requirements. The API surface used (Agent, request) remains compatible.

this is low risk, because it's only used in a test.

Changelog: [Internal]

Reviewed By: robhogan

Differential Revision: D93298172

fbshipit-source-id: be623702ebec1bd494c862f9c7990580f6b3cc4d
2026-02-17 09:14:50 -08:00
Emily Brown 10709f427d Refactor serverBaseUrl from string to URL object (#55285)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55285

Changelog: [GENERAL] [CHANGED] - `createDevMiddleware` now accepts `string | URL` for `serverBaseUrl`

Replaces the serverBaseUrl string type with a native URL object across the Metro CLI and Gateway packages.

This change improves type safety and makes URL manipulation more robust by leveraging the built-in URL API instead of string concatenation.

The public createDevMiddleware API has been updated to accept either a string or URL for the serverBaseUrl option.
Internally within the dev-middleware package, the internal APIs (InspectorProxy, openDebuggerMiddleware, getDevToolsFrontendUrl) use URL objects instead of strings.
https://www.npmjs.com/package/react-native/dev-middleware

Reviewed By: vzaidman

Differential Revision: D90987090

fbshipit-source-id: ec5b8faa4ed5c24b489c3d63f7b6030073be5403
2026-02-06 07:08:58 -08:00
Moti Zilberman f04659972c Add multi-session support to Device.js (#55237)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55237

Adds multi-session support to the Node side of the inspector-proxy protocol implementation. The protocol now has an explicit `sessionId` property in all relevant messages.

Multi-session support is fully backwards compatible:

* An app that does not report itself as multi-session capable will get the old proxy behaviour.
* If the `enableStandaloneFuseboxShell` experiment flag is disabled by the integrator/framework, we automatically disable multi-session support, too. This is to guarantee that we continue to have at most one active RNDT window/tab open per app. (The standalone shell guarantees this independently of the proxy, while the old browser-based flow requires the proxy to keep enforcing the single-session UX.)

Changelog: [General][Added] Support multiple CDP connections to one React Native Host (diff 2 of 2)

Reviewed By: robhogan

Differential Revision: D90174643

fbshipit-source-id: b277cf2777d2018c44252dc4eae7b197e51cfb79
2026-01-26 01:42:44 -08:00
Moti Zilberman 534c06f3c8 Add multi-session support to InspectorPackagerConnection (#55238)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55238

Adds multi-session support to the inspector-proxy protocol, specifically to the C++ `InspectorPackagerConnection` class that implements the "device" side of the protocol.

Changelog: [General][Added] Support multiple CDP connections to one React Native Host (diff 1 of 2)

Reviewed By: hoxyq

Differential Revision: D90174642

fbshipit-source-id: b22946aaa5a6f3d2d4a81cbfe81d371ea2bc0632
2026-01-23 05:09:17 -08:00
Vitali Zaidman 3c7b4881dd RN: Allow WS debugger connection to origin from debugger url (#55268)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55268

Allow WS debugger connection to origin from debugger url.

Also notify the user on Metro if a connection is rejected.

Changelog: [General][Fixed] - Reaching Metro from Debugger on urls other than localhost:8081 and 127.0.0.1:8081.

Reviewed By: robhogan, yungsters

Differential Revision: D91130956

fbshipit-source-id: 107dbc78aa60b888325f5c6dca68cc28f4e6af52
2026-01-22 04:21:17 -08:00
Rob Hogan 1bbb9ee0d1 Replace deprecated url.parse in dev-middleware (#55235)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55235

Use of Node's `url.parse` is deprecated and emits a runtime warning (when used in 1P code) from Node 24.

This wouldn't directly affect RN users, but does create noise running from monorepo source.

Changelog: [Internal]

Reviewed By: GijsWeterings

Differential Revision: D90992431

fbshipit-source-id: d53e2837cd13bba3fbb24302c5916038ae0e5a50
2026-01-21 14:10:33 -08:00
Moti Zilberman 211e007522 Add inspector-proxy protocol docs (#55055)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55055

TSIA.

Changelog: [Internal]

Reviewed By: robhogan

Differential Revision: D90174644

fbshipit-source-id: c61eedc70eb2169e14112bd6d48327f5979d8125
2026-01-20 00:22:46 -08:00
Marco Wang cd3a9c55c1 Transform all remaining utility types (#55178)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55178

We are transforming the following utility types to be more consistent with typescript and better AI integration:

* `$NonMaybeType` -> `NonNullable`
* `$ReadOnly` -> `Readonly`
* `$ReadOnlyArray` -> `ReadonlyArray`
* `$ReadOnlyMap` -> `ReadonlyMap`
* `$ReadOnlySet` -> `ReadonlySet`
* `$Keys` -> `keyof`
* `$Values` -> `Values`
* `mixed` -> `unknown`

See details in https://fb.workplace.com/groups/flowlang/permalink/1837907750148213/.

drop-conflicts

Command:

`js1 flow-runner codemod flow/transformUtilityType --format-files=false --legacy-type='ALL'`

Reviewed By: SamChou19815

Differential Revision: D90728908

fbshipit-source-id: a8a1a06eb274cc32b12e893679aa92034eb962c4
2026-01-15 16:02:51 -08:00
Alex Hunt f1bedfb92b Bump packages for next release (#55172)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55172

Follows the recent `0.84-stable` branch cut.

Changelog: [Internal] - Bump all packages to `0.85.0-main`

Reviewed By: vzaidman

Differential Revision: D90698490

fbshipit-source-id: b81b840bfd66e631f160a11c4c64baa6850e3393
2026-01-14 12:17:16 -08:00
Rob Hogan c9c601d61a Node.js: Drop support for Node.js versions released before 20.19.4, and EOL v21,v23 (#55114)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55114

Our official [docs](https://reactnative.dev/docs/set-up-your-environment#node--watchman) require:

> Node 20.19.4 or newer

Currently, our `package.json#engines` fields express this as `"node": ">= 20.19.4"`

This is a bit imprecise because of Node's overlapping release lines - e.g. v24.0.0 is actually older than v20.19.4 (2025-07-15), and the whole v21 line was already EOL before v20.19.4.

The release *date* is relevant because Node.js frequently backports the most important updates - notably, `require(esm)` is already stable in Node 20.19 but is not unflagged in v22 until v22.12.

This makes the `package.json#engines` requirement truer to the documented requirement, dropping some old minors and EOL majors that prevent us using features included in v20.19.

Notably, `require(esm)` is stable and unflagged on all versions supported from this diff.

 - v21 and v23 are EOL, so are dropped.
 - v22.13 pre-dates 20.19.4 and is the first to have unflagged silent `require(esm)`
 - v24.3.0 pre-dates 20.19.4 and is the first to unflag TS-stripping
 - Support v25 and newer.

Changelog:
[General][Breaking] Drop support for EOL Node.js lines and old minors.

Reviewed By: cortinico, huntie

Differential Revision: D90467358

fbshipit-source-id: a5fdfb1b93a9d6cffe78eb6811ff7420ab906f44
2026-01-14 10:49:05 -08:00
Marco Wang 7051a07c63 Transform $ReadOnlyArray to ReadonlyArray 17/n (#55109)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55109

We are transforming the following utility types to be more consistent with typescript and better AI integration:

* `$NonMaybeType` -> `NonNullable`
* `$ReadOnly` -> `Readonly`
* `$ReadOnlyArray` -> `ReadonlyArray`
* `$ReadOnlyMap` -> `ReadonlyMap`
* `$ReadOnlySet` -> `ReadonlySet`
* `$Keys` -> `keyof`
* `$Values` -> `Values`
* `mixed` -> `unknown`

See details in https://fb.workplace.com/groups/flowlang/permalink/1837907750148213/.

drop-conflicts

Command:

`js1 flow-runner codemod flow/transformUtilityType --legacy-type='$ReadOnlyArray'`

Reviewed By: SamChou19815

Differential Revision: D90402950

fbshipit-source-id: d338ad7997728d40457b1199c3bd5dcd245a39c3
2026-01-13 20:33:09 -08:00
Marco Wang ea6884cc55 Transform $ReadOnlyMap to ReadonlyMap (#55110)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55110

We are transforming the following utility types to be more consistent with typescript and better AI integration:

* `$NonMaybeType` -> `NonNullable`
* `$ReadOnly` -> `Readonly`
* `$ReadOnlyArray` -> `ReadonlyArray`
* `$ReadOnlyMap` -> `ReadonlyMap`
* `$ReadOnlySet` -> `ReadonlySet`
* `$Keys` -> `keyof`
* `$Values` -> `Values`
* `mixed` -> `unknown`

See details in https://fb.workplace.com/groups/flowlang/permalink/1837907750148213/.

drop-conflicts

Command:

`js1 flow-runner codemod flow/transformUtilityType --format-files=false --legacy-type='$ReadOnlyMap'`

Changelog: [Internal]

Reviewed By: SamChou19815

Differential Revision: D90425806

fbshipit-source-id: e725c86053879a571b36aaeae1154d779571b362
2026-01-12 19:15:05 -08:00
Rob Hogan 0cda10b00a Revert: Bump minimum Node.js version to v22.11 (prev LTS) (#55113)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55113

Reverts https://github.com/facebook/react-native/pull/55038

Dropping v20 (still in LTS) causes friction with Expo's LTS policy, so we're restoring support for v20.19.

Changelog: [General][Added] Revert https://github.com/facebook/react-native/pull/55038

Reviewed By: shwanton

Differential Revision: D90467161

fbshipit-source-id: d876cf7869f11e04058f88239f553704e0706514
2026-01-11 14:30:40 -08:00
Tim Yung f34b8702db RN: Verify Debugger Connection Origins (#55101)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55101

Introduces origin verification for requests to establish debugger connections.

Changelog:
[General][Fixed] - Changed debugger proxy to only permit connections from localhost.

Reviewed By: robhogan

Differential Revision: D90348550

fbshipit-source-id: 71589a340d16b831bdb87660963677d7e0890078
2026-01-08 17:29:06 -08:00
Phil Pluckthun 1f2312687b Bump chromium-edge-launcher to drop rimraf (#54711)
Summary:
Related to https://github.com/facebook/react-native/issues/54669

This version bump drops `rimraf`.

This has been raised at a sync before, but it'd be great to instead drop or replace this entirly. I also noticed that it pulls in `types/node@*`, which isn't necessary for it to function as well, and generally, it'd be nice if we had an alternative here.

cc huntie

## Changelog:

[GENERAL] [SECURITY] - Bump to `chromium-edge-launcher@^0.3.0` to drop `rimraf`

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

Test Plan: - Package hasn't changed except for `rimraf` having been dropped

Reviewed By: huntie, cortinico

Differential Revision: D87978681

Pulled By: robhogan

fbshipit-source-id: b761493f677f9cd4008d3fda584dd04de40c0845
2026-01-07 11:21:59 -08:00
Alex Hunt 4bd62a1d41 Remove "JavaScript logs have moved!" notice (#55075)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55075

It's been >1y since we introduced this notice (and introduced the `--client-logs` flag) — clean up.

Changelog:
[General][Changed] - Remove "JavaScript logs have moved!" notice from dev server CLI

Reviewed By: hoxyq

Differential Revision: D90247471

fbshipit-source-id: dc13c90476c65c301bdb3a51db91f0e5fe0b326b
2026-01-07 06:51:02 -08:00
Marco Wang 1cc30dc1ad Transform $ReadOnly to Readonly 37/n (#55066)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55066

We are transforming the following utility types to be more consistent with typescript and better AI integration:

* `$NonMaybeType` -> `NonNullable`
* `$ReadOnly` -> `Readonly`
* `$ReadOnlyArray` -> `ReadonlyArray`
* `$ReadOnlyMap` -> `ReadonlyMap`
* `$ReadOnlySet` -> `ReadonlySet`
* `$Keys` -> `keyof`
* `$Values` -> `Values`
* `mixed` -> `unknown`

See details in https://fb.workplace.com/groups/flowlang/permalink/1837907750148213/.

drop-conflicts

Command:

`js1 flow-runner codemod flow/transformUtilityType --legacy-type='$ReadOnly'`

Changelog:[internal]

Differential Revision: D90146145

fbshipit-source-id: 4b71784a36f8286f3be620969ea408cf8a0aac80
2026-01-06 18:57:56 -08:00
Rob Hogan 8f10b339d4 Breaking: Bump minimum Node.js version to v22.11 (prev LTS) (#55038)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55038

Bump the minimum to Node.js v22.11, which is the previous LTS now that v24 is in LTS. Drop support for Node v20.

https://nodejs.org/en/blog/release/v22.11.0
https://nodejs.org/en/about/previous-releases

Changelog: [General][Breaking] Bump minimum Node.js version to v22.11

Reviewed By: cortinico, huntie

Differential Revision: D90109056

fbshipit-source-id: 178f29d3131f21fccf956decc9ac94365a2bfe53
2026-01-05 06:21:25 -08:00
Vitali Zaidman 89ac112791 removed unstable functions tracking the existance of connected devices (#55008)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/55008

Changelog: [Internal] removed an unstable function briefly added in #54447

This was previously added in https://github.com/facebook/react-native/pull/54447, but not needed anymore as we found a different way to get this information without exposing a special API for that.

Reviewed By: robhogan

Differential Revision: D89962175

fbshipit-source-id: 3636ef8815678781ee39ef8211f00bde69b5ce63
2026-01-04 12:16:58 -08:00
Marco Wang 2624e2f52e Transform mixed to unknown in xplat/js (#54955)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54955

We are transforming the following utility types to be more consistent with typescript and better AI integration:

* `$NonMaybeType` -> `NonNullable`
* `$ReadOnly` -> `Readonly`
* `$ReadOnlyArray` -> `ReadonlyArray`
* `$ReadOnlyMap` -> `ReadonlyMap`
* `$ReadOnlySet` -> `ReadonlySet`
* `$Keys` -> `keyof`
* `$Values` -> `Values`
* `mixed` -> `unknown`

See details in https://fb.workplace.com/groups/flowlang/permalink/1837907750148213/.
drop-conflicts

Reviewed By: SamChou19815

Differential Revision: D89581584

fbshipit-source-id: cc5953ffea6cf1060f69efc714508e8ba93a040c
2025-12-22 12:25:44 -08:00
Marco Wang f41f3bf41f Transform all Flow legacy utility types ($NonMaybeType) to TypeScript-style types in xplat/js (#54935)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54935

We are transforming the following utility types to be more consistent with typescript and better AI integration:

* `$NonMaybeType` -> `NonNullable`
* `$ReadOnly` -> `Readonly`
* `$ReadOnlyArray` -> `ReadonlyArray`
* `$ReadOnlyMap` -> `ReadonlyMap`
* `$ReadOnlySet` -> `ReadonlySet`
* `$Keys` -> `keyof`
* `$Values` -> `Values`
* `mixed` -> `unknown`

See details in https://fb.workplace.com/groups/flowlang/permalink/1837907750148213/.

drop-conflicts

Reviewed By: gkz

Differential Revision: D89494075

fbshipit-source-id: 1bc3e0039dfb5bf04f1860d5098e024fb8491647
2025-12-19 01:35:12 -08:00
Alex Hunt cc9164c337 Move JavaScript exports rewrites to publishConfig/prepack (#54857)
Summary:
### Motivation

Updates the shared JavaScript build setup to use the modern `publishConfig` convention.

This:

- Simplifies the build script.
- Makes the production values for `"exports"` more understandable in place (especially by separating from exports conditions).
- Prevents us from creating a dirty file state when running `yarn build`.

### Changes

- Add `publishConfig` to each `package.json` listing production `"exports"` targets.
- Add `scripts/build/prepack.js` script to action `publishConfig` (now on `npm pack`, `npm publish` exclusively).
- Remove `"exports"` rewriting (and un-rewriting safeguards) from build script.

**Note on `"prepack"`**

Slightly unfortunately, `publishConfig` doesn't work consistently between package managers currently, including npm — so this does not work implicitly (but may in future).

We're instead following `publishConfig` as a convention, and explicitly implementing a full copy (theoretically forking us towards pnpm and Yarn v4's approach).

However, I believe this is:

- Worthwhile, for the motivations above — and in particular being able to understand the final shape of `"exports"` (independent from the dimension of conditional exports, which may come into play later).
- Completely inspectable/maintainable as an explicit implementation (`scripts/build/prepack.js`).

Changelog: [Internal]

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

Test Plan:
### CI

✅ GitHub Actions

### End-to-end release test script

(Note: Rebased on `0.83-stable` when tested)

```
yarn test-release-local -t "RNTestProject" -p "iOS" -c $GITHUB_TOKEN
```

{F1984106139}

✅ Test script runs `npm publish` on packages to a local proxy.

{F1984106146}

✅ Installed packages have `publishConfig` `"exports"` values applied

NOTE: ⬆️ This is **exactly** the same output as before.

 {F1984106148}

✅ `/tmp/RNTestProject` runs using built + proxy-published + proxy-installed packages

Reviewed By: cipolleschi

Differential Revision: D88963450

Pulled By: huntie

fbshipit-source-id: f328252cf93a1f1039b79d7f369d1e6e7e5b4b52
2025-12-12 04:08:59 -08:00
Vitali Zaidman 1c282d7ef1 move default React Native DevTools launching params downstream (#54528)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54528

Changelog: [Internal]

Currently, `DefaultBrowserLauncher.js` holds arguments configuring how the debugger shell is launched. Instead, move some of them downstream, and make `DefaultBrowserLauncher.js` use the defaults.

Reviewed By: motiz88

Differential Revision: D86772692

fbshipit-source-id: 826bb6236dc3cba3c4b0d455aebf3f81c4e8ed6f
2025-12-10 01:49:36 -08:00
Vitali Zaidman 7cecf15c59 expose if there are any connected devices to dev middleware and adding event on if this changes (#54447)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54447

Changelog: [Internal]

Expose `unstable_hasConnectedDevices` and `unstable_addHasConnectedDevicesListener` from both `InspectorProxy` and `DevMiddleware` that tells the user if any devices are connected to `devMiddleware` and allows to listen to whenever this state changes.

Reviewed By: motiz88

Differential Revision: D86319965

fbshipit-source-id: 18a30138b16a41821dc17a63e9d9cada04888f34
2025-12-10 01:49:36 -08:00
Alex Hunt ae01be8cc2 Enable RNDT standalone shell by default (#54754)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54754

Enables the standalone app shell for React Native DevTools by default.

We preserve + document this flag as an opt-out (allowing Frameworks to override this behaviour if needed).

Changelog: [Internal]

Reviewed By: motiz88

Differential Revision: D88161573

fbshipit-source-id: 64ee191dcead4e639bb3067bc9e715b1c8cdf80d
2025-12-02 09:26:26 -08:00
Rob Hogan f3f7e17c60 Update dev dependency selfsigned to v4, fix Node >=v24.5 compatibility, restore CI (#54634)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54634

CI fails after attempting to update to Node v24 (latest LTS) because our `dev-middleware` dev-only dependency `selfsigned` uses a default key size incompatible with the version of OpenSSL in Node>=24.5. We see lots of:

```
error:0A00018F:SSL routines::ee key too small
```

This was mitigated in OSS CI by pinning our Node tests to before v24.5: https://github.com/facebook/react-native/pull/53013

This default is raised upstream in https://github.com/jfromaniello/selfsigned/commit/bf687c80cfe125b7051c7b2f07e321289c037993 , this bumps to v4 which includes that fix, and removes the temporary mitigation above.

Changelog:
[Internal]

Reviewed By: cipolleschi

Differential Revision: D87643898

fbshipit-source-id: f1072c0801769d5fcd4bb53f68999653c6dad29f
2025-11-25 08:52:23 -08:00
Alex Hunt a1e534a604 Bump packages for next release (#54452)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54452

Follows the recent `0.83-stable` branch cut.

Changelog: [Internal] - Bump all packages to `0.84.0-main`

Reviewed By: cipolleschi

Differential Revision: D86534507

fbshipit-source-id: 47b88dce919857398f41516d03d60259730d2887
2025-11-12 04:22:19 -08:00
Nicola Corti d9a582e949 Bump packages to 0.83.0-main (#54009)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/54009

Packages haven't been bumped on main ahead of 0.83. This takes care of it.

Changelog:
[Internal] [Changed] -

Reviewed By: cipolleschi, huntie

Differential Revision: D83580515

fbshipit-source-id: 7471e77f74e3fb3b4ee6538a49369b5df1393098
2025-10-01 07:13:33 -07:00
Alex Hunt b577679746 Update DevTools windowKey to a sha256 hash (#53923)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/53923

Motivated by feedback on D83070252. This prevents us from including decodable information about debug targets in these values.

Changelog: [Internal]

Reviewed By: motiz88

Differential Revision: D83139401

fbshipit-source-id: 01b01d23e4dfb06e400729b8cedf1fe2e098b209
2025-09-25 01:22:58 -07:00
Vitali Zaidman 3a954caf4f don't require projectRoot in devMiddleware (#53921)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/53921

Changelog: [Internal] `devMiddleware` removed the unused option `projectRoot`

This option was used only in a dead branch of the code inside `InspectorProxy`.

The scenario where it appeared was enabling resolving script sources (`Debugger.getScriptSource`) starting with `file://` which were coming from the file system. However, we don't seem to ever point scripts at the filesystem this way.

Reviewed By: huntie

Differential Revision: D82739662

fbshipit-source-id: 9a130eaa83cb94ae0e36a5a1102c56ff8a36cffc
2025-09-24 12:47:24 -07:00
Vitali Zaidman e3bf881ae6 remove connection hints from being logged for the user (#53884)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/53884

Changelog: [Internal]

Now that there's a clear display for when HMR is disconnected, we don't want to show messages regardless devices connection and disconnection to the DevServer because they are too partial.

Reviewed By: huntie

Differential Revision: D82727105

fbshipit-source-id: 32dd077f85d2044f89ae2d8d60a37c0ec6cccbbf
2025-09-22 15:55:25 -07:00
Pieter De Baets 96c33a8b0b Update ws to 7.5.10 (#53781)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/53781

Fixes deprecation warning printed when starting various `js1` tools

Changelog: [Internal]

Reviewed By: robhogan

Differential Revision: D82449982

fbshipit-source-id: 852b5a6980badef146b4e194434f2f9c6dd9a1d5
2025-09-16 02:51:06 -07:00
Vitali Zaidman 2b4c48ae47 export Logger type from dev-middleware (#53586)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/53586

Changelog: [Internal]

Reviewed By: huntie

Differential Revision: D81588537

fbshipit-source-id: e6537dd831cfb73ce93326e2e0c0a2bcd3929caa
2025-09-04 08:13:04 -07:00
Moti Zilberman d1a99907cb Work around Electron Windows command-line args quirk (#53510)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/53510

Changelog: [Internal]

Electron imposes a [strange undocumented limitation](https://github.com/electron/electron/pull/13039) on the format of command-line arguments, which for some reason only affects Windows. Basically, the command line is truncated after the first argument that looks like a URL.

Electron's recommendation for avoiding this is to prefix the argument list with `--`,  but I prefer switching to a different arg format (`--x=y` instead of `--x y`) that will prevent us from ever running into this issue.

NOTE: I will follow up with a diff to harden arg parsing in our Electron code so that it only accepts the `--x=y` format.

Reviewed By: huntie

Differential Revision: D81237713

fbshipit-source-id: a255dc63b6486b96d9f7ccf780d1b09bc4ddf7e0
2025-08-28 10:27:22 -07:00
Moti Zilberman 111187f6a4 Document unstable_experiments.enableStandaloneFuseboxShell (#53482)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/53482

Changelog: [Internal]

TSIA

Reviewed By: huntie

Differential Revision: D81127995

fbshipit-source-id: cad5720b41ce409e9db1972bea3844ff0e0724ce
2025-08-27 08:11:51 -07:00