Skip to content
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

feat: Add --no-open-browser cli option #619

Closed
wants to merge 1 commit into from

Conversation

timmarinin
Copy link

This option allows to inhibit creating new browser tab/window.

This option allows to inhibit creating new
browser tab/window.
@ghost
Copy link

ghost commented Sep 10, 2016

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at [email protected]. Thanks!

@ghost ghost added the CLA Signed label Sep 10, 2016
@ghost
Copy link

ghost commented Sep 10, 2016

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@gaearon
Copy link
Contributor

gaearon commented Sep 10, 2016

Can you please describe your use case for this? Is it just a matter of personal taste, or is opening a new tab not working in some way for you?

@timmarinin
Copy link
Author

timmarinin commented Sep 10, 2016

It's a mix of both.

It falls back to xdg-open at my local machine, so it opens new tab in default browser, which I use for personal stuff. However, I keep development stuff in another browsers. So when I start dev server, it's a nuisance to have another tab pop out. Sometimes I want to keep distractions out, so I close my default browser. Nonetheless, react-scripts opens it back when I do npm start, which is kind of slow.

Another case is that sometimes I develop on remote virtual machine via ssh. That machine doesn't have X installed at all.

@gaearon
Copy link
Contributor

gaearon commented Sep 10, 2016

Another case is that sometimes I develop on remote virtual machine via ssh. That machine doesn't have X installed at all.

What happens? Does opn fail? Hang?

@timmarinin
Copy link
Author

Just noticed something strange: running react-scripts start created a bunch of
[some_hash].json.gzip in my project directory, but I don't think it's related to this issue.

Sometimes react-scripts process dies without any explanation/error. This is
happening in remote dev scenario. I'll investigate if this is related to opn.

@timmarinin
Copy link
Author

json.gzip issue has been dealt with already, as far as I can see.

If you think that this PR introduced flag doesn't worth it (CONTRIBUTING.md says about minimizing flags), feel free to close the PR.

@gaearon
Copy link
Contributor

gaearon commented Sep 16, 2016

I think we may revisit this at some point, but not now. Rather than add ad-hoc flags, I would like to wait for more feature requests, and then perhaps consolidate them into some sort of preferences. Thanks for your time!

@gaearon gaearon closed this Sep 16, 2016
@lock lock bot locked and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants