# Is @babel/cli ESM-only? Can you require() it?

> @babel/cli@8.0.4 has no importable main entry. No JavaScript entry point.

Babel command line.

Last verified Sep 9, 2026 against @babel/cli@8.0.4.

@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

1. 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.
2. TypeScript: no types are available for @babel/cli; declare the module yourself if you need them.

## Facts

- Latest: 8.0.4 (Jul 9, 2026)
- Module format: No JS entry point
- Last CommonJS version: 7.29.7
- TypeScript types: none
- Node engines: ^22.18.0 || >=24.11.0
- Weekly downloads: 3.5M
- License: MIT

## Runtime test results for @babel/cli@8.0.4

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 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Node.js 20 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Node.js 22 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Node.js 24 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Node.js 26 | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) | fails (ERR_PACKAGE_PATH_NOT_EXPORTED) |
| Bun 1.4.0 | fails (Error) | fails (Error) |

## How to import @babel/cli

ES modules:

```js
import * as cli from "@babel/cli";
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (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

- [@babel/cli on npm](https://www.npmjs.com/package/@babel/cli)
- [Source repository](https://github.com/babel/babel)
- [HTML version](https://canirequire.com/package/@babel/cli/)
- [JSON version](https://canirequire.com/package/@babel/cli.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.