</>PackageGraphPackageGraph

pathe

npmv2.0.3TypeScript

Universal filesystem path utils

Adopt with care

pathe is usable, with caveats. Last published 575 days ago. 4 releases in the last 2 years.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • CMaintenance: grade C, Fair — worth a look.

    Last published 575 days ago. 4 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 50 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 2 maintainers, and a contained dependency surface.

  • 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 pathe to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

50 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
ESM + CommonJS
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the pathe README.

// ESM / Typescript
import { resolve, matchesGlob } from "pathe";

// CommonJS
const { resolve, matchesGlob } = require("pathe");

Dependencies

Declared by pathe v2.0.3. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (12)

@types/node ^22.13.1@vitest/coverage-v8 ^3.0.5changelogen ^0.5.7esbuild ^0.25.0eslint ^9.20.1eslint-config-unjs ^0.4.2jiti ^2.4.2prettier ^3.5.0typescript ^5.7.3unbuild ^3.3.1vitest ^3.0.5zeptomatch ^2.0.0

Used by

Popular packages that depend on pathe.

vitenpm

Native-ESM powered web dev build tool

158.6M/wk26 dependentsMIT
vitestnpm

Next generation testing framework powered by Vite

92.7M/wk129 dependentsMITTS
rolldownnpm

Fast JavaScript/TypeScript bundler in Rust with Rollup-compatible API.

81.9M/wk8 dependentsMITTS
mllynpm

Missing ECMAScript module utils for Node.js

25.1M/wk7 dependentsMITTS
kyselynpm

Type safe SQL query builder

15.6M/wk1 dependentsMIT
@vitest/uinpm

UI for Vitest

8.9M/wk9 dependentsMITTS
@vitejs/devtools-rolldownnpm

DevTools for Rolldown

81.8K/wk1 dependentsMITTS
@devframes/vitenpm

Vite plugin for mounting a devframe inside any Vite-based host (Astro, SolidStart, Nuxt, plain Vite apps).

43.5K/wk4 dependentsMITTS
@devframes/service-opennpm

Devframe wire service that opens files in the user's editor or reveals them in the OS file explorer.

37.3K/wk1 dependentsMITTS
@vitest/mockernpm

Vitest module mocker implementation

0/wk3 dependentsMITTS
@vitejs/devtoolsnpm

Vite DevTools

0/wk2 dependentsMITTS
@vitest/snapshotnpm

Vitest snapshot manager

0/wk2 dependentsMITTS
@vitest/browsernpm

Browser running for Vitest

0/wk7 dependentsMITTS
@devframes/hubnpm

Hub layer that orchestrates devframe docks, terminals, messages, and commands on any host.

0/wk7 dependentsMITTS
@vitest/runnernpm

Vitest test runner

0/wk4 dependentsMITTS
jitinpm

Runtime typescript and ESM support for Node.js

0/wk15 dependentsMITTS
@devframes/plugin-terminalsnpm

Devframe plugin providing terminal panels for streamed output and interactive PTY shells.

0/wk1 dependentsMITTS
pkg-typesnpm

Node.js utilities and TypeScript definitions for `package.json` and `tsconfig.json`

0/wk4 dependentsMITTS
@vitejs/devtools-vitenpm

DevTools for Vite (work in progress)

0/wk1 dependentsMITTS
@vitejs/devtools-oxcnpm

DevTools for the Oxc toolchain

0/wk1 dependentsMITTS
nypmnpm

Unified Package Manager for Node.js

0/wk3 dependentsMITTS
devframenpm

Framework for building one portable devtool integration that runs in any viewer.

0/wk14 dependentsMITTS
@vitest/coverage-v8npm

V8 coverage provider for Vitest

0/wk52 dependentsMITTS
@vitest/coverage-istanbulnpm

Istanbul coverage provider for Vitest

0/wk4 dependentsMITTS

Relationship graph

Dependencies (left) and dependents (right) of pathe.

Frequently installed together

Release history

4 releases in the last two years, typically about 19 days apart.

Recent versions of pathe
VersionPublishedSizeLicense
2.0.3latest1 year ago50 KBMIT
2.0.21 year ago50 KBMIT
2.0.11 year ago49 KBMIT
2.0.01 year ago52 KBMIT
1.1.22 years ago30 KBMIT
1.1.13 years ago25 KBMIT
1.1.03 years ago25 KBMIT
1.0.13 years ago23 KBMIT
1.0.03 years ago22 KBMIT
0.3.93 years ago22 KBMIT
0.3.84 years ago22 KBMIT
0.3.74 years ago22 KBMIT
0.3.64 years ago22 KBMIT
0.3.54 years ago20 KBMIT
0.3.44 years ago20 KBMIT

Overview

pathe is an npm package that universal filesystem path utils. It has 25 known dependents in the graph. The latest version is 2.0.3, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need universal filesystem path utils 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

Frequently asked questions

Should I use pathe?

pathe is usable, with caveats. Last published 575 days ago. 4 releases in the last 2 years.

How do I install pathe?

Run `npm install pathe` to add pathe to your npm project.

What license is pathe released under?

pathe is distributed under the MIT license.

How popular is pathe?

npm does not publish download counts. Within PackageGraph's crawl, 25 known packages depend on pathe.

Is pathe still maintained?

The most recent release of pathe (v2.0.3) was published 1 year ago.

Does pathe run install scripts?

No. pathe does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.