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

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

Resole and parse `tsconfig.json`, replicating to TypeScript's behaviour

Last verified Sep 9, 2026 against tsconfig@7.0.0.

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

## Facts

- Latest: 7.0.0 (Aug 28, 2017)
- Module format: CommonJS
- Last CommonJS version: 7.0.0
- TypeScript types: bundled
- Node engines: not declared
- Weekly downloads: 3.0M
- License: MIT

## Runtime test results for tsconfig@7.0.0

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

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

ES modules:

```js
import tsconfig from "tsconfig";
```

CommonJS:

```js
const tsconfig = require("tsconfig");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 0.0.1 – 7.0.0 | CommonJS | Jan 20, 2015 |

## Frequently asked

**Is tsconfig ESM-only?**

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

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

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

**Does tsconfig ship TypeScript types?**

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

## Links

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