canirequire › No JS entry point › @eslint/core
Is @eslint/core ESM-only? Can you require() it?
Runtime-agnostic core of ESLint
Last verified Sep 9, 2026 against @eslint/core@1.2.1. Markdown · JSON
No JS entry point No JavaScript entry point
@eslint/core does not expose a JavaScript entry point in package.json. It is likely a CLI, a stylesheet, a type-definition package, or an asset bundle, so require() and import are not the way to use it.
What to do
- Do not require() or import @eslint/core: it has no JavaScript entry point. Use it as a CLI (npx @eslint/core), a stylesheet, an asset, or a type-definition package as its README describes.
- TypeScript: types are bundled; install nothing extra.
Does @eslint/core@1.2.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@eslint/core") from a CommonJS file and import "@eslint/core" from an ES module.
| Runtime | require("@eslint/core") | import "@eslint/core" |
|---|---|---|
| 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 @eslint/core
ES modules (import)
import * as core from "@eslint/core";CommonJS (require)
Not applicable.
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 (26 versions; the newest 26 shown).
| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 1.2.1 | No JS entry point | Jun 26, 2024 |
Frequently asked
Is @eslint/core ESM-only?
@eslint/core@1.2.1 has no importable main entry. @eslint/core does not expose a JavaScript entry point in package.json. It is likely a CLI, a stylesheet, a type-definition package, or an asset bundle, so require() and import are not the way to use it.
Does @eslint/core work in Bun?
Importing @eslint/core failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module '@eslint/core' from '/Users/boat/Projects/top-seo/data/probe-work/@eslint__core/imp.mjs'
Does @eslint/core ship TypeScript types?
Yes. @eslint/core bundles its own type declarations; no @types package is needed.
Links
Other no js entry point packages
- type-fest 5.9.0No entry
- undici-types 8.10.2No entry
- node-releases 2.0.55No entry
- pnpm 12.3.4No entry
- csstype 3.2.3No entry
- @octokit/types 18.0.0No entry
- @octokit/openapi-types 29.0.1No entry
- @openai/codex 0.153.4No entry
Similar popularity
- toidentifier 1.0.1CommonJS
- axios 1.20.0Dual
- delayed-stream 1.0.0CommonJS
- imurmurhash 0.1.4CommonJS
- combined-stream 1.0.8CommonJS
- @jest/schemas 30.5.0Dual
- wrappy 1.0.2CommonJS
- @typescript-eslint/utils 8.70.0CommonJS