# Is tsconfig-paths ESM-only? Can you require() it?

> tsconfig-paths@4.2.0 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

Load node modules according to tsconfig paths, in run-time or via API.

Last verified Sep 9, 2026 against tsconfig-paths@4.2.0.

tsconfig-paths ships CommonJS only. require("tsconfig-paths") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6. import "tsconfig-paths" 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("tsconfig-paths") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6.
2. From ES modules use the default import: import tsconfigPaths from "tsconfig-paths"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 4.2.0 (Mar 29, 2023)
- Module format: CommonJS
- Last CommonJS version: 4.2.0
- TypeScript types: bundled
- Node engines: >=6
- Weekly downloads: 73.1M
- License: MIT

## Runtime test results for tsconfig-paths@4.2.0

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

| Runtime | require("tsconfig-paths") | import "tsconfig-paths" |
|---|---|---|
| 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 tsconfig-paths

ES modules:

```js
import tsconfigPaths from "tsconfig-paths";
```

CommonJS:

```js
const tsconfigPaths = require("tsconfig-paths");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 0.4.0 – 4.2.0 | CommonJS | Dec 30, 2016 |

## Frequently asked

**Is tsconfig-paths ESM-only?**

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

Yes. import tsconfigPaths from "tsconfig-paths" 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 tsconfig-paths work in Bun?**

Yes. import "tsconfig-paths" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does tsconfig-paths ship TypeScript types?**

Yes. tsconfig-paths bundles its own type declarations; no @types package is needed.

## Links

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