[dev-menu] [ENG-10036] update dev menu to make refresh more prominent (#24426)# Why Refresh is the most often used button in the dev menu, but it is not the one that stands out the most. This
[dev-menu] [ENG-10036] update dev menu to make refresh more prominent (#24426)# Why Refresh is the most often used button in the dev menu, but it is not the one that stands out the most. This change will clean up the dev menu to separate out the refresh button and make it stand out more. # How - move the "copy link" button next to the URL (since that's the link you're copying) - make the whole link section peessable (not just the link icon) - move "home" next to the other buttons - move "reload" next to the other buttons, but separate it out to its own section
show more ...
[dev-menu] Disable Remote JS debugger on SDK 49+ (#22010)# Why As part of https://github.com/facebook/react-native/pull/36754, we should remove the ability to use remote JS debugging from the D
[dev-menu] Disable Remote JS debugger on SDK 49+ (#22010)# Why As part of https://github.com/facebook/react-native/pull/36754, we should remove the ability to use remote JS debugging from the DevMenu. This change is motivated by the fact that generally speaking, this feature does not work with the new architecture and most of the popular modules these days. Related to ENG-8088 # How This PR disables the `Remote JS debugger` option inside the dev-menu when using SDK 49 or above # Test Plan Run `dev-menu` locally through bare-expo <table> <tr><th>iOS</th><th>Android</th></tr> <tr> <td> <img src="https://user-images.githubusercontent.com/11707729/230195305-5fcf6bbf-f669-40d6-841b-1decc967bebe.png" height="700px" /> </td> <td> <img src="https://user-images.githubusercontent.com/11707729/230218993-b2fd081c-bc03-4330-8a61-29485c512682.png" height="700px" /> </td> </tr> </table> # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[dev-menu] Integrate hermes inspector like expo go (#19301)# Why align the hermes inspector implementation as expo go #19175. close ENG-6295 # How - from the dev-menu, if the js engine i
[dev-menu] Integrate hermes inspector like expo go (#19301)# Why align the hermes inspector implementation as expo go #19175. close ENG-6295 # How - from the dev-menu, if the js engine is inspectable (hermes /v8), show *Open JS debugger*. otherwise, show the *Remote JS debugger* - change the menu label from *Local dev tools* to *Remote JS debugger* that would make more clear what it is. - [android] change the isJSInsectorAvailable detection from sending http request to dev-server to check engine type. that aligns with expo go implementation and shows the dev menu faster (without waiting for dev-server http response). - [ios] integrate dev-server's endpoint to open the js inspector. note that i still use the classic dev-menu-item extensions to register the command. that would align with android implementations. - align `JsInspector -> JSInspector` - also, support js inspector for v8 # Test Plan - ✅ ios bare-expo hermes + Open JS debugger - ✅ ios bare-expo jsc + Remote JS debugger - ✅ android bare-expo hermes (have to downgrade react-native because the vendored reanimated lead to a crash) + Open JS debugger - ✅ android bare-expo jsc + Remote JS debugger Co-authored-by: Eric Samelson <[email protected]>
[dev-menu][dev-launcher] update dev-menu extensions API (#16558)
[dev-menu] update initial props on android and ios (#16271)
[dev-menu] refactor dev menu on iOS to simplify dev-launcher relationship (#16067)
[dev-menu] remove old js dev menu (#16083)