Understanding Node.js Express Routers as Middleware: Solving the 404 Issue

---

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---

The Problem

Let's say you've set up your Express application and created two routers: one for authentication (let's call it authRouter) and another for general routes (let’s name it generalRouter). Here's an outline of the steps you usually take:

Define Routers: You create authRouter and generalRouter for handling authorization and general routing respectively.

Set Up Routes: You define various routes, such as login for the authentication router and dashboard for the general router.

Attach Routers to the App: You add both routers to your Express application.

You expected the request handling to flow smoothly – if a route isn’t matched, the middleware should logically redirect to the notFoundHandler. Yet, that's not what happens. It seems like only the first router is shadowing the next. Let's find out why.

Why the Issue Occurs

The issue arises due to how middleware works in Express:

Order of Middleware: Middleware in Express processes requests in the order they are defined. If your authRouter is matched first, it can handle the request completely, leaving no room for subsequent routers or handlers, including your custom 404 error handler.

Not Calling next(): When using routers as middleware, if you don’t call next() in your route handlers, the request flow halts. Thus, even if your second router has potential routes, they can’t be reached if the first router handles the request entirely.

Solution to the Middleware Challenge

The solution to this problem is straightforward and involves ensuring that next() is called within your route handlers. Here’s how you can implement this solution:

Step 1: Set Up Your Routers

Make sure you define your routers properly:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Define Routes and Call next()

When defining your route handlers, remember to invoke next() where appropriate. Here’s an example of how to modify one of your handlers:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Attach Your Routers and the NotFoundHandler

When appending the routers to the main app, it should look like this:

[[See Video to Reveal this Text or Code Snippet]]

By making sure to call next() in each of your route handlers, you allow the request to continue processing and reach the notFoundHandler if no routes match.

Conclusion

By modifying your middleware handlers to include calls to next(), you can make sure that no route handling is prematurely terminated, thus solving the 404 issue you encountered. Remember, the proper order and structure of middleware in your Express app are paramount to a smooth request handling process.