Dynamic Modules Development in Node.js

[guybedford]

I wanted to just provide a brief update on the status of the dynamic modules specification in Node.js - https://github.com/nodejs/dynamic-modules.

This proposal is designed to support the use case of named exports from CommonJS when importing them from ES Modules:

import { exportName } from 'cjs-package';

The proposal is moving to final review stages with the details now all worked out as an ECMA-262 patch (tc39/ecma262#1306), Node.js specification (https://nodejs.github.io/dynamic-modules/) and v8 implementation (https://chromium-review.googlesource.com/c/v8/v8/+/1303725).

At the last Node.js modules group meeting there was consensus that the group would continue to support this work going forward. That does not mean that we will definitely use this approach in Node.js, but that we as a group are committed to continuing to develop this work as a viable path forward as we make the various decisions around ES modules interop.

It's important for TC39 and v8 to know that this is a proposal with the collective support of Node.js as a project, so I'm creating this issue to get wider feedback from everyone involved.

If anyone has any questions or concerns about the approach, or Node.js advocating this work further, please do let us know here.

[devsnek]

@nodejs/modules @nodejs/v8

[jdalton]

I'm not a fan of making export * from "cjs" throw.
Please see my comment nodejs/dynamic-modules#11 (comment).