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: Allow browser to be specified #757

Closed

Conversation

evancharlton
Copy link

Instead of making the assumption on behalf of the user, allow them to
control the browser which is used for the debugger UI. This is
controlled via the RCT_DEBUGGER_BROWSER environment variable. If this
variable is populated, then it will be tried first, before falling back
to the baked-in defaults.

Test plan

This can be tested by setting RCT_DEBUGGER_BROWSER to another browser
and then running the start command for the @haul-bundler/cli
package.

Issues

This addresses issue #756

Instead of making the assumption on behalf of the user, allow them to
control the browser which is used for the debugger UI. This is
controlled via the `RCT_DEBUGGER_BROWSER` environment variable. If this
variable is populated, then it will be tried first, before falling back
to the baked-in defaults.
@evancharlton
Copy link
Author

I haven't looked into how to test this in an automated way, but I can if it agreed that this is a valid approach.

},
];

// If the user has provided a specific browser preference, try that one first.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's certainly an argument to be made for not doing a fallback if the user has specified a preference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant