Registry / devops / babel-plugin-dynamic-import-node

babel-plugin-dynamic-import-node

JSON →
library2.3.3jsnpmunverified

This Babel plugin, `babel-plugin-dynamic-import-node`, transpiles ECMAScript `import()` expressions into deferred CommonJS `require()` calls specifically for Node.js environments. Its primary purpose is to enable the use of modern dynamic `import()` syntax in projects targeting Node.js versions that do not natively support ESM dynamic imports, or in mixed CommonJS/ESM contexts where asynchronous loading of CommonJS modules is required. The current stable version is 2.3.3, with its last significant updates occurring around 2019. While still functional for legacy projects, its necessity has largely diminished with the widespread adoption of native ESM support in modern Node.js versions and the capabilities of `@babel/preset-env` to handle dynamic imports for various targets. Key differentiators include its focus solely on `import()` to `require()` transformation, offering specific control over interoperability via the `noInterop` option.

devops
npm install babel-plugin-dynamic-import-node
github ↗package ↗
INSTALL
IMPORT
SIG · BABEL-PLUGIN-DYNAM
B
babel-plugin-dynamic-import-node
devopsjavascriptv2.3.3
Install
—
Import
—
Disk
—
Pass rate
0/ 6
Env Coverage0 / 6
glibc
18–22
musl
18–22
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18–226 runs
build_error
glibc
node 18–226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

Config via .babelrc
✓ { "plugins": ["dynamic-import-node"] }
✗ import dynamicImportNode from 'babel-plugin-dynamic-import-node';
This plugin is loaded via Babel's configuration file (`.babelrc`, `babel.config.js`, etc.), not imported into application code.
Config with options
✓ { "plugins": [ ["dynamic-import-node", { "noInterop": true }] ] }
✗ { "plugins": [ "dynamic-import-node", { "noInterop": true } ] }
Plugin options must be provided as a second element in an array when specifying the plugin name in Babel configuration.
Node API usage
✓ const dynamicImportNode = require('babel-plugin-dynamic-import-node');
✗ import dynamicImportNode from 'babel-plugin-dynamic-import-node';
When using Babel's Node.js API, the plugin itself is typically required using CommonJS syntax.

Demonstrates how to use `babel-plugin-dynamic-import-node` via the Node.js API to transpile dynamic `import()` calls into `require()` for execution in a Node.js environment.

const babel = require('@babel/core'); const fs = require('fs'); const path = require('path'); const inputCode = ` async function loadModules() { const [mod1, mod2] = await Promise.all([ import('./lib/module1.js'), import('./lib/module2.js') ]); console.log('Module 1:', mod1.default); console.log('Module 2:', mod2.message); } loadModules(); `; // Create dummy modules for demonstration fs.mkdirSync(path.join(__dirname, 'lib'), { recursive: true }); fs.writeFileSync(path.join(__dirname, 'lib', 'module1.js'), 'module.exports = { default: "Hello from Module 1!" };'); fs.writeFileSync(path.join(__dirname, 'lib', 'module2.js'), 'exports.message = "Greetings from Module 2!";'); try { const result = babel.transformSync(inputCode, { plugins: ['babel-plugin-dynamic-import-node'], filename: 'test.js' // Needed for relative imports }); console.log('Transpiled code:\n', result.code); // To run the transpiled code in Node.js, you'd typically save it to a file: // fs.writeFileSync('output.js', result.code); // require('./output.js'); } catch (error) { console.error('Babel transformation failed:', error); }
Debug
Known issues
gotchaThis plugin requires a specific version of Babel's parser, Babylon >= v6.12.0, to correctly parse dynamic imports. Using an older Babel core or parser may result in `SyntaxError`s when encountering `import()` expressions.
fix
Ensure you are using a compatible version of Babel (e.g., Babel 7 with `@babel/core` and `@babel/parser`) or at least `babel-core@^6.12.0` if on Babel 6.
affects: <=2.3.3
deprecatedThe primary use case for `babel-plugin-dynamic-import-node` has been largely superseded. Modern Node.js versions (12.x LTS and above, especially 14+) offer robust native ESM support for dynamic imports. Additionally, `@babel/preset-env` can handle `import()` transformations for various target environments, including Node.js, without requiring this specific plugin.
fix
For new projects or upgrades, consider leveraging native Node.js ESM or configuring `@babel/preset-env` with appropriate targets. This plugin is primarily relevant for maintaining older projects or specific legacy setups.
affects: >=1.0.0
gotchaWhen transpiling CommonJS modules that do not export a `default` property (which is common for many CJS modules), the transpiled `require('module').default` call can result in `undefined` or runtime errors. This often occurs when importing a CJS module that uses `module.exports = ...` or `exports.foo = ...`.
fix
Use the `noInterop: true` option for the plugin: `["dynamic-import-node", { "noInterop": true }]`. This will prevent the plugin from adding `.default` to the `require()` calls, allowing direct access to the CommonJS export.
affects: >=1.0.0
Errors
Common errors & fixes
SyntaxError: 'import' and 'export' may only appear at the top level
This error occurs when the Babel parser (Babylon) used by your setup is too old to understand the `import()` syntax, or if `babel-plugin-syntax-dynamic-import` (which this plugin implicitly depends on) is missing or not configured.
fix
Ensure your Babel configuration includes `babel-plugin-dynamic-import-node` and that your `@babel/core` (or `babel-core`) version is recent enough (e.g., Babel 7+). This plugin handles the necessary syntax parsing automatically.
TypeError: (0, _module.default) is not a function
This runtime error typically indicates that you are dynamically importing a CommonJS module that does not have a `default` export, but the plugin transpiled it assuming one. This is due to Babel's default interop behavior for `import` statements.
fix
Apply the `noInterop: true` option to the plugin configuration: `["dynamic-import-node", { "noInterop": true }]`. This directs the plugin to output `require()` calls without appending `.default`.
ReferenceError: require is not defined
This plugin specifically transpiles `import()` to `require()` for Node.js environments. If the transpiled code is run in a non-Node.js environment (e.g., a browser without a CommonJS shim like Webpack's), `require` will be undefined.
fix
Ensure the transpiled output is executed within a Node.js environment. If targeting browsers or other environments, consider using a different Babel setup or bundler-specific dynamic import solutions (e.g., Webpack's `import()` for code splitting).
Upgrade
Version history
2.3.3latest on npm
Audit
Dependencies
@babel/corerequiredRequired as the core Babel transpiler engine. This plugin integrates with Babel's parser (Babylon) and transform pipeline.
Agent activity
4 hits · last 30 days
node
4
Resources
githubhttps://github.com/airbnb/babel-plugin-dynamic-import-node ↗
packagehttps://www.npmjs.com/package/babel-plugin-dynamic-import-node ↗
babel-plugin-dynamic-import-node — npm install babel-plugin-dynamic-import-node · libregistry