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

Instead of opening my default macOS browser, opens Ubuntu VM through Parallels with Chromium #12

Closed
felixfbecker opened this issue Oct 11, 2020 · 1 comment

Comments

@felixfbecker
Copy link

Ever since Storybook changed to use better-opn my default browser doesn't open anymore when I run it, but instead an Ubuntu VM boots up in Parallels to launch Chromium. This is extremely annoying of course as it takes a lot of resources and takes a while to shut down again.

Here's my setup:

I am on macOS Catalina and have Parallels installed.

Inside Parallels, I have a Ubuntu VM:

image

Inside that Ubuntu VM, I have Chromium installed. This Chromium is registered in macOS as an app shortcut through Parallels:

Chromium shortcut

This is NOT my default browser though. I use regular Chrome, and sometimes others for development, and have Choosy set as my default browser:

Choosy default browser

I would expect that better-opn will always respect the choice I made in macOS system settings as my browser (i.e. exactly what would be picked if you run open https://github.com on the command line).

But instead it always tries to launch Chromium for some reason, which is inside a VM and not my default browser.

@michaellzc
Copy link
Owner

michaellzc commented Oct 13, 2020

the purpose of building this utility program is to re-use the same tab if possible and it can only be done with chromium on macOS, hence by default better-opn favours opening the URL in chromium-based browsers.

I suggest setting the BROWSER environment variable globally or on a per-project basis to the browser of your choice if you don't want such behaviour.

Learn more at storybookjs/storybook#12206 (comment)

I'll close this issue for now. Feel free to reopen if you believe there is a bug exist.

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

No branches or pull requests

2 participants