fix: use stringifySafe for serializing messages in FuseboxReactDevToolsDispatcher

[DorianMazur]

Summary:

Replace JSON.stringify with stringifySafe in FuseboxReactDevToolsDispatcher to safely serialize messages that may contain circular refs. This prevents errors observed when some plugins (e.g., on rozenite.dev) emit circular structures and hardens the dispatcher for other callers.

Changelog:

[GENERAL] [FIXED] - Prevent errors when serializing messages with circular references in FuseboxReactDevToolsDispatcher by using stringifySafe.

Test Plan:

Repro before: use a plugin that emits a circular structure (e.g., via rozenite.dev) → app crashes with “Converting circular structure to JSON”.

After change: no crash; messages are delivered; receiving side still JSON.parses and emits as expected.

[DorianMazur]

Related issue callstackincubator/rozenite#78

[huntie]

Hi @DorianMazur!

React Native DevTools currently has no support for custom plugin communication. My understanding is that Rozenite implements them by reaching into React Native’s internals in an unsupported way. To be clear, such access to internals (including, but not limited to FuseboxReactDevToolsDispatcher) may break at any point, and is not allowed by React Native’s API.

• Phrased another way, you are piggybacking a specific binding meant exclusively for the "Components" and "Profiler" panels
• Outside of Rozenite, this update to FuseboxReactDevToolsDispatcher is unnecessary and adds overhead that will likely slow down these features.

So unfortunately, this isn’t a PR we can accept.

Alternative approach

Looking narrowly at the problem you're solving in this PR - what's the benefit of using the private __FUSEBOX_REACT_DEVTOOLS_DISPATCHER__ hook, as opposed to building your own user-land mechanism for messages? For example, a separate, dedicated binding where you can support any kind of data structure needed for your use case.

Our stance on React Native DevTools extendability

Extensions support in RNDT is something we absolutely want to build towards (capacity willing in our team!). We appreciate the early steps made by Rozenite, however we cannot have these extensions compromise the core debugging experience in RNDT.

We don't want to block the ability for open source to build upon the React Native project, however these must use public extension points. And again, we're concerned about the current setup of Rozenite in some places.

Again we're grateful that a start has been made on extensions support, and we're keen to coalesce on a durable design. We are in communication(!), and will sync up at the Core Contributors Summit in September.