http-mockjs-util v4.5.2

http-mockjs

中文文档

A tool for the local mock interface.

It has the following features:

1. Perform the mock mapping relationship through the httpmock field in the package.json , or configuration file .httpmockrc.
2. Support mockjs syntax, flexible configuration of dynamic mock return value;
3. Identify express-style urls based on path-to-regexp
4. Based on http-mockjs-ui, manage the configuration file and mock file content in a visual way to improve efficiency.More detail

Usage

GUI

GUI for configuration and mock content.More detail

Configuration

Take a configuration file .httpmockrc as an example:

{
    "mockFileName":"mymocks",
    "routes":{
        "GET /j/getSomeData.json":
        {
            "path": "/api/get.json"
        },
        "POST /p/postData.do":
        {
            "path": "/api/post.json"
        },
        "GET /user/:id":{
            "path": "/api/user.json"
        },
        "GET /users/:id+":{
            "path": "/api/info.json",
            "ignore": true
        },
        "GET /users/user?id=123":{
            "path": "/api/user/123.json",
            "ignore": true
        }
    }
}

Use responseHeaders to custom response header, the default Content-Type is application/json:

{
    "mockFileName":"mymocks",
    "responseHeaders":{
      "Content-Type":"application/json",
      "xixi":"hah"
    }
}

Return the file content demo as follows, you can use the mockjs style:

{
    "code":0,
    "message":"success",
    "result":{
        "content":true,
        "name":"brizer123",
        "domain":"@domain()",
        "otherUrl":"@url()",
        "desciption":"@cparagraph(1, 3)",
        "date":"@date('yyyy-MM-dd')"
    }
}

mockFileName

The root path where the mock file is stored, default is mocks

routes

Mapping management of the corresponding interface

path

Path of the mapped local mock file

ignore

If set to true, skip this matching rule.

Sometimes you want to keep the configuration, but you don't want it to take effect, for example, when an interface needs to directly call the result of the remote rather than the local mock. It is useful.

port

Which port to start mock server, default is 8009

responseHeaders

Custom response headers.

working with webpack-dev-server

Config in devServer.before

  devServer:{
    before:(app)=>{
      mocker(app)
    }
  }

demo

working with express

set app into mocker:

const app = express();
const {mocker} = require('http-mockjs')

mocker(app)

app.listen(8002)

working with command line tools such as http-server

Proxy the request to the proxy server started by httpmock through the proxy http-server.

  "scripts": {
    "serve": "http-server -p 8008 -P http://localhost:8001/",
    "mock": "httpmock 8001"
  }

demo