Why i like ESM?
ESM module system is modern javascript's official module system. It is natively supported by all the modern browsers we have now. Also this module system is statically analyzable which makes it easy to make tools optimized. ESM can reduce bundle sizes through better tree-shaking support.
We can use ESM by using type: "module" in the package.json file or using .mjs extension. Since its natively supported by all the browsers also it is optimized not only just for node.js but also all the other javascript runtimes like bun, deno and javascript frameworks & libraries.
ESM module system is getting really popular in recent modern projects, Creating a great sustainable ecosystem for developers.
Let's Talk about CommonJS
It's not like i hate CommonJS. CommonJS played a huge role in growth of the Node.js ecosystem and it is still widely used today.
A lot of existing Node.js applications, libraries and large production codebases were built with CommonJS. So if you're working on an older project, maintaining an exisiting product, or using a package that relies on CommonJS then you'll likely use it.
That's why both module system are important in my opinion.
For new projects i personally prefer ESM. But in real-world development, the right choice depends on the existing codebase, dependencies, runtime, and project requirements.
You don't need to choose one and forget the other. Learn both, understand their differences, and know when to use each one.
Top comments (0)