Modular Express Routing With Router

Express.Router splits routes across files, but mounting order and param inheritance can trip you up. This post shows a concrete setup and the one flag you need.

The Problem of Scattered Routes

When an Express application grows beyond a single file, route handlers multiply, middleware ordering becomes a guessing game, and parameter handling feels scattered. You find yourself scrolling through one massive app.js file, searching for where a URL pattern is defined, and wondering why a newly added middleware isn't affecting a specific route. This is the concrete problem many Node.js teams face as their services scale.

Router to the Rescue

Express.Router creates a mini‑application that carries its own middleware stack, route handlers, and parameter processing. You define it in a separate file, mount it at a path prefix, and the main app remains clean. Each router is independent: its own use() calls apply only within that router unless you explicitly share them.

Parameter names in router paths (for example, /users/:id) are accessible via req.params and support regex constraints, enabling reusable route patterns across modules. Since Express 4.0, Router is built‑in and does not require extra packages; it works with all current LTS Node.js versions (>=14) and maintains backward compatibility.

// routes/users.js
const express = require('express')
const router = express.Router()
router.get('/:id', (req, res) => {
  res.json({ userId: req.params.id })
})
module.exports = router

Mounting Order and Middleware Inheritance

The most common pitfall is assuming that middleware defined after app.use('/api', router) still runs for routes inside that router. In Express, middleware placed before the mount runs for the router's routes; middleware placed after does not, unless the router explicitly uses it. This ordering rule means you must decide where to put global middlewares like express.json() relative to your router mounts. If you place express.json() after the mount, body‑parsed data will not be available to router handlers.

Nested Params and mergeParams

When a child router needs access to parameters from a parent route, Express does not share req.params by default. The mergeParams option solves this: mount the child router with the mergeParams: true flag, and once enabled, req.params.id from the parent becomes available in the child's handlers. Be aware that enabling mergeParams merges the parent's params into the child's req.params, so plan your parameter names accordingly to avoid collisions.

Verification and Gotchas

Create a minimal Express app: mkdir express-router-demo && cd express-router-demo, npm init -y, npm i express.
Define a router in a separate file (e.g., routes/users.js) with a GET /:id handler.
Mount it in your main app: app.use('/api/users', usersRouter).
Start the server: node app.js.
Send a request: curl http://localhost:3000/api/users/123. Expect {userId: \"123\"} if the router is mounted before express.json() or if body parsing isn't needed.
Check middleware ordering: place app.use(express.json()) before the mount to ensure router routes receive parsed bodies; move it after and verify the request body is empty.

Getting Started Today

Start modularizing today: split your routes into separate files, mount them early in your app setup, and use mergeParams only when nested parameter access is truly needed. Verify each mount with a quick curl request and you'll keep your Express app both scalable and predictable.

Modular Express Routing With Router and mergeParams