Route matching order matters in Express - Mini Project: Build & Apply

Route matching order matters

📖 Scenario: You are building a simple Express server that responds to different URL paths. The order in which you define routes affects which response the server sends.

🎯 Goal: Learn how to define routes in Express so that the server matches the correct route based on the order they are written.

📋 What You'll Learn

Create an Express app with three routes: a specific route, a parameter route, and a catch-all route

Define a variable to hold the port number

Use the correct order of route definitions so the server responds properly

Add the final line to start the server listening on the port

💡 Why This Matters

🌍 Real World

Web servers often have many routes. Defining them in the right order ensures users get the correct pages.

💼 Career

Backend developers must understand route matching to build reliable APIs and web servers.

1

Set up Express app and routes

Create an Express app by requiring express and calling it to get app. Then define three routes in this order: /about that sends "About page", /user/:id that sends "User ID: " plus the id parameter, and a catch-all * route that sends "Page not found".

Express

const express = require('express');
const app = express();

// Your code here

Hint

Remember to require Express and create the app first. Then add the three routes in the order given.

2

Add port configuration

Create a constant called port and set it to 3000.

Express

const express = require('express');
const app = express();

app.get('/about', (req, res) => {
  res.send('About page');
});

app.get('/user/:id', (req, res) => {
  res.send('User ID: ' + req.params.id);
});

app.get('*', (req, res) => {
  res.send('Page not found');
});

// Your code here

Hint

Just add a constant named port and assign it the number 3000.

3

Reorder routes to show matching order importance

Move the catch-all app.get('*', ...) route to be the first route defined, before /about and /user/:id. Keep the rest of the code unchanged.

Express

const express = require('express');
const app = express();

// Your code here to move the catch-all route first

const port = 3000;

Hint

Cut the catch-all route and paste it before the other two routes.

4

Start the server listening

Add app.listen(port) with a callback that sends console message Server running on port 3000.

Express

const express = require('express');
const app = express();

app.get('*', (req, res) => {
  res.send('Page not found');
});

app.get('/about', (req, res) => {
  res.send('About page');
});

app.get('/user/:id', (req, res) => {
  res.send('User ID: ' + req.params.id);
});

const port = 3000;

// Your code here to start the server

Hint

Use app.listen with port and a callback that logs the message.

Practice

1. In Express, why does the order of route definitions matter?
app.get('/user', ...) and app.get('/:id', ...) are defined. Which route will handle /user if /:id is defined first?

easy

A. The most specific route always handles the request regardless of order.

B. Express matches all routes and runs all handlers regardless of order.

C. The first matching route in order handles the request, so /:id will handle /user.

D. Express throws an error if routes overlap.

Solution

1. Step 1: Understand Express route matching order

   Express checks routes in the order they are defined and stops at the first match.

2. Step 2: Analyze the given routes

   If /:id is defined before /user, the path /user matches /:id first, so that handler runs.

3. Final Answer:

   The first matching route in order handles the request, so /:id will handle /user. -> Option C

4. Quick Check:

   Route order controls matching = C [OK]

Hint: Remember: Express uses first match wins rule [OK]

Common Mistakes:

• Thinking Express runs all matching routes
• Assuming specific routes override order automatically
• Believing Express throws errors on overlapping routes

2. Which of the following is the correct way to define routes so that /about is handled before any dynamic /:page route in Express?

easy

A. app.get('/:page', handler); app.get('/about', handler);

B. app.get('/about', handler); app.get('/:page', handler);

C. app.get('/about', handler); app.use('/:page', handler);

D. app.use('/:page', handler); app.get('/about', handler);

Solution

1. Step 1: Recall route order importance

   Specific routes like /about must be defined before dynamic routes like /:page to match first.

2. Step 2: Check options for correct order

   app.get('/about', handler); app.get('/:page', handler); defines /about first, then /:page, ensuring /about matches before dynamic routes.

3. Final Answer:

   app.get('/about', handler); app.get('/:page', handler); -> Option B

4. Quick Check:

   Specific before dynamic = A [OK]

Hint: Put specific routes before dynamic ones [OK]

Common Mistakes:

• Defining dynamic routes before specific ones
• Using app.use instead of app.get for specific routes
• Assuming order doesn't affect matching

3. Given the following Express routes:

app.get('/product/:id', (req, res) => res.send('Product ' + req.params.id));
app.get('/product/list', (req, res) => res.send('Product List'));

What will be the response when a client requests /product/list?

medium

A. 'Product List'

B. 'Product list'

C. 404 Not Found

D. Error: Route conflict

Solution

1. Step 1: Check route order

   The dynamic route /product/:id is defined before the specific /product/list route.

2. Step 2: Determine which route matches first

   Request /product/list matches /product/:id first, so it returns 'Product list'.

3. Step 3: Check case sensitivity

   The specific route sends 'Product List' with capital 'L', while the dynamic route sends 'Product ' + id, which would be 'Product list' if matched.

4. Final Answer:

   'Product List' -> Option A

5. Quick Check:

   Specific route matches only if defined before dynamic [OK]

Hint: First matching route runs, order matters for specific vs dynamic [OK]

Common Mistakes:

• Assuming specific route matches first regardless of order
• Expecting 404 when dynamic route matches
• Thinking Express throws route conflict errors

4. You have these Express routes:

app.get('/:category', handler1);
app.get('/books', handler2);

Requests to /books always go to handler1. How do you fix this?

medium

A. Move app.get('/books', handler2) before app.get('/:category', handler1).

B. Change /:category to /category/:name.

C. Use app.use instead of app.get for /books.

D. Rename /books to /books/all.

Solution

1. Step 1: Identify route order problem

   The dynamic route /:category matches /books first because it is defined before the specific route.

2. Step 2: Fix by reordering routes

   Moving the specific /books route before the dynamic one ensures /books matches handler2 first.

3. Final Answer:

   Move app.get('/books', handler2) before app.get('/:category', handler1). -> Option A

4. Quick Check:

   Specific routes before dynamic fix matching [OK]

Hint: Place specific routes above dynamic routes [OK]

Common Mistakes:

• Changing route paths unnecessarily
• Using app.use instead of app.get incorrectly
• Ignoring route order importance

5. You want to create an Express app where:
- /api/users returns a user list
- /api/:resource returns data for any resource

How should you order these routes to ensure /api/users returns the user list and /api/products returns product data?

hard

A. Define /api/:resource first, then /api/users.

B. Combine both routes into one with conditional logic inside.

C. Use app.use for /api/users and app.get for /api/:resource.

D. Define /api/users first, then /api/:resource.

Solution

1. Step 1: Understand route specificity and order

   Specific routes like /api/users must be defined before dynamic routes like /api/:resource to match correctly.

2. Step 2: Apply correct order

   Defining /api/users first ensures requests to /api/users hit that route, while other resources match the dynamic route.

3. Final Answer:

   Define /api/users first, then /api/:resource. -> Option D

4. Quick Check:

   Specific before dynamic for correct matching [OK]

Hint: Always put specific API routes before dynamic ones [OK]

Common Mistakes:

• Defining dynamic route before specific API routes
• Using app.use incorrectly for route handlers
• Trying to merge routes instead of ordering