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

> @babel/node@8.0.1 has no importable main entry. No JavaScript entry point.

Babel command line

Last verified Sep 9, 2026 against @babel/node@8.0.1.

@babel/node 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/node: it has no JavaScript entry point. Use it as a CLI (npx @babel/node), a stylesheet, an asset, or a type-definition package as its README describes.
2. TypeScript: no types are available for @babel/node; declare the module yourself if you need them.

## Facts

- Latest: 8.0.1 (Jun 17, 2026)
- Module format: No JS entry point
- Last CommonJS version: n/a
- TypeScript types: none
- Node engines: ^22.18.0 || >=24.11.0
- Weekly downloads: 659K
- License: MIT

## Runtime test results for @babel/node@8.0.1

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

| Runtime | require("@babel/node") | import "@babel/node" |
|---|---|---|
| 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/node

ES modules:

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

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 7.8.0 – 8.0.1 | No JS entry point | Jan 12, 2020 |

## Frequently asked

**Is @babel/node ESM-only?**

@babel/node@8.0.1 has no importable main entry. @babel/node 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/node work in Bun?**

Importing @babel/node failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module '@babel/node' from '/Users/boat/Projects/top-seo/data/probe-work/@babel__node/imp.mjs'

**Does @babel/node ship TypeScript types?**

No. @babel/node ships no type declarations and there is no @types package for it.

## Links

- [@babel/node on npm](https://www.npmjs.com/package/@babel/node)
- [Source repository](https://github.com/babel/babel)
- [HTML version](https://canirequire.com/package/@babel/node/)
- [JSON version](https://canirequire.com/package/@babel/node.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.