You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Facebook released Hermes JS engine and implemented it to React Native Android. This engine is compatible with Chrome DevTools Protocol so we need to investigate how to implement Hermes debugging in React Native Tools.
Important notice
Currently, Hermes doesn't fully support Chrome debugger protocol, so there are some gaps in its implementation. If something not working as expected will be noticed (like object inspector bugs) in the extension debugger then the same thing should be tested in the latest Chrome (Run app, attach to it in Chrome, check how Chrome debugger behave in the same debug scenario).
Here is the Hermes debugging issues list.
Hermes Direct debugging for the extension has been added. With respect to Hermes Expo - I think it might be tracked as another issue when it is released.
Description
Facebook released Hermes JS engine and implemented it to React Native Android. This engine is compatible with Chrome DevTools Protocol so we need to investigate how to implement Hermes debugging in React Native Tools.
Important notice
Currently, Hermes doesn't fully support Chrome debugger protocol, so there are some gaps in its implementation. If something not working as expected will be noticed (like object inspector bugs) in the extension debugger then the same thing should be tested in the latest Chrome (Run app, attach to it in Chrome, check how Chrome debugger behave in the same debug scenario).
Here is the Hermes debugging issues list.
Implementation roadmap
Run Android
scenario supportAttach to packager
scenario supportDebug in Expo
scenario support (Expo doesn't support Hermes yet, here's a roadmap for adding it)cwd
target
env
envFile
trace
address
port
logCatArguments
runArguments
skipFiles
launchActivity
variant
sourceMaps
sourceMapPathOverrides
The text was updated successfully, but these errors were encountered: