Request: Update Node.js / ESM Documentation for 2025

[erifystudio]

Hello MDN team ✏️,

I noticed that some of the MDN docs around ECMAScript modules (ESM) and Node.js interoperability feel slightly out of sync with current 2025 practices. For example:
• The evolution of native ESM in Node.js (v20+ defaults).
• Details on using import maps, import.meta, and dynamic import() when bridging between Node.js and browsers.
• Guidance for developers migrating from CommonJS → ESM in modern stacks.

👉 Proposal: Could we refresh the ESM/Node-related content to better reflect the 2025 landscape and ensure the compatibility tables are up to date?

Thanks as always for keeping the docs sharp and future-proof 💎🔥

⚡ DC ERIFY | GERIZON 🧃🐐

[pransh15]

Hi @erifystudio 👋
Thanks for raising this! You’re right that the ecosystem has evolved a lot since ESM first landed in browsers and Node.js.

On MDN, we aim to document JavaScript language features (like import, export, import.meta, and dynamic import()) and their browser compatibility. What we don’t usually cover in depth are Node.js-specific runtime details (like package resolution, CommonJS interop rules, or Node’s defaults in v20+).

That said, some of our pages on ESM could certainly be updated to reflect today’s landscape more clearly, especially around import maps, interop notes, and guidance for developers migrating from CJS → ESM. I will share the discussion with the team for that, and they can share more on what we cover.

For Node-specific migration details, external guides like this one can complement what MDN covers.

Thanks again for helping us improve MDN!