feat: reuse opening tab in chromium browsers when start dev server

[nvh95]

Description

Currently, if a mac users use Google Chrome, when they start the dev server, vite will try to reuse an opening tab (using AppleScript).

However, many developers they use other Chromium-based browsers such as Chrome Dev, Chrome Beta, Microsoft Edge... This PR is to support reuse an existing tab for some common Chromium browser

Reference:

• https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-dev-utils/openBrowser.js
• https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-dev-utils/openChrome.applescript

Additional context

This is a "nice to have" feature of vite for mac users. We only need to test it on mac (which I already did)

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[ArnaudBarre]

Hi thanks for improving the browser support for Vite.

I want to point out that is not totally free, even if the Apple script is executed once the ps cax | grep is done for each browser, and this is around ~50ms on my Intel mac, without the nodejs overhead. A more precise benchmark could be done, but this is PR would adds around ~150ms to relaunch the browser for current user of Google Chrome (and ~350ms if it's not running).

I think doing a more complex grep in one go and then adding a post filtering in js to know which one effectively match would make this feature almost invisible for current users.

[bluwy]

Thanks for investigating the perf implications of this @ArnaudBarre! Would you like to submit a PR with the suggestion? I think it would benefit create-react-app too

[ArnaudBarre]

Yes I can do it this evening

[ArnaudBarre]

@bluwy can you look at the suggested fix?

I just updated a repo to 3.2 and saw a big jump in server start due to that.

Profiles before/after for Chrome already opened:

[bluwy]

Ah my bad I miss your PR, checking that out now!