CommonJS vs ES Modules in Node.js: Key Differences and Usage

In Node.js, CommonJS uses require() and module.exports for synchronous module loading, while ES Modules use import and export with asynchronous loading and static analysis. ES Modules are the modern standard supported natively since Node.js 12+, offering better compatibility with frontend JavaScript.

Quick Comparison

This table summarizes the main differences between CommonJS and ES Modules in Node.js.

Feature	CommonJS	ES Modules
Syntax	require(), module.exports	import, export
Loading	Synchronous	Asynchronous
File Extension	.js (default), .cjs for explicit CommonJS	.mjs or "type": "module" in package.json
Support in Node.js	Supported since start	Stable since Node.js 12+
Interop	Can import ES Modules with dynamic import	Can import CommonJS with default import
Static Analysis	No (dynamic require)	Yes (imports are static)

Key Differences

CommonJS modules use require() to load modules synchronously at runtime, which means the code runs step-by-step and modules are loaded when the code reaches the require call. This makes it simple but less optimized for modern tools.

ES Modules use import and export statements that are static and loaded asynchronously before the code runs. This allows better optimization, tree shaking, and compatibility with browsers.

In Node.js, ES Modules require either the .mjs file extension or setting "type": "module" in package.json. CommonJS remains the default for .js files unless overridden. Interoperability between the two systems is possible but requires care, such as using dynamic import() to load ES Modules from CommonJS.

Code Comparison

javascript

const message = require('./message');

console.log(message);

Output

Hello from CommonJS!

ES Modules Equivalent

javascript

import message from './message.js';

console.log(message);

Output

Hello from ES Modules!

When to Use Which

Choose CommonJS when working on existing Node.js projects or packages that rely on synchronous loading and compatibility with older tools. It is simpler for scripts and quick setups.

Choose ES Modules for new projects aiming for modern JavaScript features, better optimization, and compatibility with frontend code. ES Modules are the future standard and recommended for long-term projects.

Key Takeaways

ES Modules use static import/export and load asynchronously, unlike CommonJS's synchronous require().

CommonJS is the default in Node.js but ES Modules are stable and recommended for modern projects.

Use .mjs or "type": "module" in package.json to enable ES Modules.

Interop between CommonJS and ES Modules is possible but requires dynamic import or default imports.

Choose ES Modules for future-proof code and CommonJS for legacy or simple scripts.