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. JSON
CommonJS CommonJS — require() works on every Node.js version
@typescript-eslint/parser ships CommonJS only. require("@typescript-eslint/parser") works everywhere. 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.
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.
| Runtime | require("@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 | ✓ 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 (407 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 8.34.0 – 8.70.0 | CommonJS | Jun 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 everywhere. 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 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
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- @vitest/utils 5.0.0ESM-only
- @babel/traverse 8.0.4ESM-only
- @pkgjs/parseargs 0.11.0CommonJS
- @floating-ui/core 1.8.0Dual
- @babel/plugin-syntax-jsx 8.0.1ESM-only
- @floating-ui/dom 1.8.0Dual
- @babel/code-frame 8.0.0ESM-only
- @typescript-eslint/eslint-plugin 8.70.0CommonJS