Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript Express Basics Middleware Middleware Sequence and Routing

Ceri Woolway
Ceri Woolway
4,682 Points
Posted by Ceri Woolway
Ceri Woolway
4,682 Points

What is the point of middleware that runs on only one route?

I don't understand why you wouldn't just include that functionality in the bit that fulfils that requests for that route?

2 Answers

Travis Alstrand
seal-mask
STAFF
.a{fill-rule:evenodd;}techdegree
Travis Alstrand
Treehouse Teacher
Travis Alstrand
.a{fill-rule:evenodd;}techdegree
Travis Alstrand
Treehouse Teacher

I believe it's up to you and the tasks you're trying to accomplish and your situation.

I think he's just explaining here the possibilities of passing data through different middleware before returning a response to the client.

Seth Foss
Seth Foss
7,097 Points
Seth Foss
Seth Foss
7,097 Points

Another possibility is that, even though anonymous functions like we are using in this lesson are hugely popular, the function you pass in doesn't HAVE to be anonymous.

You could define a reusable function, and apply it to just the routes that need it:

node.js 
function myMiddleware(req, res, next) {
   console.log('One');
   next();
}

app.use('/route1',myMiddleware);
app.use('/route2',myMiddleware);