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

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

Express style path to RegExp utility

Last verified Sep 9, 2026 against path-to-regexp@8.4.2.

path-to-regexp ships CommonJS only. require("path-to-regexp") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "path-to-regexp" 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-to-regexp") 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 pathToRegexp from "path-to-regexp"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 8.4.2 (Apr 1, 2026)
- Module format: CommonJS
- Last CommonJS version: 8.4.2
- TypeScript types: bundled
- Node engines: not declared
- Weekly downloads: 193.1M
- License: MIT

## Runtime test results for path-to-regexp@8.4.2

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

| Runtime | require("path-to-regexp") | import "path-to-regexp" |
|---|---|---|
| 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-to-regexp

ES modules:

```js
import pathToRegexp from "path-to-regexp";
```

CommonJS:

```js
const pathToRegexp = require("path-to-regexp");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 0.1.11 – 8.4.2 | CommonJS | Sep 12, 2024 |

## Frequently asked

**Is path-to-regexp ESM-only?**

path-to-regexp@8.4.2 is a CommonJS package. path-to-regexp ships CommonJS only. require("path-to-regexp") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "path-to-regexp" 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-to-regexp with ES module syntax?**

Yes. import pathToRegexp from "path-to-regexp" 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-to-regexp work in Bun?**

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

**Does path-to-regexp ship TypeScript types?**

Yes. path-to-regexp bundles its own type declarations; no @types package is needed.

## Links

- [path-to-regexp on npm](https://www.npmjs.com/package/path-to-regexp)
- [Source repository](https://github.com/pillarjs/path-to-regexp)
- [HTML version](https://canirequire.com/package/path-to-regexp/)
- [JSON version](https://canirequire.com/package/path-to-regexp.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.