# Is path-parse ESM-only? Can you require() it?

> path-parse@1.0.7 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

Node.js path.parse() ponyfill

Last verified Sep 9, 2026 against path-parse@1.0.7.

path-parse ships CommonJS only. require("path-parse") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "path-parse" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

## What to do

1. require("path-parse") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
2. From ES modules use the default import: import pathParse from "path-parse"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: npm install -D @types/path-parse

## Facts

- Latest: 1.0.7 (May 25, 2021)
- Module format: CommonJS
- Last CommonJS version: 1.0.7
- TypeScript types: @types/path-parse
- Node engines: not declared
- Weekly downloads: 95.2M
- License: MIT

## Runtime test results for path-parse@1.0.7

Installed and executed on Sep 9, 2026 with require("path-parse") from a CommonJS file and import "path-parse" from an ES module.

| Runtime | require("path-parse") | import "path-parse" |
|---|---|---|
| Node.js 18 | works | works |
| Node.js 20 | works | works |
| Node.js 22 | works | works |
| Node.js 24 | works | works |
| Node.js 26 | works | works |
| Bun 1.4.0 | works | works |

## How to import path-parse

ES modules:

```js
import pathParse from "path-parse";
```

CommonJS:

```js
const pathParse = require("path-parse");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (8 versions; the newest 8 shown).

| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.0.7 | CommonJS | Apr 17, 2015 |

## Frequently asked

**Is path-parse ESM-only?**

path-parse@1.0.7 is a CommonJS package. path-parse ships CommonJS only. require("path-parse") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "path-parse" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

**Can I import path-parse with ES module syntax?**

Yes. import pathParse from "path-parse" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.

**Does path-parse work in Bun?**

Yes. import "path-parse" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does path-parse ship TypeScript types?**

Not bundled. Install the community types with "npm install -D @types/path-parse".

## Links

- [path-parse on npm](https://www.npmjs.com/package/path-parse)
- [Source repository](https://github.com/jbgutierrez/path-parse)
- [HTML version](https://canirequire.com/package/path-parse/)
- [JSON version](https://canirequire.com/package/path-parse.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.