Modern tools and libraries have increasingly adopted ESM as the primary module format, reducing the need for dual CJS/ESM packages. Transitioning to ESM-only simplifies development, reduces maintenance overhead, and improves package optimization. While careful consideration is needed when moving legacy packages, new packages should be released as ESM-only to leverage the benefits of modern tooling. The gradual adoption of ESM in the ecosystem is evident, and tools like Node Modules Inspector help in analyzing dependencies for a smoother transition.
Table of contents
The Toolings are Ready #The Troubles with Dual Formats #When Should We Move to ESM-only? #How Far We Are? #Moving Forward #Sort: