# Is @typescript-eslint/utils ESM-only? Can you require() it?

> @typescript-eslint/utils@8.70.0 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

Utilities for working with TypeScript + ESLint together

Last verified Sep 9, 2026 against @typescript-eslint/utils@8.70.0.

@typescript-eslint/utils ships CommonJS only. require("@typescript-eslint/utils") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^18.18.0 || ^20.9.0 || >=21.1.0. import "@typescript-eslint/utils" 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("@typescript-eslint/utils") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^18.18.0 || ^20.9.0 || >=21.1.0.
2. From ES modules use the default import: import utils from "@typescript-eslint/utils"; 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.70.0 (Sep 7, 2026)
- Module format: CommonJS
- Last CommonJS version: 8.70.0
- TypeScript types: bundled
- Node engines: ^18.18.0 || ^20.9.0 || >=21.1.0
- Weekly downloads: 106.1M
- License: MIT

## Runtime test results for @typescript-eslint/utils@8.70.0

Installed and executed on Sep 9, 2026 with require("@typescript-eslint/utils") from a CommonJS file and import "@typescript-eslint/utils" from an ES module.

| Runtime | require("@typescript-eslint/utils") | import "@typescript-eslint/utils" |
|---|---|---|
| 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 @typescript-eslint/utils

ES modules:

```js
import utils from "@typescript-eslint/utils";
```

CommonJS:

```js
const utils = require("@typescript-eslint/utils");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 8.34.0 – 8.70.0 | CommonJS | Jun 9, 2025 |

## Frequently asked

**Is @typescript-eslint/utils ESM-only?**

@typescript-eslint/utils@8.70.0 is a CommonJS package. @typescript-eslint/utils ships CommonJS only. require("@typescript-eslint/utils") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^18.18.0 || ^20.9.0 || >=21.1.0. import "@typescript-eslint/utils" 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 @typescript-eslint/utils with ES module syntax?**

Yes. import utils from "@typescript-eslint/utils" 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 @typescript-eslint/utils work in Bun?**

Yes. import "@typescript-eslint/utils" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does @typescript-eslint/utils ship TypeScript types?**

Yes. @typescript-eslint/utils bundles its own type declarations; no @types package is needed.

## Links

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