-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open Metro in iTerm on macOS #303
Comments
Current terminal is available behind |
Summary: This PR specifies the correct terminal to start the Metro bundler as stated in react-native-community/cli#303. [iOS] [Changed] - Start the packager on the correct terminal. Pull Request resolved: #24436 Differential Revision: D14932703 Pulled By: cpojer fbshipit-source-id: 4c9b5a380ff4f4767acbeb6872e11e03df5b160c
You can always open Finder and find the |
npx react-native run-ios also open |
anyone ... maybe @lucasbento ... clear on why both of these still open Terminal.app, not iTerm?
I've also tried macOS 10.17.7 |
@swrobel I think the |
Thanks @mattwoberts but the examples provided in #310 indicate that it should work with |
I'm using tmux and the trick above doesn't work... It would be nice if the process just ran in the same shell where I invoke |
Looks like this was implemented in facebook/react-native#24436 which added support for $RCT_TERMINAL, $REACT_TERMINAL, and $TERM_PROGRAM in There's now a https://github.com/facebook/react-native/blob/main/template/ios/HelloWorld.xcodeproj/project.pbxproj but that doesn't include any of the support for $RCT_TERMINAL, $REACT_TERMINAL, $TERM_PROGRAM etc. |
Worked here |
Describe the Feature
A lot of people use iTerm 2 on macOS. When using
run-android
orrun-ios
, Metro is started inTerminal.app
even when launched from iterm. Ideally we'd create a new tab or window in iTerm.Possible Implementations
Related Issues
Note that
run-android
already has an option to chose the terminal via an environment variable. It looks like it should work but it didn't when I just tested it.The text was updated successfully, but these errors were encountered: