The Guide to JavaScript Modules: ES Modules vs. CommonJS
Aug 01, 2025 am 02:23 AMES Modules (ESM) are the modern standard, while CommonJS is the older Node.js-style system; use ESM for new projects. 1) ESM uses import/export, is asynchronous, supports tree-shaking, and is natively supported in browsers and Node.js with "type": "module" or .mjs files. 2) CommonJS uses require() and module.exports, is synchronous, dynamic, and widely used in legacy Node.js code. 3) Node.js supports both, but mixing them can cause issues—prefer one per project. 4) For frontend code, ESM is required; for npm packages, consider supporting both via the exports field. 5) Dynamic imports (import()) in ESM allow conditional loading, bridging the gap with CommonJS. Ultimately, ESM is the future, but understanding CommonJS remains essential for working with older codebases and libraries.
JavaScript modules are a core part of modern development, helping you organize code into reusable, maintainable pieces. But with different module systems—especially ES Modules (ESM) and CommonJS—it can be confusing to know which to use and when. Let’s break it down in plain terms.
What Are JavaScript Modules?
A module is just a file that exports code (like functions, objects, or variables) so other files can import and use it. This avoids polluting the global scope and makes code easier to test and reuse.
Over time, two main module systems became popular:
-
CommonJS – the older, Node.js-style
require()
andmodule.exports
-
ES Modules (ESM) – the modern, standardized
import
andexport
syntax
They do similar things but work differently under the hood.
CommonJS: The Old Workhorse
CommonJS was created for server-side JavaScript (Node.js) before browsers had native module support.
Syntax Example:
// math.js function add(a, b) { return a b; } module.exports = { add }; // app.js const { add } = require('./math'); console.log(add(2, 3)); // 5
Key Traits:
- Uses
require()
to import andmodule.exports
orexports
to export - Synchronous loading – fine for servers, not ideal for browsers
- Dynamic: You can
require
anywhere, even inside functions or conditionals - Loads modules on demand at runtime
- Widely used in older Node.js projects and npm packages
? Fun fact: Node.js adopted CommonJS early because it needed a module system long before browsers did.
ES Modules (ESM): The Modern Standard
ES Modules are part of the official JavaScript language (since ES6/ES2015) and supported natively in modern browsers and recent Node.js versions.
Syntax Example:
// math.js export function add(a, b) { return a b; } // app.js import { add } from './math.js'; console.log(add(2, 3)); // 5
Key Traits:
- Uses
import
andexport
keywords - Asynchronous by design – better for browser loading and optimization
- Static: Imports are resolved at compile time (mostly), enabling tree-shaking
- Supports named exports and default exports
- Enables better bundling and dead-code elimination
Example of named vs default:
// Named export export const PI = 3.14; // Default export export default function() { ... } // Importing import myFunc, { PI } from './utils.js';
Key Differences at a Glance
Feature | CommonJS | ES Modules |
---|---|---|
Syntax | require() , module.exports | import , export |
Loading | Synchronous | Asynchronous / static |
When resolved | Runtime | Parse time (mostly) |
Dynamic imports | Yes (require() anywhere) | Limited (but import() exists) |
Tree-shaking support | No | Yes |
File extension | Usually no .js | Often requires .js in browser |
Browser support | No (without bundler) | Yes (modern browsers) |
Node.js support | Yes (legacy) | Yes (with .mjs or "type": "module" in package.json) |
How Node.js Handles Both
Node.js now supports both systems, but you need to opt into ESM.
To use ES Modules in Node.js:
- Rename file to
.mjs
, or - Add
"type": "module"
in yourpackage.json
{ "type": "module" }
Now you can use import/export
in .js
files.
If "type"
is not set or is "commonjs"
, Node treats .js
files as CommonJS.
?? Mixing ESM and CommonJS in the same project can cause issues. Stick to one when possible.
Practical Tips for Developers
Here’s what you should keep in mind today:
- New projects? Use ES Modules. It’s the future and works everywhere with proper tooling.
- Working in older Node.js code? You’ll likely see CommonJS — that’s fine.
- Publishing npm packages? Consider supporting both (via
exports
field or dual builds). - Browsers only support ESM natively. So if you’re writing frontend code, ESM is your only real option.
- Use
.mjs
for ESM and.cjs
for CommonJS if you want to mix them explicitly.
Example of dual package:
{ "main": "./index.cjs", "module": "./index.mjs", "exports": { "import": "./index.mjs", "require": "./index.cjs" } }
Dynamic Imports: Bridging the Gap
Even with static ESM, you can do dynamic imports:
if (condition) { const { something } = await import('./module.js'); }
This is useful for lazy-loading or conditional logic—similar to CommonJS’s dynamic require()
.
Bottom Line
- CommonJS is older, dynamic, and Node-first. Still common in legacy code.
- ES Modules are modern, static, and standard across browsers and Node.js.
- Use ESM for new projects — it’s faster, safer, and enables better tooling.
- Be aware of file extensions and
package.json
settings when using ESM in Node.
Basically, ESM won. But you’ll still run into CommonJS — especially in npm packages or older codebases. Knowing both helps you debug, migrate, and write compatible code.
Not complicated — just two eras of JavaScript meeting in the middle.
The above is the detailed content of The Guide to JavaScript Modules: ES Modules vs. CommonJS. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

