jsonServer.rewriter not work in module solution

[qiluo]

My main code is very simple as below,

/// Set default middlewares (logger, static, cors and no-cache)
server.use(middlewares);

// To handle POST, PUT and PATCH you need to use a body-parser
// You can use the one used by JSON Server
server.use(jsonServer.bodyParser);

// Use default router
// server.use(jsonServer.rewriter({
//     '/api/v1/': '/'
// }));
server.use('/api/v1', router);
server.listen(3000, () => {
    console.log('JSON Server is running')
});

neither rewriter nor server.use('/api/v1', router) worked, the access url only happened on / not /api/v1/...

any idea?

[zentoaku]

Same for me. Upgraded from 0.8.x to 0.10.0 and custom routes aren't working

[techpool]

For me it works pretty well, in order to achieve custom routes we can have it just the way you described:

const jsonServer = require('json-server')
const server = jsonServer.create()
const router = jsonServer.router('db.json')
const middlewares = jsonServer.defaults()

server.use(middlewares)
server.use('/api/v1', router)
server.listen(3000, () => {
  console.log('JSON Server is running')
})

But if we use the router at this endpoint and use the middleware for the same old root route then it might not work properly. The landing page that you see won't give you the list of endpoints.

So you should probably use the middleware as well like this:

const jsonServer = require('json-server')
const server = jsonServer.create()
const router = jsonServer.router('db.json')
const middlewares = jsonServer.defaults()

server.use('/api/v1', middlewares)
server.use('/api/v1', router)
server.listen(3000, () => {
  console.log('JSON Server is running')
})

Then if you go to /api/v1 you will be greeted with the landing page listing all the routes available.

But even though if you don't use the middleware you will still have the endpoints working perfectly.

[qiluo]

Thanks it finally worked. Hopefully document could get improved

[techpool]

Great! Maybe we can mark this as closed.

[rchod]

@qiluo Hello, maybe you can close this issue ?