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
The full search treatment for mac only happens for getInstallations, which is not called by our launcher.
Some things we could change:
getFirstInstallation does the fast mac path, but does not fall back to slow path if none found
We could provide a similar fast path for each OS
for lsregister usage, check for duplicates before reading filesystem (minor perf improvement)
which -a (unix) and where (windows) exist for finding all things on PATH
drop LIGHTHOUSE_CHROMIUM_PATH (it is deprecated)
Some of the sorting seems inconsistent
Worth noting that in practice, only the first installation ever matters, but I can imagine that finding all installations on a machine is a useful feature to someone so let's keep it.
The text was updated successfully, but these errors were encountered:
This is how it works today:
Manually provided chrome location:
CHROME_PATH / LIGHTHOUSE_CHROMIUM_PATH
(mac) Any Chrome you've ever opened (uses
lsregister
)Note: this finds lots of installations! https://gist.github.com/connorjclark/97fef0c9a209b4bd09c87f4125a9b678
(linux) Look for any installation in these desktop folders (recursively), adding all found:
(windows) Look for installations:
in these folders:
Note: the order is: first folder;Chrome SxS;Chrome;second folder; ...
which
for:google-chrome-stable
google-chrome
chromium-browser
chromium
(linux) Do a sorting pass. Because previous steps searched a folder, they need to be sorted by our preference:
(mac) Do a sorting pass. Unlike linux, this sorts primarily by installation folder:
Note: there is a "fast mac" path. Looks like for mac, we always just do:
The full search treatment for mac only happens for
getInstallations
, which is not called by our launcher.Some things we could change:
getFirstInstallation
does the fast mac path, but does not fall back to slow path if none foundlsregister
usage, check for duplicates before reading filesystem (minor perf improvement)which -a
(unix) andwhere
(windows) exist for finding all things on PATHWorth noting that in practice, only the first installation ever matters, but I can imagine that finding all installations on a machine is a useful feature to someone so let's keep it.
The text was updated successfully, but these errors were encountered: