I'm writing an API using Node.js and Express. My API has GET methods of the form:

/api/v1/doSomething

/api/v1/doSomethingElse

My code is looking something like this:

server.js:

var app = express();

...

var routes = require('./routes')

routes.attachHandlers(app, '/api/v1')

routes/index.js

...

module.exports.attachHandlers = function(app, context) {

    //get a list of all the other .js files in routes

    //for each route, require() it and call it myRoute

    myRoute.attachHandlers(app, context)

}

routes/some-route.js

...

module.exports.attachHandlers = function(app, context) {

    app.get(context + '/doSomething', doSomething)

    app.get(context + '/doSomethingElse', doSomethingElse)

}

...

Effectively I'm passing the context path/mount point down through the app. If somebody were to write a route like the following, though, the context would be lost:

app.get('/doFoo', foo)

Rather than having that part of the API mounted on /api/v1/doFoo it's on /doFoo. I would like to avoid having to pass the context path around like this.

app.use supports mounting middleware on an optional mount path. I have seen references online to mounting an entire Express application on a mount path using app.use. This seems like the sort of thing I want to do, but I'm not sure how to do it or if it's the best solution for my particular use case.

To summarise - I want to mount my app.get() routes with a particular prefix by default. What's the best way of doing this?