Separating routes into files in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

Why should you separate routes into different files in an Express app?

Separating routes keeps code organized and easier to manage, especially as the app grows. It helps avoid a big messy file and makes it simpler to find and update routes.

beginner

What Express feature helps you create routes in separate files?

Express Router lets you create modular route handlers in separate files. You can define routes on a router and then use it in your main app file.

intermediate

How do you use a router from another file in your main Express app?

You export the router from the route file using module.exports, then import it in your main app file with require(), and use app.use() to add it to your app.

intermediate

What is the purpose of app.use('/path', router) in Express?

It tells Express to use the routes defined in the router for any requests starting with '/path'. This prefixes all routes in the router with '/path'.

beginner

Show a simple example of creating and exporting a router in a separate file.

In routes.js:
const express = require('express');
const router = express.Router();
router.get('/', (req, res) => res.send('Hello from router!'));
module.exports = router;

What Express method creates a new router to separate routes into files?

A express.Router()

B express.createRoute()

C express.newRouter()

D express.routeFile()

express.Router() creates a new router object to define routes separately.

How do you add routes from a router file to your main Express app?

A app.route(router)

B app.use('/path', router)

C app.addRouter(router)

D app.include(router)

app.use('/path', router) mounts the router on the specified path.

Which keyword exports the router from a separate file in Node.js?

A router.export

B export default

C exports.router

D module.exports

module.exports is used to export objects like routers in Node.js.

If your router has a route '/list' and you use app.use('/items', router), what is the full path to access the route?

A /list/items

B /list

C /items/list

D /items

The router path '/list' is prefixed by '/items' from app.use, making '/items/list'.

Why is separating routes into files helpful in Express apps?

A Keeps code organized and easier to maintain

B Makes the app run faster

C Prevents errors automatically

D Allows using multiple databases

Separating routes helps organize code and makes maintenance easier.

Explain how to separate routes into files in an Express app and how to use them in the main app.

Think about creating a mini app inside a file and connecting it to the main app.

Describe the benefits of separating routes into different files in Express.

Consider how you organize things in real life to keep them neat and easy to find.

Practice

1. What is the main benefit of separating routes into different files in an Express app?

easy

A. It makes the app run faster.

B. It keeps the app organized and easier to maintain.

C. It automatically secures the routes.

D. It removes the need for middleware.

Solution

1. Step 1: Understand code organization

   Separating routes into files helps keep code clean and manageable as the app grows.

2. Step 2: Identify benefits

   This separation does not affect speed or security directly but improves maintainability.

3. Final Answer:

   It keeps the app organized and easier to maintain. -> Option B

4. Quick Check:

   Organized code = easier maintenance [OK]

Hint: Think about code clarity and maintenance benefits [OK]

Common Mistakes:

• Confusing organization with performance improvements
• Assuming route separation adds security automatically
• Thinking middleware is not needed after separation

2. Which of the following is the correct way to create a router in a separate file named users.js?

easy

A. const router = express.Router(); module.exports = router;

B. const router = new express.Router(); export default router;

C. const router = express.Router; module.exports = router();

D. const router = express.Router(); export router;

Solution

1. Step 1: Create router instance correctly

   Use express.Router() to create a new router instance.

2. Step 2: Export the router properly

   Use module.exports = router; to export it for use in other files.

3. Final Answer:

   const router = express.Router(); module.exports = router; -> Option A

4. Quick Check:

   Correct router creation and export = const router = express.Router(); module.exports = router; [OK]

Hint: Remember to call Router() and use module.exports [OK]

Common Mistakes:

• Forgetting parentheses after Router
• Mixing CommonJS and ES module syntax
• Exporting router incorrectly

3. Given the following code in users.js:

const express = require('express');
const router = express.Router();
router.get('/profile', (req, res) => {
  res.send('User Profile');
});
module.exports = router;

And in app.js:

const express = require('express');
const app = express();
const usersRouter = require('./users');
app.use('/users', usersRouter);
app.listen(3000);

What will be the response when a client requests /users/profile?

medium

A. User Profile

B. Cannot GET /users/profile

C. 404 Not Found error

D. Server crashes with error

Solution

1. Step 1: Understand route prefixing

   The router is mounted at /users, so /profile inside router becomes /users/profile.

2. Step 2: Check route handler response

   The route /profile sends 'User Profile' as response.

3. Final Answer:

   User Profile -> Option A

4. Quick Check:

   Route prefix + handler response = 'User Profile' [OK]

Hint: Remember mounted path prefixes router routes [OK]

Common Mistakes:

• Forgetting the prefix from app.use
• Expecting route at root instead of prefixed path
• Assuming 404 without checking router setup

4. You have this code in products.js:

const express = require('express');
const router = express.Router();
router.get('/list', (req, res) => {
  res.send('Product List');
});
// Missing module.exports here

And in app.js:

const express = require('express');
const app = express();
const productsRouter = require('./products');
app.use('/products', productsRouter);
app.listen(3000);

What error will occur when starting the app or accessing /products/list?

medium

A. SyntaxError due to missing export

B. TypeError: Cannot read property 'use' of undefined

C. No error, but route won't respond

D. productsRouter is undefined, causing an error

Solution

1. Step 1: Check module export in products.js

   Since module.exports is missing, require('./products') returns undefined.

2. Step 2: Understand impact in app.js

   Using undefined as router in app.use causes an error when app tries to use it.

3. Final Answer:

   productsRouter is undefined, causing an error -> Option D

4. Quick Check:

   Missing export = undefined import error [OK]

Hint: Always export router to avoid undefined imports [OK]

Common Mistakes:

• Assuming app runs without export
• Confusing syntax error with runtime error
• Not checking module.exports presence

5. You want to separate routes for /api/users and /api/products into two files: users.js and products.js. Each file exports a router with routes starting at /. How should you mount these routers in app.js to correctly handle requests to /api/users/profile and /api/products/list?

hard

A. app.use('/api', usersRouter); app.use('/api', productsRouter);

B. app.use('/users', usersRouter); app.use('/products', productsRouter);

C. app.use('/api/users', usersRouter); app.use('/api/products', productsRouter);

D. app.use('/', usersRouter); app.use('/', productsRouter);

Solution

1. Step 1: Understand router base paths

   Each router handles routes starting at /, so mounting them at specific paths adds prefixes.

2. Step 2: Mount routers with full API paths

   Mount usersRouter at /api/users and productsRouter at /api/products to match desired URLs.

3. Final Answer:

   app.use('/api/users', usersRouter); app.use('/api/products', productsRouter); -> Option C

4. Quick Check:

   Mount routers at full paths for correct URL handling [OK]

Hint: Mount routers at full URL prefixes to match routes [OK]

Common Mistakes:

• Mounting routers at wrong or incomplete paths
• Mounting both routers at same path causing conflicts
• Assuming routers handle full paths internally