


A definitive JS roundup on JavaScript modules: ES Modules vs CommonJS
Jul 02, 2025 am 01:28 AMES模塊和CommonJS的主要區(qū)別在于加載方式和使用場景。1. CommonJS是同步加載,適用于Node.js服務(wù)器端環(huán)境;2. ES模塊是異步加載,適用于瀏覽器等網(wǎng)絡(luò)環(huán)境;3. 語法上,ES模塊使用import/export,且必須位于頂層作用域,而CommonJS使用require/module.exports,可在運(yùn)行時動態(tài)調(diào)用;4. CommonJS廣泛用于舊版Node.js及依賴它的庫如Express,ES模塊則適用于現(xiàn)代前端框架和Node.js v14+;5. 雖然可混合使用,但容易引發(fā)問題,建議項(xiàng)目中統(tǒng)一使用一種方式;6. 使用ES模塊時需注意文件擴(kuò)展名、路徑處理等細(xì)節(jié)問題。
If you're working with JavaScript and have run into modules, you've probably seen terms like ES Modules and CommonJS floating around. They’re both ways to organize and share code across files, but they work differently and are used in different environments. Here’s a straightforward breakdown of the main differences and when to use each.

What's the big difference between ES Modules and CommonJS?
The core difference is when things happen — CommonJS loads modules synchronously, while ES Modules load them asynchronously. That might sound abstract, but it affects how your code behaves and where you can use each system.

CommonJS was designed for server-side JavaScript (like Node.js), where files are read from disk quickly, so waiting for one module to finish loading before moving on isn't a problem.
ES Modules, on the other hand, were built with browsers in mind. Since fetching files over the network takes time, ES Modules are structured to handle that better by loading in a way that doesn’t block everything else.

How do import and export syntax differ?
This is where most developers notice the biggest difference day-to-day.
In ES Modules:
You use import
and export
like this:
// math.js export const add = (a, b) => a + b; // main.js import { add } from './math.js';
These statements are static, meaning you can’t put them inside conditionals or functions. This helps tools like bundlers optimize your code during build time.
In CommonJS:
You use require()
and module.exports
:
// math.js exports.add = (a, b) => a + b; // or module.exports = { add: (a, b) => a + b, }; // main.js const math = require('./math'); const add = math.add;
Here, require()
can be called anywhere — even inside loops or if statements — because it runs at runtime.
Which one works where?
Use CommonJS when:
- You're writing Node.js code that doesn't use
"type": "module"
inpackage.json
- You're using older versions of Node.js (before ES Module support)
- You're working with tools like Express or Mongoose that historically rely on CommonJS
Use ES Modules when:
- You're building frontend apps (React, Vue, etc.)
- You're using modern Node.js versions (v14+) and want to write cleaner, future-proof code
- You're building libraries that need to be tree-shakable or used in both browser and Node.js environments
Note: If you're using a bundler like Webpack or Vite, you're likely already using ES Modules under the hood.
Can you mix ES Modules and CommonJS?
Technically yes, but it gets messy fast. Node.js allows you to mix them using certain flags or file extensions (mjs
vs cjs
), but doing so can lead to confusion and bugs.
For example, importing a CommonJS module into an ES Module works fine most of the time, but exporting from an ES Module and trying to use it in CommonJS might give you unexpected results unless you use await import()
.
So unless you have a very good reason, stick to one style per project.
A few gotchas to watch out for
- File extensions matter more in ES Modules — you usually need to include
.js
when importing. -
__dirname
andpath
usage is trickier in ES Modules; you’ll often need to useimport.meta.url
andnew URL()
instead. - Some older packages on npm still use CommonJS, which may cause issues if you're enforcing strict ESM mode.
That’s basically it. It’s not rocket science, but understanding these differences helps avoid confusion — especially as more tools shift toward ES Modules by default.
The above is the detailed content of A definitive JS roundup on 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)

Hot Topics

JavaScript's garbage collection mechanism automatically manages memory through a tag-clearing algorithm to reduce the risk of memory leakage. The engine traverses and marks the active object from the root object, and unmarked is treated as garbage and cleared. For example, when the object is no longer referenced (such as setting the variable to null), it will be released in the next round of recycling. Common causes of memory leaks include: ① Uncleared timers or event listeners; ② References to external variables in closures; ③ Global variables continue to hold a large amount of data. The V8 engine optimizes recycling efficiency through strategies such as generational recycling, incremental marking, parallel/concurrent recycling, and reduces the main thread blocking time. During development, unnecessary global references should be avoided and object associations should be promptly decorated to improve performance and stability.

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

Which JavaScript framework is the best choice? The answer is to choose the most suitable one according to your needs. 1.React is flexible and free, suitable for medium and large projects that require high customization and team architecture capabilities; 2. Angular provides complete solutions, suitable for enterprise-level applications and long-term maintenance; 3. Vue is easy to use, suitable for small and medium-sized projects or rapid development. In addition, whether there is an existing technology stack, team size, project life cycle and whether SSR is needed are also important factors in choosing a framework. In short, there is no absolutely the best framework, the best choice is the one that suits your needs.

IIFE (ImmediatelyInvokedFunctionExpression) is a function expression executed immediately after definition, used to isolate variables and avoid contaminating global scope. It is called by wrapping the function in parentheses to make it an expression and a pair of brackets immediately followed by it, such as (function(){/code/})();. Its core uses include: 1. Avoid variable conflicts and prevent duplication of naming between multiple scripts; 2. Create a private scope to make the internal variables invisible; 3. Modular code to facilitate initialization without exposing too many variables. Common writing methods include versions passed with parameters and versions of ES6 arrow function, but note that expressions and ties must be used.

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)

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.