The way to add drag and drop functionality to a web page is to use HTML5's DragandDrop API, which is natively supported without additional libraries. The specific steps are as follows: 1. Set the element draggable="true" to enable drag; 2. Listen to dragstart, dragover, drop and dragend events; 3. Set data in dragstart, block default behavior in dragover, and handle logic in drop. In addition, element movement can be achieved through appendChild and file upload can be achieved through e.dataTransfer.files. Note: preventDefault must be called

The reason why ARIA and HTML5 semantic tags are needed is that although HTML5 semantic elements have accessibility meanings, ARIA can supplement semantics and enhance auxiliary technology recognition capabilities. For example, when legacy browsers lack support, components without native tags (such as modal boxes), and state updates need to be dynamically updated, ARIA provides finer granular control. HTML5 elements such as nav, main, aside correspond to ARIArole by default, and do not need to be added manually unless the default behavior needs to be overridden. The situations where ARIA should be added include: 1. Supplement the missing status information, such as using aria-expanded to represent the button expansion/collapse status; 2. Add semantic roles to non-semantic tags, such as using div role to implement tabs and match them

The security risks of HTML5 applications need to be paid attention to in front-end development, mainly including XSS attacks, interface security and third-party library risks. 1. Prevent XSS: Escape user input, use textContent, CSP header, input verification, avoid eval() and direct execution of JSON; 2. Protect interface: Use CSRFToken, SameSiteCookie policies, request frequency limits, and sensitive information to encrypt transmission; 3. Secure use of third-party libraries: periodic audit dependencies, use stable versions, reduce external resources, enable SRI verification, ensure that security lines have been built from the early stage of development.

HTML5, CSS and JavaScript should be efficiently combined with semantic tags, reasonable loading order and decoupling design. 1. Use HTML5 semantic tags, such as improving structural clarity and maintainability, which is conducive to SEO and barrier-free access; 2. CSS should be placed in, use external files and split by module to avoid inline styles and delayed loading problems; 3. JavaScript is recommended to be introduced in front, and use defer or async to load asynchronously to avoid blocking rendering; 4. Reduce strong dependence between the three, drive behavior through data-* attributes and class name control status, and improve collaboration efficiency through unified naming specifications. These methods can effectively optimize page performance and collaborate with teams.

Using HTML5 semantic tags can improve web structure clarity, accessibility and SEO effects. 1. Semantic tags such as,,,, and make it easier for the machine to understand the page content; 2. Each tag has a clear purpose: used in the top area, wrap navigation links, include core content, display independent articles, group relevant content, place sidebars, and display bottom information; 3. Avoid abuse when using it, ensure that only one per page, avoid excessive nesting, reasonable use and in blocks. Mastering these key points can make the web page structure more standardized and practical.

Common reasons why HTML5 videos don't play in Chrome include format compatibility, autoplay policy, path or MIME type errors, and browser extension interference. 1. Videos should be given priority to using MP4 (H.264) format, or provide multiple tags to adapt to different browsers; 2. Automatic playback requires adding muted attributes or triggering .play() with JavaScript after user interaction; 3. Check whether the file path is correct and ensure that the server is configured with the correct MIME type. Local testing is recommended to use a development server; 4. Ad blocking plug-in or privacy mode may prevent loading, so you can try to disable the plug-in, replace the traceless window or update the browser version to solve the problem.

HTML5Canvas is suitable for web graphics and animations, and uses JavaScript to operate context drawing; ① First add canvas tags to HTML and get 2D context; ② Use fillRect, arc and other methods to draw graphics; ③ Animation is achieved by clearing the canvas, redrawing, and requestAnimationFrame loops; ④ Complex functions require manual processing of event detection, image drawing and object encapsulation.

Embed web videos using HTML5 tags, supports multi-format compatibility, custom controls and responsive design. 1. Basic usage: add tags and set src and controls attributes to realize playback functions; 2. Support multi-formats: introduce different formats such as MP4, WebM, Ogg, etc. through tags to improve browser compatibility; 3. Custom appearance and behavior: hide default controls and implement style adjustment and interactive logic through CSS and JavaScript; 4. Pay attention to details: Set muted and autoplay to achieve automatic playback, use preload to control loading strategies, combine width and max-width to achieve responsive layout, and use add subtitles to enhance accessibility.
