How to organize your code like a pro using ES6 modules
The Problem: Why One Giant File Doesn’t Scale
When you first start learning JavaScript, it’s tempting to put everything in a single app.js file. It works fine for a small calculator or a to-do list. But what happens when your project grows?
Suddenly, you’re scrolling through hundreds of lines just to find one function. Variables accidentally overwrite each other because they share the same global scope. Debugging feels like searching for a needle in a haystack. And if you’re working with a teammate, merging changes becomes a nightmare.
Think of it like a kitchen where every ingredient, utensil, and recipe is thrown into one giant drawer. You can technically cook, but finding what you need wastes time and invites mistakes. This is the exact problem JavaScript modules were designed to solve.
What Are JavaScript Modules?
A module is simply a JavaScript file that focuses on doing one thing well. Instead of dumping all your code into one place, you split it into separate files. Each file can then share specific pieces of code with others using two keywords: export and import.
Modules give every file its own private scope. Variables and functions inside a module stay hidden unless you explicitly choose to share them. This means no more accidental global variable collisions, no more guessing where a function came from, and a much cleaner project structure.
Modern JavaScript uses ES6 Modules (ESM), which are built directly into the language. You don’t need extra tools to understand how they work.
Exporting: Sharing Functions and Values
To make code available outside its file, you use the export keyword. You can export functions, variables, objects, or classes.
Here’s how named exports work:
// mathUtils.js
export function add(a, b) {
return a + b;
}
export const PI = 3.14159;
Notice how each piece we want to share gets the export keyword. You can also group exports at the bottom of a file:
// mathUtils.js
function subtract(a, b) { return a - b; }
function multiply(a, b) { return a * b; }
export { subtract, multiply };
Exporting is like putting items on a store shelf. Only what you place on the shelf is available for others to take. Everything else stays in the back room.
Importing: Bringing Modules Into Your Code
Once you’ve exported something, you can bring it into another file using import. You’ll need to specify exactly what you want and where it’s coming from.
// app.js
import { add, PI } from './mathUtils.js';
console.log(add(2, 3)); // 5
console.log(PI); // 3.14159
A few important notes for beginners:
The curly braces {} must match the exact names you exported.
The file path usually starts with ./ (meaning “in the same folder”) and includes the .js extension.
Imports are static, meaning they’re resolved before your code runs. You can’t conditionally import inside an if statement with this syntax.
⚠️ Quick Setup Tip: Browsers block module imports when you open an HTML file directly from your folder (file://). To test modules locally, use a simple live server (like the VS Code Live Server extension) or add <script type="module" src="app.js"></script> in your HTML.
Importing is like checking out items from the store. You ask for exactly what you need, and JavaScript delivers it to your current file.
JavaScript gives you two ways to export: named exports and default exports. Knowing the difference will save you hours of debugging.
Named Exports (what we’ve used so far)
You can have multiple per file.
You must import them using curly braces: import { add } from './mathUtils.js';
The imported name must match the exported name.
Default Exports
Only one per file.
Best when a file represents a single main thing (like a main component or a core utility).
No curly braces when importing, and you can rename it on the fly:
// logger.js
export default function logMessage(msg) {
console.log(`[LOG]: ${msg}`);
}
// app.js
import log from './logger.js'; // No braces, custom name allowed
log('Hello modules!');
Quick Rule of Thumb: Use named exports for utility files with multiple functions. Use default exports when a file has one clear purpose. Many developers prefer sticking to named exports for consistency, and that’s perfectly fine too.
The Real Benefits of Modular Code
Splitting your code into modules isn’t just about following trends. It fundamentally changes how you write and maintain JavaScript:
Easier Debugging: When a bug appears, you know exactly which file to check. No more scanning a massive script.
Reusability: Export a function once, import it anywhere. Need that add function in three different projects? Just copy the module.
Team Collaboration: Multiple developers can work on separate modules without stepping on each other’s code.
Clear Dependencies: At the top of every file, import statements act like a table of contents. You instantly see what the file relies on.
Private Scope by Default: Variables stay contained unless explicitly exported. This prevents accidental overwrites and makes your code more predictable.
In short, modules turn a tangled mess of code into a well-organized toolbox.
Visualizing How Modules Work
(Add these diagrams to your blog using Hashnode’s image uploader, Excalidraw, or Draw.io)
Diagram 1: File Dependency Map Show app.js at the top with arrows pointing down to mathUtils.js, logger.js, and api.js. This helps beginners see that modules form a clean tree structure, not a spiderweb.
Diagram 2: Import/Export Flow Left: mathUtils.js with export function add()
Arrow labeled “export” → Middle: Module Boundary
Arrow labeled “import { add }” → Right: app.js using add()
This visual reinforces that code only crosses file boundaries when you explicitly allow it.
Conclusion & Your Turn
JavaScript modules might feel unfamiliar at first, especially if you’re used to writing everything in one file. But once you start splitting your code, you’ll wonder how you ever worked without them.
Start small: take a project you’ve already built, pick two or three functions, and move them into a separate file. Export them, import them back, and watch your code instantly become cleaner.
You don’t need bundlers, build tools, or complex configurations to understand modules. Just export, import, and a willingness to organize your code intentionally.
What’s the first file you’ll split into a module? Try it out, and share your experience in the comments. Happy coding!
