Modules Team

Purpose

The Node.js Modules Team maintains and actively develops the ESModules (ESM) implementation in Node.js Core.

Work includes:

Based on these use cases (#55), our implementation aims to support the following features (subject to change):

Spec compliance (#132)
Browser equivalence (#133)
No refactoring (#87)
Pluggable Loaders to support multiple use cases (#82)
Named exports when importing CJS (#81)
Dual-goal packages (#93)
Multi-mode packages (#94)
Code coverage/instrumentation (#95)
Runtime loaders, transpilation at import time (#96)
Arbitrary sources for module source text (#97)
Mock modules (injection) (#98)
Mixed module types within app/module; gradual migration from CommonJS to ESM (#99)
Transparent interoperability for ESM importing CommonJS (#100)
Polyfillability (#101)
Tree shaking (#102)
File / path / URL resolving (#103)
Retrievable module metadata (#104)
Transparent migration (#105)
WASM modules (#106)
Browser and Node compatibility without building (#107)
Browser-compatible build that includes CommonJS (#108)
Browser-compatible specifier resolution (#109)
Specifier resolution customization (#110)
Package encapsulation (#111)
Don’t break CommonJS (#112)
Conditional imports (#113)
Import JSON without needing asynchronous syntax (#114)
Importing non-JavaScript files (#115)
Import CommonJS without needing asynchronous syntax (#116)
NodeJS contextual pathing use cases (#121)