canirequire

canirequire › CommonJS › codelyzer

Is codelyzer ESM-only? Can you require() it?

Linting for Angular applications, following angular.io/styleguide.

Last verified Sep 9, 2026 against codelyzer@6.0.2. Markdown · JSON

CommonJS CommonJS on paper — require() failed in our runtime test

codelyzer declares a CommonJS entry only, but require("codelyzer") failed on every Node.js version in our probe: ERR_PACKAGE_PATH_NOT_EXPORTED. import "codelyzer" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

What to do

  1. require("codelyzer") failed in our probe on every Node.js version (ERR_PACKAGE_PATH_NOT_EXPORTED); check the package README for peer dependencies or setup before relying on it.
  2. From ES modules use the default import: import codelyzer from "codelyzer"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for codelyzer; declare the module yourself if you need them.
Latest
6.0.2 (May 3, 2021)
Module format
CommonJS
Last CommonJS version
6.0.2
TypeScript types
None
Node engines
not declared
Weekly downloads
394K
License
MIT

Does codelyzer@6.0.2 actually load? Runtime test results

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

Runtimerequire("codelyzer")import "codelyzer"
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.0✗ failsError✗ failsError

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 codelyzer

ES modules (import)

import codelyzer from "codelyzer";

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)

// require("codelyzer") failed in our probe on every Node.js version we test (ERR_PACKAGE_PATH_NOT_EXPORTED); see the runtime table.
const codelyzer = require("codelyzer");

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 (56 versions; the newest 56 shown).

VersionsFormatFirst published
0.0.0 – 6.0.2CommonJSMar 24, 2016

Frequently asked

Is codelyzer ESM-only?

codelyzer@6.0.2 declares a CommonJS entry, but require() fails at runtime. codelyzer declares a CommonJS entry only, but require("codelyzer") failed on every Node.js version in our probe: ERR_PACKAGE_PATH_NOT_EXPORTED. import "codelyzer" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

Can I require codelyzer?

Not in practice. codelyzer declares a CommonJS entry, but require("codelyzer") failed on every Node.js version in our probe: ERR_PACKAGE_PATH_NOT_EXPORTED. Check the package README for peer dependencies or setup before relying on it.

Can I import codelyzer with ES module syntax?

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

Importing codelyzer failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module 'typescript/lib/typescript' from '/Users/boat/Projects/top-seo/data/probe-work/codelyzer/node_modules/codelyzer/importDestructuringSpacingRule.js'

Does codelyzer ship TypeScript types?

No. codelyzer ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity