canirequire › No JS entry point › @babel/cli
Is @babel/cli ESM-only? Can you require() it?
Babel command line.
Last verified Sep 9, 2026 against @babel/cli@8.0.4. Markdown · JSON
No JS entry point No JavaScript entry point
@babel/cli 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 @babel/cli: it has no JavaScript entry point. Use it as a CLI (npx @babel/cli), a stylesheet, an asset, or a type-definition package as its README describes.
- TypeScript: no types are available for @babel/cli; declare the module yourself if you need them.
Does @babel/cli@8.0.4 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@babel/cli") from a CommonJS file and import "@babel/cli" from an ES module.
| Runtime | require("@babel/cli") | import "@babel/cli" |
|---|---|---|
| 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 @babel/cli
ES modules (import)
import * as cli from "@babel/cli";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 (87 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 8.0.0 – 8.0.4 | No JS entry point | Jun 16, 2026 |
| 7.11.5 – 7.29.7 | CommonJS | Aug 31, 2020 |
Frequently asked
Is @babel/cli ESM-only?
@babel/cli@8.0.4 has no importable main entry. @babel/cli 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 @babel/cli work in Bun?
Importing @babel/cli failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module '@babel/cli' from '/Users/boat/Projects/top-seo/data/probe-work/@babel__cli/imp.mjs'
Does @babel/cli ship TypeScript types?
No. @babel/cli ships no type declarations and there is no @types package for it.
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
- @eslint/core 1.2.1No entry
- @octokit/types 18.0.0No entry
- @octokit/openapi-types 29.0.1No entry
Similar popularity
- @angular/animations 22.1.5ESM-only
- @angular/platform-browser-dynamic 22.1.5ESM-only
- markdown-it-anchor 10.0.0CommonJS
- popper.js 1.16.1CommonJS
- vite-plugin-dts 5.1.0Dual
- pug 3.0.4CommonJS
- @changesets/cli 3.0.2ESM-only
- webpack-manifest-plugin 6.0.1ESM-only