betterhyq

betterhyq / browser-paths

Public

A tiny cross‑platform helper crate that locates the executable file paths of Chrome and Edge (stable / beta / dev / canary) on the current machine.

chrome chrome-paths devtools edge edge-paths
21
0
100% credibility
Found Feb 17, 2026 at 21 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Rust
AI Summary

A compact helper that automatically detects and provides the file paths to Chrome and Edge browsers (including beta, dev, and canary versions) on different computers.

How It Works

1
🕵️‍♂️ Need browser locations

You're creating something that must find where Chrome or Edge browsers are installed on any computer.

2
📖 Discover the helper

You find a small, reliable tool made just to locate these browsers on Windows, Mac, or Linux.

3
➕ Add it simply

You include this handy finder into your creation with a quick, effortless step.

4
🔍 Ask for a browser

You request the location of stable Chrome, latest Edge, or any version you need.

5
💡 It finds instantly

The tool checks common places and delivers the exact spot where the browser lives.

🎉 Ready to use

Your project now knows precisely where the browser is, working perfectly everywhere.

Sign up to see the full architecture

4 more

Sign Up Free

Star Growth

See how this repo grew from 21 to 21 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is browser-paths?

This Rust crate finds executable paths for Chrome and Edge—covering stable, beta, dev, and canary channels—on Linux, macOS, or Windows. It solves the hassle of hunting browser binaries across platforms, like figuring out where browser click paths are saved in which format or self_binary_paths browser_path on the current machine. Drop in functions like get_any_chrome_latest or get_edge_path to get an Option instantly.

Why is it gaining traction?

Unlike bulkier tools, it's a github tiny crate—lean like github tiny 11 or github tiny windows 11—relying on just the 'which' dep for cross-platform detection without fuss. Devs grab the latest (Canary first) or stable-ish (Stable prioritized) browser paths in one call, beating manual env var checks or platform-specific hacks. Simple API hooks Rust tool builders needing quick browser launches.

Who should use this?

Rust CLI authors automating browser tasks, like e2e test runners spawning Chrome dev or Edge canary. Desktop app devs integrating webviews, or pathsolutions mib browser wrappers avoiding hardcoded paths. Skip if you're in Node/Python—stick to platform-native finders.

Verdict

Grab it for niche Rust automation; 21 stars and 1.0% credibility score signal early days with basic tests assuming browsers exist. Solid docs and MIT license make it low-risk to try, but watch for edge cases on custom installs.

(178 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.