canirequire

canirequire › CommonJS › @typescript-eslint/parser

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

An ESLint custom parser which leverages TypeScript ESTree

Last verified Sep 9, 2026 against @typescript-eslint/parser@8.70.0. Markdown · JSON

CommonJS CommonJS — require() works on every Node.js version we test

@typescript-eslint/parser ships CommonJS only. require("@typescript-eslint/parser") 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/parser" 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/parser") 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 parser from "@typescript-eslint/parser"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
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
121.9M
License
MIT

Does @typescript-eslint/parser@8.70.0 actually load? Runtime test results

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

Runtimerequire("@typescript-eslint/parser")import "@typescript-eslint/parser"
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/parser

ES modules (import)

import parser from "@typescript-eslint/parser";

Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.

CommonJS (require)

const parser = require("@typescript-eslint/parser");

Module format by version

Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (407 versions; the newest 60 shown).

VersionsFormatFirst published
8.34.0 – 8.70.0CommonJSJun 9, 2025

Frequently asked

Is @typescript-eslint/parser ESM-only?

@typescript-eslint/parser@8.70.0 is a CommonJS package. @typescript-eslint/parser ships CommonJS only. require("@typescript-eslint/parser") 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/parser" 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/parser with ES module syntax?

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

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

Does @typescript-eslint/parser ship TypeScript types?

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

Links

Other commonjs packages

Similar popularity