Helium Paths

Possible paths or binary names of Helium in the current platform

Why?

• Well Documented
• Well Tested
• Zero dependencies
• Written with Love <3
• Fully open sourced

Usage

• Helium ships a single channel. There is no separate beta / dev / canary build like Edge, so there are just two functions. On Linux the .desktop entry is parsed as well, so AppImage installs are found too.

Javascript

import { getHeliumPath, getAnyHelium } from "./dist/index.js"

console.log(getHeliumPath())
// console.log(getAnyHelium())

The output shall look like this according to your installation

// On macOS
// /Applications/Helium.app/Contents/MacOS/Helium

// On Windows
// C:\Users\you\AppData\Local\imput\Helium\Application\chrome.exe

// On Linux
// /usr/bin/helium

Typescript

import { getHeliumPath, getAnyHelium } from "helium-paths"

console.log(getHeliumPath())
console.log(getAnyHelium())

Installation

Use npm.

$ npm install helium-paths

// or

$ yarn add helium-paths

API

import { getHeliumPath, getAnyHelium } from "helium-paths"

• getHeliumPath() returns the Helium binary path, or throws if it can't be found.
• getAnyHelium() is the same today, but use it if you don't want to care about specific channels later.

Both throw a plain { name: "helium-paths", message, ... } object when Helium isn't found, so wrap them in a try/catch if that is expected.

License

MIT License

© 2026 Shirshak Bajgain