canirequire

canirequire › No JS entry point › @babel/node

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

Babel command line

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

No JS entry point No JavaScript entry point

@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.
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

Does @babel/node@8.0.1 actually load? Runtime test results

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

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

ES modules (import)

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

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

VersionsFormatFirst published
7.8.0 – 8.0.1No JS entry pointJan 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

Other no js entry point packages

Similar popularity