Working with JavaScript Module Systems (ESM vs CommonJS)
Jul 21, 2025 am 12:03 AMCommonJS is suitable for Node.js backend projects, adopts synchronous loading and value copying methods, and uses require/module.exports; ESM is a standard module system that supports asynchronous loading and dynamic references, which is more suitable for front-end and modern tool chains; when choosing, it should be decided based on the project type, environment and tool support. ESM is preferred for the front-end, and CommonJS can be selected for the back-end; the two can coexist in the same project, but attention should be paid to issues such as extension, configuration and circular dependencies.
JavaScript module system plays an important role in modern development, especially the two mainstream solutions: ESM (ECMAScript Modules) and CommonJS. They each have applicable scenarios, and there are some key differences. Understanding their differences and usage can help you organize your code structure more efficiently.

What is CommonJS? What situations are suitable?
CommonJS is a module specification introduced in Node.js in the early days. It adopts synchronous loading method, syntax uses require()
to introduce modules and exports content using module.exports
.

// Export exports.myFunc = function() { /*...*/ }; // Or another way to write module.exports = { myFunc: function() {} }; // Introduce const utils = require('./utils');
It is very suitable for server-side development, such as projects in Node.js environments, because synchronous loading is not a problem for the local file system. But that also means it is not very suitable for browser environments, especially when there was no native support module loading in the early days.
It should be noted that the CommonJS module is a value copy when importing, which means that the exported content will not change with the change of the source module after importing.

What is ESM? Why is it more recommended to use now?
ESM, which is the official ECMA standard module system, uses import
and export
to handle module dependencies. It is loaded asynchronously by default, which is more suitable for the browser environment and supports static analysis, which helps optimize the work of packaging tools.
// Export export function myFunc() {} // Or export the whole export default { myFunc }; //Introduce import { myFunc } from './utils.js';
Compared with CommonJS, one of the major advantages of ESM is that it is a language-level standard and therefore has better cross-platform compatibility. In addition, ESM uses dynamic references , which means that the imported variables will be consistent with the source module. If the source module updates a certain value, changes will also be seen in the import.
Currently, most modern browsers and build tools (such as Webpack and Vite) have fully supported ESM, and Node.js also supports ESM stably since version 14.
How to choose ESM or CommonJS?
This problem actually depends on your project type and running environment:
- If you are working on front-end projects (React, Vue, Svelte, etc.), or want to use Tree-shaking to optimize volume, you should prioritize ESM.
- If you are writing a pure Node.js backend service and do not require browser compatibility, CommonJS is still a simple and stable option.
- Mixed use situation : Some projects may contain both ESM and CommonJS modules. At this time, you need to pay attention to the setting of
"type": "module"
in package.json, otherwise you may encounter errors.
In addition, in Node.js, ESM can be used with .mjs
extension and CommonJS can be used with .cjs
, so that two module systems can coexist in the same project.
Common pitfalls and precautions
- The extension cannot be omitted : In ESM, the imported file must be equipped with
.js
or.mjs
extension, otherwise an error will be reported. - Top-level await can only be used in ESM : This is a convenient feature of ESM, but is not allowed in CommonJS.
- Differences in toolchain configuration : For example, tools such as Babel and Webpack handle the two differently, and the configuration needs to be adjusted according to the module system.
- Circular Dependency Issue : While both may encounter Circular Dependency problems, ESM is usually more clearer to handle than CommonJS.
Basically that's it. Module systems may seem simple, but understanding their behavioral differences is important for writing robust, maintainable code.
The above is the detailed content of Working with JavaScript Module Systems (ESM 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)

There are three common ways to initiate HTTP requests in Node.js: use built-in modules, axios, and node-fetch. 1. Use the built-in http/https module without dependencies, which is suitable for basic scenarios, but requires manual processing of data stitching and error monitoring, such as using https.get() to obtain data or send POST requests through .write(); 2.axios is a third-party library based on Promise. It has concise syntax and powerful functions, supports async/await, automatic JSON conversion, interceptor, etc. It is recommended to simplify asynchronous request operations; 3.node-fetch provides a style similar to browser fetch, based on Promise and simple syntax

JavaScript data types are divided into primitive types and reference types. Primitive types include string, number, boolean, null, undefined, and symbol. The values are immutable and copies are copied when assigning values, so they do not affect each other; reference types such as objects, arrays and functions store memory addresses, and variables pointing to the same object will affect each other. Typeof and instanceof can be used to determine types, but pay attention to the historical issues of typeofnull. Understanding these two types of differences can help write more stable and reliable code.

Hello, JavaScript developers! Welcome to this week's JavaScript news! This week we will focus on: Oracle's trademark dispute with Deno, new JavaScript time objects are supported by browsers, Google Chrome updates, and some powerful developer tools. Let's get started! Oracle's trademark dispute with Deno Oracle's attempt to register a "JavaScript" trademark has caused controversy. Ryan Dahl, the creator of Node.js and Deno, has filed a petition to cancel the trademark, and he believes that JavaScript is an open standard and should not be used by Oracle

CacheAPI is a tool provided by the browser to cache network requests, which is often used in conjunction with ServiceWorker to improve website performance and offline experience. 1. It allows developers to manually store resources such as scripts, style sheets, pictures, etc.; 2. It can match cache responses according to requests; 3. It supports deleting specific caches or clearing the entire cache; 4. It can implement cache priority or network priority strategies through ServiceWorker listening to fetch events; 5. It is often used for offline support, speed up repeated access speed, preloading key resources and background update content; 6. When using it, you need to pay attention to cache version control, storage restrictions and the difference from HTTP caching mechanism.

Promise is the core mechanism for handling asynchronous operations in JavaScript. Understanding chain calls, error handling and combiners is the key to mastering their applications. 1. The chain call returns a new Promise through .then() to realize asynchronous process concatenation. Each .then() receives the previous result and can return a value or a Promise; 2. Error handling should use .catch() to catch exceptions to avoid silent failures, and can return the default value in catch to continue the process; 3. Combinators such as Promise.all() (successfully successful only after all success), Promise.race() (the first completion is returned) and Promise.allSettled() (waiting for all completions)

JavaScript array built-in methods such as .map(), .filter() and .reduce() can simplify data processing; 1) .map() is used to convert elements one to one to generate new arrays; 2) .filter() is used to filter elements by condition; 3) .reduce() is used to aggregate data as a single value; misuse should be avoided when used, resulting in side effects or performance problems.

JavaScript's event loop manages asynchronous operations by coordinating call stacks, WebAPIs, and task queues. 1. The call stack executes synchronous code, and when encountering asynchronous tasks, it is handed over to WebAPI for processing; 2. After the WebAPI completes the task in the background, it puts the callback into the corresponding queue (macro task or micro task); 3. The event loop checks whether the call stack is empty. If it is empty, the callback is taken out from the queue and pushed into the call stack for execution; 4. Micro tasks (such as Promise.then) take precedence over macro tasks (such as setTimeout); 5. Understanding the event loop helps to avoid blocking the main thread and optimize the code execution order.

Event bubbles propagate from the target element outward to the ancestor node, while event capture propagates from the outer layer inward to the target element. 1. Event bubbles: After clicking the child element, the event triggers the listener of the parent element upwards in turn. For example, after clicking the button, it outputs Childclicked first, and then Parentclicked. 2. Event capture: Set the third parameter to true, so that the listener is executed in the capture stage, such as triggering the capture listener of the parent element before clicking the button. 3. Practical uses include unified management of child element events, interception preprocessing and performance optimization. 4. The DOM event stream is divided into three stages: capture, target and bubble, and the default listener is executed in the bubble stage.
