canirequire

canirequire › CommonJS › babel-plugin-component

Is babel-plugin-component ESM-only? Can you require() it?

Modular build plugin for babel.

Last verified Sep 9, 2026 against babel-plugin-component@1.1.1. Markdown · JSON

CommonJS CommonJS — require() works on every Node.js version we test

babel-plugin-component ships CommonJS only. require("babel-plugin-component") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "babel-plugin-component" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

What to do

  1. require("babel-plugin-component") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
  2. From ES modules use the default import: import babelPluginComponent from "babel-plugin-component"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for babel-plugin-component; declare the module yourself if you need them.
Latest
1.1.1 (May 8, 2018)
Module format
CommonJS
Last CommonJS version
1.1.1
TypeScript types
None
Node engines
not declared
Weekly downloads
28K
License
MIT

Does babel-plugin-component@1.1.1 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("babel-plugin-component") from a CommonJS file and import "babel-plugin-component" from an ES module.

Runtimerequire("babel-plugin-component")import "babel-plugin-component"
Node.js 18✓ works✓ works
Node.js 20✓ works✓ works
Node.js 22✓ works✓ works
Node.js 24✓ works✓ works
Node.js 26✓ works✓ works
Bun 1.4.0✓ works✓ works

How to import babel-plugin-component

ES modules (import)

import babelPluginComponent from "babel-plugin-component";

Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.

CommonJS (require)

const babelPluginComponent = require("babel-plugin-component");

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

VersionsFormatFirst published
0.1.1 – 1.1.1CommonJSMay 25, 2016

Frequently asked

Is babel-plugin-component ESM-only?

babel-plugin-component@1.1.1 is a CommonJS package. babel-plugin-component ships CommonJS only. require("babel-plugin-component") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "babel-plugin-component" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

Can I import babel-plugin-component with ES module syntax?

Yes. import babelPluginComponent from "babel-plugin-component" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.

Does babel-plugin-component work in Bun?

Yes. import "babel-plugin-component" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does babel-plugin-component ship TypeScript types?

No. babel-plugin-component ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity