title: How to debug javascript in the new React Native architecture?
body: <p>I couldn't find any documentation or any piece of information about how we will handle javascript debugging in the same or at least similar manner as we have already been doing in the current architecture like using <code>Attach to packager</code> or Chrome DevTools debugging options.</p>
  <p>As far as I understand, currently we are using JSC for the main javascript engine, but when we start a debug session, instead of using JSC, it starts using the Chrome V8 engine since it allows us to use Chrome Developer Tools for easy debugging. Taken from <a href="https://medium.com/@suyogkrazz/you-should-not-always-rely-on-remote-debugging-react-native-787a850c7ad8" rel="nofollow noreferrer">here</a></p>
  <blockquote>
  <p>When using Chrome debugging, it runs all the JavaScript code within
  Chrome itself and communicates with native code via WebSocket. So you
  are using V8.</p>
  </blockquote>
  <p>With the new architecture, we must enable TurboModules first, but it completely disable the Debug option so we can not carry on using these traditional debugging options.</p>
  <p>But it is also mentioned <a href="https://formidable.com/blog/2019/jsi-jsc-part-2/" rel="nofollow noreferrer">here</a> that we can theoretically use any javascript engine. So it can be Chrome v8 as well. Does it mean that we can use Chrome DevTools if we somehow enable to tell JSI to use V8?</p>