canirequire

canirequire › CommonJS › eslint-module-utils

Is eslint-module-utils ESM-only? Can you require() it?

Core utilities to support eslint-plugin-import and other module-related plugins.

Last verified Sep 9, 2026 against eslint-module-utils@2.14.0. JSON

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

eslint-module-utils ships CommonJS only. require("eslint-module-utils") works everywhere. import "eslint-module-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.

Latest
2.14.0 (Jul 3, 2026)
Module format
CommonJS
Last CommonJS version
2.14.0
TypeScript types
None
Node engines
>=4
Weekly downloads
42.7M
License
MIT

Does eslint-module-utils@2.14.0 actually load? Runtime test results

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

Runtimerequire("eslint-module-utils")import "eslint-module-utils"
Node.js 18✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 20✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 22✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 24✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Node.js 26✗ failsERR_PACKAGE_PATH_NOT_EXPORTED✗ failsERR_PACKAGE_PATH_NOT_EXPORTED
Bun 1.4✗ failserror: Cannot find package 'eslint-module-utils' from '/Users/boat/Projects/top-seo/data/probe-work/eslint-module-utils/req.cjs'✗ failserror: Cannot find package 'eslint-module-utils' from '/Users/boat/Projects/top-seo/data/probe-work/eslint-module-utils/imp.mjs'

A failing require() on a CommonJS package usually means the package needs a browser/DOM global, a peer dependency, or a native binary that is not available in a bare Node.js process.

How to import eslint-module-utils

ES modules (import)

import eslintModuleUtils from "eslint-module-utils";

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 eslintModuleUtils = require("eslint-module-utils");

Module format by version

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

VersionsFormatFirst published
0.1.0 – 2.14.0CommonJSMar 29, 2016

Frequently asked

Is eslint-module-utils ESM-only?

eslint-module-utils@2.14.0 is a CommonJS package. eslint-module-utils ships CommonJS only. require("eslint-module-utils") works everywhere. import "eslint-module-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 eslint-module-utils with ES module syntax?

Yes. import eslintModuleUtils from "eslint-module-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 eslint-module-utils work in Bun?

Importing eslint-module-utils failed in Bun 1.4 on Sep 9, 2026: error: Cannot find package 'eslint-module-utils' from '/Users/boat/Projects/top-seo/data/probe-work/eslint-module-utils/imp.mjs'

Does eslint-module-utils ship TypeScript types?

No. eslint-module-utils ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity