Node.js Modules and the require System

Node.js uses a module system to keep code organised. Instead of putting everything in one giant file, you split your application into separate files — each responsible for one thing — and connect them using require and module.exports. This is the CommonJS module system, and it is what Node.js uses by default. Every file you create in your Express server is a module. Understanding how modules work is fundamental to reading and writing any Node.js code, and it determines how you structure your entire MERN backend.

What Is a Module? #

In Node.js, every .js file is automatically treated as a module. Each module has its own private scope — variables and functions defined in one file are not visible to other files unless you explicitly export them. This prevents naming conflicts and makes each file self-contained and testable.

Exporting and Importing — Basic Patterns #

// ── Exporting a single value ──────────────────────────────────────────────────
// server/src/config/db.js
const mongoose = require('mongoose');

const connectDB = async () => {
  await mongoose.connect(process.env.MONGODB_URI);
  console.log('MongoDB connected');
};

module.exports = connectDB;   // export a single function

// ── Importing a single value ─────────────────────────────────────────────────
// server/index.js
const connectDB = require('./src/config/db');   // .js extension is optional
connectDB();

// ── Exporting multiple values ─────────────────────────────────────────────────
// server/src/utils/helpers.js
const slugify = (text) => text.toLowerCase().replace(/\s+/g, '-');
const capitalize = (text) => text.charAt(0).toUpperCase() + text.slice(1);

module.exports = { slugify, capitalize };   // export an object

// ── Importing multiple values ─────────────────────────────────────────────────
const { slugify, capitalize } = require('./utils/helpers');
console.log(slugify('Hello World'));    // hello-world
console.log(capitalize('mern stack')); // Mern stack

The require() Resolution Algorithm #

When you call require('something'), Node.js resolves it in this order:

1. Is it a core module? (fs, path, http, crypto...)
   → Load the built-in module immediately

2. Does the path start with ./ or ../  or  / ?
   → It is a local file — resolve relative to the current file
   → Try: something.js  →  something.json  →  something/index.js

3. Otherwise — look in node_modules:
   → ./node_modules/something
   → ../node_modules/something
   → ../../node_modules/something   (walks up until root)
   → Throw MODULE_NOT_FOUND if not found anywhere

Structuring a MERN Server with Modules #

server/
├── index.js                  ← requires config/db, routes, middleware
├── src/
│   ├── config/
│   │   └── db.js             ← exports connectDB function
│   ├── models/
│   │   └── Post.js           ← exports Post Mongoose model
│   ├── controllers/
│   │   └── postController.js ← exports { getAllPosts, createPost, ... }
│   ├── routes/
│   │   └── posts.js          ← exports Express Router
│   └── middleware/
│       └── auth.js           ← exports protect middleware function

// ── How the modules connect ───────────────────────────────────────────────────

// server/src/controllers/postController.js
const Post = require('../models/Post');  // ← requires the model

const getAllPosts = async (req, res) => {
  const posts = await Post.find();
  res.json({ success: true, data: posts });
};

module.exports = { getAllPosts };

// server/src/routes/posts.js
const express    = require('express');
const router     = express.Router();
const { getAllPosts } = require('../controllers/postController'); // ← requires controller

router.get('/', getAllPosts);
module.exports = router;   // ← exports the router

// server/index.js
const express  = require('express');
const app      = express();
app.use('/api/posts', require('./src/routes/posts')); // ← requires the router

Core Modules You Will Use in MERN #

Common Mistakes #

Mistake 1 — Wrong path in require() #

❌ Wrong — forgetting the leading dot on a local file path:

const connectDB = require('src/config/db');
// Error: Cannot find module 'src/config/db'
// Node thinks it is an npm package, not a local file

✅ Correct — always use ./ or ../ for local files:

const connectDB = require('./src/config/db');   // relative to current file ✓

Mistake 2 — Circular dependencies #

❌ Wrong — file A requires file B, and file B requires file A:

userController.js → requires → postModel.js
postModel.js      → requires → userController.js   ← circular!
// Node.js will partially load one of them — hard-to-debug undefined errors

✅ Correct — restructure so data flows in one direction. Models should never require controllers. Controllers require models — not the other way around.

Mistake 3 — Modifying module.exports after assignment #

❌ Wrong — assigning to module.exports then trying to add properties to exports:

module.exports = connectDB;   // replaces exports with a function
exports.helper = someHelper;  // ignored — exports no longer === module.exports

✅ Correct — pick one style per file. Either assign to module.exports directly, or add all properties to the exports shorthand — never mix them:

module.exports = { connectDB, helper: someHelper };  // clean single assignment ✓

Quick Reference #