Work out plan to move community to direct debugging · Issue #206 · react-native-community/discussions-and-proposals (original) (raw)

Introduction

Various upcoming react-native features are going to start requiring that developers debug JS directly against the JS engine running on the device instead of remote JS debugging (or web debugging) that is commonly used today. This includes TurboModules and Fabric, which do not work unless the JS is running on device. In addition even without using these things code has been slowly diverging between web debugging, and direct debugging. (View Configs being an obvious example).

We need to work out a transition plan to move people away from using web debugging, and to start using direct debugging.

Discussion points

How can we identify what are the current blocking issues preventing people from using direct debugging?

How can we encourage people to use direct debugging instead of web debugging?

Web debugging already causes warnings in view configs - should we have an additional more explicit warning, maybe with instructions on how to direct debug instead?

When can we remove web debugging?

We probably wont know for sure until we get a better sense of what gaps currently exist, but could it be marked as deprecated in 0.63, then removed in 0.64? Is that too quick?