canirequire

canirequire › CommonJS › @babel/plugin-proposal-export-namespace-from

Is @babel/plugin-proposal-export-namespace-from ESM-only? Can you require() it?

Compile export namespace to ES2015

Last verified Sep 9, 2026 against @babel/plugin-proposal-export-namespace-from@7.18.9. JSON

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

@babel/plugin-proposal-export-namespace-from ships CommonJS only. require("@babel/plugin-proposal-export-namespace-from") works everywhere. import "@babel/plugin-proposal-export-namespace-from" 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.

Latest
7.18.9 (Jul 18, 2022)
Module format
CommonJS
Last CommonJS version
7.18.9
TypeScript types
None
Node engines
>=6.9.0
License
MIT

Deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.

Does @babel/plugin-proposal-export-namespace-from@7.18.9 actually load? Runtime test results

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

Runtimerequire("@babel/plugin-proposal-export-namespace-from")import "@babel/plugin-proposal-export-namespace-from"
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✓ works✓ works

How to import @babel/plugin-proposal-export-namespace-from

ES modules (import)

import pluginProposalExportNamespaceFrom from "@babel/plugin-proposal-export-namespace-from";

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 pluginProposalExportNamespaceFrom = require("@babel/plugin-proposal-export-namespace-from");

Module format by version

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

VersionsFormatFirst published
7.0.0 – 7.18.9CommonJSAug 27, 2018

Frequently asked

Is @babel/plugin-proposal-export-namespace-from ESM-only?

@babel/plugin-proposal-export-namespace-from@7.18.9 is a CommonJS package. @babel/plugin-proposal-export-namespace-from ships CommonJS only. require("@babel/plugin-proposal-export-namespace-from") works everywhere. import "@babel/plugin-proposal-export-namespace-from" 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-proposal-export-namespace-from with ES module syntax?

Yes. import pluginProposalExportNamespaceFrom from "@babel/plugin-proposal-export-namespace-from" 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-proposal-export-namespace-from work in Bun?

Yes. import "@babel/plugin-proposal-export-namespace-from" loaded successfully in Bun 1.4 on Sep 9, 2026.

Does @babel/plugin-proposal-export-namespace-from ship TypeScript types?

No. @babel/plugin-proposal-export-namespace-from ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity