edge-paths

What is edge-paths?

The edge-paths npm package is designed to provide the path to the Microsoft Edge browser executable on different operating systems. This can be useful for developers who need to programmatically launch or interact with the Edge browser in their applications.

What are edge-paths's main functionalities?

Get Edge Path

This feature allows you to retrieve the path to the Microsoft Edge executable. The code sample demonstrates how to use the edge-paths package to get the path and print it to the console.

const edgePaths = require('edge-paths');
const edgePath = edgePaths.getEdgePath();
console.log(edgePath);

Other packages similar to edge-paths

chrome-paths

The chrome-paths package provides the path to the Google Chrome browser executable on different operating systems. Similar to edge-paths, it helps developers programmatically locate the Chrome browser for launching or interacting with it.

puppeteer

Puppeteer is a Node library that provides a high-level API to control Chrome or Chromium over the DevTools Protocol. While it does more than just provide the path to the browser executable, it includes functionality to launch and interact with the browser, making it a more comprehensive tool compared to edge-paths.

README

Edge Paths

Possible paths or binary names of Edge in the current platform

Why?

• Well Documented
• Well Tested
• Used by popular players
• Written with Love <3
• Fully open sourced

Usage

• At the moment linux support is only avail for dev channel. Once canary, beta and stable version are release we shall update the package.

Javascript

import {
	getEdgeBetaPath,
	getEdgeCanaryPath,
	getEdgeDevPath,
	getEdgePath,
	getAnyEdgeStable,
	getAnyEdgeLatest,
} from "./dist/index.js"

console.log(getEdgeBetaPath())
console.log(getEdgeCanaryPath())
console.log(getEdgeDevPath())
console.log(getEdgePath())
// console.log(getAnyEdgeStable())
// console.log(getAnyEdgeLatest())

The output shall look like this according to your installation

// On OSX
// /Applications/Microsoft Edge Beta.app/Contents/MacOS/Microsoft Edge Beta
// /Applications/Microsoft Edge Canary.app/Contents/MacOS/Microsoft Edge Canary
// /Applications/Microsoft Edge Beta.app/Contents/MacOS/Microsoft Edge Dev
// /Applications/Microsoft Edge Beta.app/Contents/MacOS/Microsoft Edge

// On Windows
// C:\Program Files (x86)\Microsoft\Edge Beta\Application\msedge.exe
// C:\Program Files (x86)\Microsoft\Edge Canary\Application\msedge.exe
// C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
// C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe

// On Linux
// Beta edge not avail yet
// Canary not avail
// /usr/bin/microsoft-edge-dev
// Stable not avail

Typescript

import {
	getEdgeBetaPath,
	getEdgeCanaryPath,
	getEdgeDevPath,
	getEdgePath,
} from "edge-paths"

console.log(getEdgeBetaPath())
console.log(getEdgeCanaryPath())
console.log(getEdgeDevPath())
console.log(getEdgePath())

Installation

Use npm.

$ npm install edge-paths

// or

$ yarn add edge-paths

API

import {
	getEdgeBetaPath,
	getEdgeCanaryPath,
	getEdgeDevPath,
	getEdgePath,
	getAnyEdgeStable,
	getAnyEdgeLatest,
}  from "./dist/index.js"

• getAnyEdgeStable or getAnyEdgeLatest might be more useful if you don't want any specific version.

Used By

• devtools

• Please send PR if you are using edge paths. We will be accepting first 10 request.

License

MIT License

© 2020 Shirshak Bajgain