Namespaces for separation in Express - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when accessing routes with namespaces?

Consider this Express app code that uses namespaces (routers) to separate routes:

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

const apiRouter = express.Router();
apiRouter.get('/users', (req, res) => res.send('API Users'));

const adminRouter = express.Router();
adminRouter.get('/users', (req, res) => res.send('Admin Users'));

app.use('/api', apiRouter);
app.use('/admin', adminRouter);

app.listen(3000);

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

Express

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

const apiRouter = express.Router();
apiRouter.get('/users', (req, res) => res.send('API Users'));

const adminRouter = express.Router();
adminRouter.get('/users', (req, res) => res.send('Admin Users'));

app.use('/api', apiRouter);
app.use('/admin', adminRouter);

app.listen(3000);

A The response is 'Admin Users'.

B The response is 'API Users'.

C 404 Not Found error.

D 500 Internal Server Error.

💡 Hint

Think about how the app.use prefixes the routes in each router.

The adminRouter is mounted at /admin. So the route /users inside adminRouter becomes /admin/users. When the client requests /admin/users, the handler in adminRouter responds with 'Admin Users'.

📝 Syntax

intermediate

Which option correctly creates a namespace router in Express?

Which code snippet correctly creates a router namespace for /blog in Express?

A const blogRouter = express.Router; app.use('/blog', blogRouter);

B const blogRouter = new express.Router(); app.use('/blog', blogRouter);

C const blogRouter = express(); app.use('/blog', blogRouter);

D const blogRouter = express.Router(); app.use('/blog', blogRouter);

💡 Hint

Remember how to create a router instance in Express.

The correct way to create a router is by calling express.Router(). Option D does this correctly. Option D calls express() which creates an app, not a router. Option D misses parentheses, so it references the function but does not call it. Option D tries to use new which is not how Router is instantiated.

🔧 Debug

advanced

Why does this namespaced route not respond as expected?

Given this Express code:

const express = require('express');
const app = express();
const userRouter = express.Router();

userRouter.get('/profile', (req, res) => res.send('User Profile'));

app.use('/user', userRouter);

app.listen(3000);

When requesting GET /profile, the server responds with 404. Why?

Express

const express = require('express');
const app = express();
const userRouter = express.Router();

userRouter.get('/profile', (req, res) => res.send('User Profile'));

app.use('/user', userRouter);

app.listen(3000);

A Because the route is mounted under '/user', so '/profile' is not matched; the correct path is '/user/profile'.

B Because the route handler is missing a next() call.

C Because the router was not attached with app.use().

D Because the server is not listening on port 3000.

💡 Hint

Check the full path the route is mounted on.

The router is mounted at '/user', so all routes inside it are prefixed with '/user'. The route '/profile' inside the router becomes '/user/profile' in the app. Requesting '/profile' does not match any route, causing 404.

❓ state_output

advanced

What is the output of nested namespaces with middleware?

Consider this Express app:

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

const apiRouter = express.Router();
const v1Router = express.Router();

v1Router.use((req, res, next) => {
  req.version = 'v1';
  next();
});

v1Router.get('/data', (req, res) => {
  res.send(`API version: ${req.version}`);
});

apiRouter.use('/v1', v1Router);
app.use('/api', apiRouter);

app.listen(3000);

What will be the response body when a client requests GET /api/v1/data?

Express

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

const apiRouter = express.Router();
const v1Router = express.Router();

v1Router.use((req, res, next) => {
  req.version = 'v1';
  next();
});

v1Router.get('/data', (req, res) => {
  res.send(`API version: ${req.version}`);
});

apiRouter.use('/v1', v1Router);
app.use('/api', apiRouter);

app.listen(3000);

A 404 Not Found

B API version: undefined

C API version: v1

D 500 Internal Server Error

💡 Hint

Look at how middleware sets req.version before the route handler.

The middleware on v1Router sets req.version = 'v1' before the route handler runs. So when the client requests /api/v1/data, the response is 'API version: v1'.

🧠 Conceptual

expert

Which statement about Express namespaces (routers) is true?

Choose the correct statement about using namespaces (routers) in Express:

A Routers cannot have middleware; middleware must be applied only on the main app instance.

B Routers can be nested and each can have its own middleware and routes, allowing modular route separation.

C Routes defined in routers lose access to the original request object properties.

D Routers automatically merge query parameters from parent routers without extra configuration.

💡 Hint

Think about how routers help organize routes and middleware.

Express routers can be nested and each router can have its own middleware and routes. This allows developers to separate routes into modules or namespaces. Middleware applies normally within routers. Options A, C, and D are incorrect because routers do support middleware, routes keep access to request properties, and query parameters are passed normally but not 'automatically merged' in a special way.

Practice

1. What is the main purpose of using namespaces in Express routing?

easy

A. To group related routes under a common path prefix

