</>PackageGraphPackageGraph

path-parse

npmv1.0.7

Node.js path.parse() ponyfill

Not recommended for new projects

No — path-parse should not be adopted for new projects. Last published 1933 days ago.

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

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1933 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 4.4 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 path-parse 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.

4.4 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
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the path-parse README.

jsFull README ↗
var pathParse = require('path-parse');

pathParse('/home/user/dir/file.txt');
//=> {
//       root : "/",
//       dir : "/home/user/dir",
//       base : "file.txt",
//       ext : ".txt",
//       name : "file"
//   }

path-parse vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
path-parsethis page01MIT5 years ago
env-paths02MIT1 day ago
locate-path01MIT1 day ago
mime136.4M6MIT1 day ago
normalize-path72.6M1MIT1 day ago
unicorn-magic31.6M1MIT1 day ago

Used by

Popular packages that depend on path-parse.

resolvenpm

resolve like require.resolve() on behalf of files asynchronously and synchronously

↓ 0/wk◈ 2 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of path-parse.

resolvepath-parse
path-parse dependencies dependents

Frequently installed together

eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS
supports-preserve-symlinks-flagnpm

Determine if the current node version supports the `--preserve-symlinks` flag.

↓ 46.3M/wk◈ 1 dependents⚖ MIT
semvernpm

The semantic version parser used by npm.

↓ 0/wk◈ 55 dependents⚖ ISC
jitinpm

Runtime typescript and ESM support for Node.js

↓ 0/wk◈ 15 dependents⚖ MITTS
es-errorsnpm

A simple cache for a few of the JS Error constructors.

↓ 0/wk◈ 15 dependents⚖ MITTS
is-core-modulenpm

Is this specifier a node.js core module?

↓ 0/wk◈ 1 dependents⚖ MIT

Release history

No releases in the last two years, typically about 0 days apart.

Recent versions of path-parse
VersionPublishedSizeLicense
1.0.7latest5 years ago4.4 KBMIT
1.0.68 years ago8.8 KBMIT
1.0.511 years ago—MIT
1.0.411 years ago—MIT
1.0.311 years ago—MIT
1.0.211 years ago—MIT
1.0.111 years ago—MIT
1.0.011 years ago—MIT

Overview

path-parse is an npm package that node.js path.parse() ponyfill. It has 1 known dependents in the graph. The latest version is 1.0.7, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need node.js path.parse() ponyfill and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).
  • Zero runtime dependencies — minimal footprint.

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

jbgutierrez

Keywords

built-incoredirfileparsepathpathspolyfillponyfillshimutilutils

Frequently asked questions

Should I use path-parse?

No — path-parse should not be adopted for new projects. Last published 1933 days ago.

How do I install path-parse?

Run `npm install path-parse` to add path-parse to your npm project.

What license is path-parse released under?

path-parse is distributed under the MIT license.

How popular is path-parse?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on path-parse.

Is path-parse still maintained?

The most recent release of path-parse (v1.0.7) was published 5 years ago.

Does path-parse run install scripts?

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