next('route') ignores chained route

[me-nkr]

To skip the rest of the middleware functions from a router middleware stack, call next('route') to pass control to the next route. NOTE: next('route') will work only in middleware functions that were loaded by using the app.METHOD() or router.METHOD() functions.

Saw this is express docs. Would like to know why it can't work with chained routes?

[harshagarwalnyu]

The reason next('route') does not jump to a chained route is by design. next('route') only works when middleware is loaded via app.METHOD() or router.METHOD() -- it skips the remaining handlers in the current route's handler array and moves to the next separately defined route at the same path.

So if you have:

app.get('/foo', handler1, handler2)  // route A
app.get('/foo', handler3)             // route B

Calling next('route') inside handler1 skips handler2 and jumps to route B's handler3.

But with chaining like router.route('/foo').get(h1).get(h2), the second .get() is a chained handler on the same route object, not a separate route -- so next('route') has nowhere to jump.

The fix is to define them as separate router.get() calls rather than chaining on the same router.route() object.