# esmod-pmb > Use esm (ES modules, import, export for Node v6) with less boilerplate. Latest version **0.1.15** (published 2026-04-15) · ISC license · 0 weekly downloads ## Install ```sh npm install esmod-pmb pnpm add esmod-pmb yarn add esmod-pmb bun add esmod-pmb ``` ## Health **Score 45/100 (D)** — status: stable. Positive: no vulnerabilities. Warnings: low downloads; no types; no esm support; pre 1.0. ## Facts | | | |---|---| | Version | 0.1.15 | | Published | 2026-04-15 | | First published | 2018-02-03 | | Weekly downloads | 0 | | License | ISC | | TypeScript types | none | | Module format | CommonJS | | Node | >=16.0.0 | | Dependencies | 2 | | Unpacked size | 18.7 KB | | Known vulnerabilities | 0 | | Install scripts | no | | GitHub stars | 0 | | Author | M.K. | | Maintainers | mk-pmb | ## Links - npm: https://www.npmjs.com/package/esmod-pmb - Repository: https://github.com/mk-pmb/esmod-pmb-js - Homepage: https://github.com/mk-pmb/esmod-pmb-js/#readme - Issues: https://github.com/mk-pmb/esmod-pmb-js/issues - npm.io page: https://npm.io/package/esmod-pmb ## Dependencies (2) - [esm](https://npm.io/package/esm.md) ^3.2.25 - [now-ymd](https://npm.io/package/now-ymd.md) ^0.1.0 ## Recent versions - 0.1.15 (latest) — 2026-04-15 - 0.1.13 — 2021-06-01 - 0.1.11 — 2020-01-05 - 0.1.10 — 2019-03-15 - 0.1.9 — 2019-03-15 - 0.1.8 — 2019-03-13 - 0.1.7 — 2018-08-31 - 0.1.6 — 2018-08-27 - 0.1.5 — 2018-04-15 - 0.1.3 — 2018-02-10 - 0.1.2 — 2018-02-09 - 0.1.1 — 2018-02-03 ## README esmod-pmb ========= Use esm (ES modules, import, export for Node v6) with less boilerplate. ⚠ DEPRECATED ⚠ -------------- As of 2026-04-15, this module is deprecated. I released a compatibility layer for Node.js v24 that you can use to make old software continue to work, but you should really upgrade your code base to instead embrace the native ESM support of Node.js v24 or later. ### What you'll have to update: * Clarify your `import` statements: * Use full filenames with explicit filename extension. * If you're already using `eslint-config-nodejs-pmb` as your eslint rules, it's eay: The rules package ships a script `util/massfix_missing_import_fext.sh` that will auto-fix probably all occurrences. Make sure your project repo is clean before you run it, then from the top of your project repo, run the fix script by full path. * If you import JSON files, declare the type, e.g. `import pkgInfo from './package.json' with { type: 'json' };` * Delete all bridge modules. * In all places where you had mentioned a bridge module (probably in your `package.json`), write the `.mjs` file instead. * In all places where you called `nodemjs` (probably in your `package.json`), call Node.js directly instead. * Properly declare that your project now requires Node.js v24 or later (probably in your `package.json` and docs). ### How to mute the deprecation warning If you don't want to deal with the deprecation warning today, you can mute it by setting environment variable `ESMODPMB_IGNORE_DEPRECATION_UNTIL` to a six-digit date (yymmdd). ----- The next few sections are kept for historians. They explain why and how this module was useful for ancient Node.js versions. ----- Usage ----- Let's assume you have an ES module like [`usage.mjs`](test/usage.mjs): ```javascript import dfOnly from './default-export-only'; import * as named from './named-exports-only'; export default dfOnly; export const { foo, answer } = named; ``` … and you want to use it from old node's CommonJS realm. The `esm` module can do it: ```javascript module.exports = require('esm')(module)('./usage.mjs') ``` But that's still a bit too much boilerplate for my taste. Don't waste your time micro-managing the filename and whether you should add `.default` to the above formula! There's a much easier way: Make a bridge module with almost the same name, except it ends with `.node.js` instead of `.mjs` (thus here, [`usage.node.js`](test/usage.node.js)): ```javascript require('esmod-pmb')(module); ``` It should work out of the box: ```bash $ nodejs -p "require('./usage.node.js')" { foo: [Getter], answer: [Getter], default: [Getter] } ``` To see values instead of getters, copy them to another object: ```bash $ nodejs -p "Object.assign({}, require('./usage.node.js'))" { foo: 23, answer: 42, default: { isDefaultExport: true, bar: 5 } } ``` For modules that have a default export and no named exports, like [`default-export-only.mjs`](test/default-export-only.mjs): ```javascript export default { isDefaultExport: true, bar: 5 }; ``` … your bridge module will export that as the top level: ```bash $ nodejs -p "require('./default-export-only.node.js')" { isDefaultExport: true, bar: 5 } $ nodejs -p "require('esm')(module)('./default-export-only.mjs')" { default: [Getter] } ``` API --- ```javascript // standard: require('esmod-pmb')(module); // custom options: require('esmod-pmb')(module, { preferDefaultExport: false }); // detailed: var bridgeBuilder = require('esmod-pmb'); var opt = { reexport: false }; var esmRequire = bridgeBuilder(module, opt); var yourEsModule = esmRequire('./yourmodule.mjs'); ``` This module exports one function: ### esmRqr = bridgeBuilder(baseModule[, opt]) Returns an ESM-capable `require`-like function obtained from `esm`. The optional options object `opt` can be used to modify the default options. If you need custom options for something you consider "normal"/"usual", please file an issue so we can try to provide better defaults. After all, the purpose of this module is to _reduce_ boilerplate. That said, `bridgeBuilder` uses the same options object as `esm`, so you can use all of its options, and some additional ones: * `reexport`: (bool, default: true) Whether `bridgeBuilder` shall do its main magic: 1. guess the name of your ES module, 1. import it, 1. (skippable) resolve the imported bindings 1. and "re-export" them, i.e. assign the imported values to `baseModule.exports`. * Set to `false` to opt-out of the main magic, but still get an `esmRqr` with the combined options based on this module's defaults. Options used only when `reexport` is enabled: * `stripSuffixes`: (regexp) and `addSuffix` (string, default: `".mjs"`) To guess the ES module filename, the `bridgeBuilder` removes the part matched by `stripSuffixes` and appends `addSuffix`. * `resolveImportedValues`: (bool, default: `true`) Whether to resolve (copy) the imported values. Set to `false` if you prefer getter functions. Sane modules usually shouldn't mutate their exports, so usually resolving them makes life easier by reducing the amount of magic involved. * `preferDefaultExport`: Determines which of the ESM exports shall be re-export into CommonJS land. * `false` = all of them. The re-export will be a dictionary (object). If the ES module only has a default export, the dictionary will contain only one key, `default`. * `true` = only the default export. If the ES module doesn't have a default export, the re-export will be `undefined`. * `1` (as a number; also the default) = automatic. The re-export will be a dictionary with all exports, except in case there is only one single export and its name is `default`; in that case, that default export will be re-exported directly. Known issues ------------ * Needs more/better tests and docs.   License ------- ISC --- _Source: https://npm.io/package/esmod-pmb · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._