Hello all,

I'm opening this issue to start discussing what the future looks like once Turbomodules are GA. It looks like the current debugging experience will be broken in most cases and I think it will be good to start planning.

The gist of the linked conversation is that the only thing that will work is direct debugging. Depending on the target platform this could be a bit more complicated.

Android

The extension already supports Hermes with direct debugging so this shouldn't be an issue.
Do you know the distribution of engines used for Android apps? Should V8 taken into account as well (although hopefully it shouldn't be too complicated?).

iOS

This is more problematic as the only engine that can run is JSC so a proxy that converts its protocol to CDP will be needed. I believe the team already has experience with ios-webkit-debug-proxy but there seems to be an issue with iOS 12.3.1 and real devices.
Does that issue apply only to cordova or would it be the same for React Native? Also, it seems like the project has added support for iOS 13. Would that be enough to enable direct debugging on real iOS devices of React Native applications?

remotedebug-ios-webkit-adapter is another proxy package that seems to have solved the 12.3.1 issue but looks less maintained than the other one.

Windows

It already supports direct debugging. @acoates-ms what engine is/will be used? If it is V8 or Hermes it should hopefully not add a lot of extra work.

Something else that should be taken into account?

Thanks!