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
Interesting. I hadn't considered that. The only downsides I see:
It's harder to find. Start would be the logical place I'd check first.
It would bubble up to all environments which is typically undesirable. Though this can be mitigated by checking the url for localhost so that redirecting only occurs in local dev.
The use case: App that is normally called from a separate app with required context provided via querystring.
I have the config above working on a fork of create-react-app, but I had to disable the Apple specific alternative to opn in react-dev-utils/openBrowser because it ignores querystrings.
I think this is a bit of an unusual use case, and I don't think we'll be supporting this by default.
Maybe in the future as part of more general "default URL" customization.
I think I'm going to close this unless there's more support for this being configurable. Since 0.9.0, you can override BROWSER environment variable to disable the default opening behavior (and potentially do something else in a custom script instead):
Activity
gaearon commentedon Feb 9, 2017
Hmm. Why not set up a redirect in
src/index.jsif this is absolutely required for the app?coryhouse commentedon Feb 9, 2017
Interesting. I hadn't considered that. The only downsides I see:
The use case: App that is normally called from a separate app with required context provided via querystring.
I have the config above working on a fork of create-react-app, but I had to disable the Apple specific alternative to opn in react-dev-utils/openBrowser because it ignores querystrings.
gaearon commentedon Feb 9, 2017
I think this is a bit of an unusual use case, and I don't think we'll be supporting this by default.
Maybe in the future as part of more general "default URL" customization.
gaearon commentedon Feb 11, 2017
I think I'm going to close this unless there's more support for this being configurable. Since 0.9.0, you can override
BROWSERenvironment variable to disable the default opening behavior (and potentially do something else in a custom script instead):gaearon commentedon May 15, 2017
Seems like this use case will be fixed by #1590.