edge-paths
npmv3.0.5TypeScriptGet the paths of edge browser easily
Not recommended for new projects
No — edge-paths should not be adopted for new projects. Last published 1345 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1345 days ago.
- AWeight: grade A, Excellent.
Pulls in 3 transitive packages, about 86 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding edge-paths to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Licenses in the dependency tree
Every license you inherit by installing edge-paths, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=14.0.0
- Module format
- ESM only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the edge-paths README.
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())edge-paths vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| edge-pathsthis page | 0 | 1 | MIT | 3 years ago |
| locate-path | 0 | 1 | MIT | 1 day ago |
| path-parse | 0 | 1 | MIT | 1 day ago |
| jose | 0 | 2 | MIT | 1 day ago |
| env-paths | 0 | 2 | MIT | 1 day ago |
| path-key | 244.9M | 1 | MIT | 1 day ago |
Dependencies
Declared by edge-paths v3.0.5. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (2)
Dev (3)
Used by
Popular packages that depend on edge-paths.
Relationship graph
Dependencies (left) and dependents (right) of edge-paths.
Frequently installed together
Like which(1) unix command. Find the first instance of an executable in the PATH.
An HTTP(s) proxy `http.Agent` implementation for HTTPS
An AST-based pattern checker for JavaScript.
Next generation testing framework powered by Vite
Convert a camelized string into a lowercased one with a custom separator: unicornRainbow → unicorn_rainbow
TypeScript execution environment and REPL for node.js, with source map support
Next-gen browser and mobile automation test framework for Node.js
V8 coverage provider for Vitest
A helper utility for logging of WebdriverIO packages
TypeScript definitions for node
Utility to wait for a TCP port to open.
Validate XML, Parse XML, Build XML without C/C++ based libraries
Release history
No releases in the last two years, typically about 0 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.0.5latest | 3 years ago | 9.3 KB | MIT |
| 3.0.4 | 3 years ago | 9.3 KB | MIT |
| 3.0.3 | 3 years ago | 9.3 KB | MIT |
| 3.0.2 | 3 years ago | 9.3 KB | MIT |
| 3.0.1 | 3 years ago | 9.3 KB | MIT |
| 3.0.0 | 3 years ago | 9.3 KB | MIT |
| 2.2.1 | 5 years ago | 21 KB | MIT |
| 2.2.0 | 5 years ago | 21 KB | MIT |
| 2.1.0 | 6 years ago | 12 KB | MIT |
| 2.0.0 | 6 years ago | 13 KB | MIT |
| 1.0.5 | 6 years ago | 3.8 KB | MIT |
| 1.0.4 | 6 years ago | 3.8 KB | MIT |
| 1.0.3 | 6 years ago | 3.8 KB | MIT |
| 1.0.2 | 6 years ago | 3.4 KB | ISC |
| 1.0.1 | 6 years ago | 3.4 KB | ISC |
Overview
edge-paths is an npm package that get the paths of edge browser easily. It has 1 known dependents in the graph. The latest version is 3.0.5, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need get the paths of edge browser easily and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use edge-paths?
No — edge-paths should not be adopted for new projects. Last published 1345 days ago.
How do I install edge-paths?
Run `npm install edge-paths` to add edge-paths to your npm project.
How many dependencies does edge-paths have?
edge-paths declares 5 direct dependencies and pulls in 3 packages in total once its runtime tree is resolved totalling about 86 KB on disk.
What license is edge-paths released under?
edge-paths is distributed under the MIT license. Its dependency tree also includes: BlueOak-1.0.0, ISC, MIT.
How popular is edge-paths?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on edge-paths.
Is edge-paths still maintained?
The most recent release of edge-paths (v3.0.5) was published 3 years ago.
Does edge-paths run install scripts?
No. edge-paths does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.