B. To improve database query speed

C. To style HTML elements

D. To manage user sessions

Solution

1. Step 1: Understand what namespaces do in Express

   Namespaces help organize routes by grouping them under a shared path prefix.

2. Step 2: Compare with other options

   Options B, C, and D relate to other concerns like database, styling, or sessions, not routing namespaces.

3. Final Answer:

   To group related routes under a common path prefix -> Option A

4. Quick Check:

   Namespaces = Group routes [OK]

Hint: Namespaces group routes by path prefix [OK]

Common Mistakes:

• Confusing namespaces with database or styling concepts
• Thinking namespaces manage sessions
• Believing namespaces affect frontend styling

2. Which of the following is the correct way to attach a router to an Express app under the namespace '/api'?

easy

A. app.router('/api', router);

B. app.attach('/api', router);

C. app.route('/api', router);

D. app.use('/api', router);

Solution

1. Step 1: Recall Express method to use middleware or routers

   Express uses app.use(path, router) to mount routers under a path.

2. Step 2: Check other options for validity

   Options A, B, and C are not valid Express methods for attaching routers.

3. Final Answer:

   app.use('/api', router); -> Option D

4. Quick Check:

   Attach router with app.use() [OK]

Hint: Use app.use('/path', router) to attach routers [OK]

Common Mistakes:

• Using app.router instead of app.use
• Confusing app.route with router attachment
• Trying to use non-existent methods like app.attach

3. Given the code below, what will be the full URL path to access the route handler?

const express = require('express');
const app = express();
const userRouter = express.Router();

userRouter.get('/profile', (req, res) => res.send('User Profile'));
app.use('/user', userRouter);

medium

A. /user/profile

B. /profile

C. /user

D. /profile/user

Solution

1. Step 1: Identify the namespace prefix

   The router is attached with app.use('/user', userRouter), so '/user' is the base path.

2. Step 2: Combine router path with namespace

   The route inside the router is '/profile', so full path is '/user/profile'.

3. Final Answer:

   /user/profile -> Option A

4. Quick Check:

   Namespace + route = full path [OK]

Hint: Full path = namespace + router path [OK]

Common Mistakes:

• Ignoring the namespace prefix
• Using only the router path without prefix
• Mixing order of path segments

4. Identify the error in the following Express code that tries to create a namespace:

const express = require('express');
const app = express();
const adminRouter = express.Router();

adminRouter.get('/dashboard', (req, res) => res.send('Admin Dashboard'));
app.use(adminRouter, '/admin');

medium

A. Missing app.listen call

B. adminRouter.get should be adminRouter.post

C. Router should be attached with app.use('/admin', adminRouter);

D. Cannot use express.Router() for namespaces

Solution

1. Step 1: Check app.use syntax

   The correct syntax is app.use('/path', router), but here arguments are reversed.

2. Step 2: Confirm other options

   adminRouter.get should be adminRouter.post is incorrect because GET is valid; C is unrelated to namespace error; D is false because express.Router() is used for namespaces.

3. Final Answer:

   Router should be attached with app.use('/admin', adminRouter); -> Option C

4. Quick Check:

   app.use(path, router) order matters [OK]

Hint: app.use(path, router) order is important [OK]

Common Mistakes:

• Swapping arguments in app.use
• Thinking HTTP method must be POST
• Confusing missing listen with routing error

5. You want to create two separate namespaces in Express: '/api' for API routes and '/admin' for admin routes. Which code snippet correctly sets this up?

hard

A. const apiRouter = express.Router();
const adminRouter = express.Router();
app.route('/api', apiRouter);
app.route('/admin', adminRouter);

B. const apiRouter = express.Router();
const adminRouter = express.Router();
app.use('/api', apiRouter);
app.use('/admin', adminRouter);

C. const apiRouter = express.Router();
const adminRouter = express.Router();
app.use(apiRouter, '/api');
app.use(adminRouter, '/admin');

D. const apiRouter = express.Router();
const adminRouter = express.Router();
app.attach('/api', apiRouter);
app.attach('/admin', adminRouter);

Solution

1. Step 1: Create routers for each namespace

   Both apiRouter and adminRouter are created using express.Router().

2. Step 2: Attach routers with correct syntax

   Use app.use('/path', router) to mount routers under '/api' and '/admin'.

3. Step 3: Verify other options

   Options A, B, and D use incorrect methods or argument orders.

4. Final Answer:

   const apiRouter = express.Router(); const adminRouter = express.Router(); app.use('/api', apiRouter); app.use('/admin', adminRouter); -> Option B

5. Quick Check:

   Separate namespaces need separate routers and app.use() [OK]

Hint: Use separate routers and app.use('/path', router) [OK]

Common Mistakes:

• Reversing arguments in app.use
• Using app.route or app.attach incorrectly
• Trying to attach routers without namespaces