I read almost all the open questions, maybe this article can provide some solutions for them.

[wll8]

Thanks json-server, you are great. I gradually created the mockm project in the process of using, maybe it can provide some help for the following problems:

• out of the box
  • CrUD and generated data #727
  • local ip #879
• Support proxying to one or more servers
• Support interception and modification of proxies
• Support data generator
• Support logging (including carried data and returned data), configure log ignore rules
  • Is there any way not to save record with POST, PUT, PATCH or DELETE requests? #645
• Support interception and modification of api generated by db.json
• Support generating websocket interface
  • WebSocket #870
• Support extranet mapping
• Support modification and instant update
• better integration with express
  • Add custom routes to expressJS app with json-server #475
• For routes that do not exist in db.json, enter other middleware
  • Potential feature: Custom 404 handler? #205
• Multiple static directories, and histroy mode
  • Support for multiple static directories #182
• Monitor multiple files or directories
  • how to watch multiple files? #656

read and write db

Read or change it from custom api or json-server api.

• Reading db in real time in custom request #1214
• fetch value from db.json #401
• serve static data #159
• Increase counter on the server, autonomously? #484
• How do i create a new table using json-server #349
• DELETE from server by property of a JSON object #310
• Is there a way to add new resources? #1170
• Convert json to API server, suggestion #991

module.exports = (util) => {
  return {
    api: {
      'get /test/db' (req, res) {
        const db = global.config._db // Object wrapped by _.chain(db.json)
        const data = db.getState() // whole json data
        data.user[0].t1 = 111
        db.write() // call write to store changes
        data.user[0].t2 = 222
        db.get(`user`).set(`[0].t3`, 333).value() // You can use lodash chain operations, you need to call .value() after the operation is complete
        res.json(data.user[0])
      },
    },
    db: {
      user: [
        {
          name: `ace`,
        },
      ],
    },
  }
}

Intercept requests and responses

Just create the same api and you can intercept it.

• How to mock a api for login? #390
• Provides user authentication with jwt #1282
• How to create a custom route that doesn't care of query params #1238
• How to change default query params like _page or _limit? #1246
• Not finding any way to change a response for a request from the client side #1002
• How to get params from request #969
• Intercept request for with DB query? #616
• Accessing query strings before routing #314
• How to match the given GET parameters every time? #313
• Custom query params #141
• Custom query params #141
• [Question] Filtrations in custom route #1199
• How can I intercept and modify the data returned by db.js in this place? #958
• Paginate can't return total  #791
• Does json-server support call-back functionality? #778
• customize response like this possible? #717
• Is there anyway to delay the response time? #647
• [Feature request] Ability to intercept the sent data #125
• Return a blob or pdf from json-server #1269

module.exports = (util) => {
  return {
    api: {
      // For example, permission checks can be created at all entry points
      'use /' (req, res, next) { 
        if(req.headers.token === undefined) {
          res.status(403).json({msg: `No permission`})
        } else {
          next()
        }
      },
      // Intercepts any requests sent to db.json, and responses from db.josn
      'patch /books/:id' (req, res, next) { // intercept config.db
        req.body.a = `111` // Modify the data passed in by the user
        next()
        res.mm.resHandleJsonApi = async (arg) => {
          arg.data.a = `222` // Modify the response, it will not be stored in db.json
          return arg.resHandleJsonApi(arg)
        }
      },
    },
    db: {
      books: [
        {
          id: 1,
          title: `css`,
        },
      ],
    },
  }
}

route rewrite

Acts on static file addresses, addresses generated by db.json, and custom api addresses.

• Running behind a proxy in sub path #1172
• unable to mount api with a prefix #1049
• Custom route not working when accessing a single resource #1011
• Pagination, filtering, sorting, slicing, operators do not work on custom routes. #790
• Routes functionality doesn't work for static files #591

module.exports = (util) => {
  return {
    route: {
      '/test/db/api/*': '/$1', // /test/db/api/books/1 => /books/1
    },
  }
}

upload files

• File Upload #528
• Upload JSON To Server? #354

const path = require(`path`)

module.exports = (util) => {
  return {
    api: {
      async '/upload'(req, res) {
        const multiparty = await util.toolObj.generate.initPackge(`multiparty`) // or require(`multiparty`)
        const form = new multiparty.Form({
          uploadDir: `${__dirname}/upload/`,
        })
        form.parse(req, async (err, fields = [], files) => {
          const file = files.file[0]
          let url = `http://127.0.0.1:${global.config.port}/file/${path.parse(file.path).base}`
          // Can also be saved to db.json: global.config._db.
          res.json({url})
        })
      },
    },
    // Support for multiple static directories, and histroy mode
    static: {
      path: `/file`,
      fileDir: `./upload`,
    },
  }
}

how to use

Sorry, as I'm not familiar with English, there is currently no documentation in English, but the tool is simple and should be easy to use.

# Check the node version, currently mockm supports node v10.12.0 and above
node -v

# Install
npm i -g mockm

# Run it with the sample configuration
mockm --config 

# Browser open http://127.0.0.1:9005/#/apiStudio/

The above command will generate common configuration, modify mm.config.js and try it out.

The following documents can be helpful to you:

• simple.mm.config.js
• config.d.ts
• test case