Gathering detailed insights and metrics for mockm
Gathering detailed insights and metrics for mockm
用于处理前端在接口环节中的各种问题，例如快速生成 api 以及创造数据、页面部署等，开箱即用，便于迁移。A framework based on Express. It can quickly generate APIs and create data, ready for deployment out of the box.
Installations
npm install mockmDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Min. Node Version
>=10.12.0
Node Version
18.19.0
NPM Version
10.7.0
Releases
4
Languages
4
JavaScript
HTML
CSS
SCSS
JavaScript (87.44%)
HTML (8.7%)
CSS (2.52%)
SCSS (1.34%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
282 Stars
797 Commits
25 Forks
3 Watchers
22 Branches
2 Contributors
Updated on Jul 02, 2025
Maintainers
1
Package Meta Information
Latest Version
1.1.27-alpha.12
Package Id
mockm@1.1.27-alpha.12
Unpacked Size
4.66 MB
Size
1.26 MB
File Count
108
NPM Version
10.7.0
Node Version
18.19.0
Published on
Jun 10, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
27
@babel/runtime-corejs3@httptoolkit/httpolyglot@wll8/better-mock@wll8/express-ws@wll8/json-server@wll8/process-manageraddressaxiosbody-parserchokidarcompressioncore-jsdefault-gatewayexpress-urlrewritefilenamifyhttp-proxy-middlewarelodash.clonedeeplodash.droplodash.orderbylodash.takemimemorgannode-http-proxy-jsonpath-to-regexppostinstall-postinstallvm2whatnpm
一个基于 express 的工具。它可以快速生成 api 以及创造数据，开箱即用，便于部署。
尝试
- 安装: 命令行输入
npm i -g mockm - 启动: 命令行输入
mm --config
所有工作已经结束了, 并且你还创建了一个自己的 api, 拥有了后端接口允许跨域的功能, 接口记录功能和重放功能...
为了让你更快的找到感觉, --config 这个参数创建了一个简单的示例配置 mm.config.js, 你可以查看它窥探天机！
- 浏览器访问 http://127.0.0.1:9000/api/1 查看效果.
- 浏览器访问 http://127.0.0.1:9005/#/get/api/1 查看请求详情.
- 想了解更多功能请继续...
功能示例
这里演示了一些不同场景下的配置, 包括各种代理和拦截, api 的编写和数据生成方式. 详细文档请参考配置项
如何使后端的接口允许跨域
不需要配置 webpack, 不需要后端人员更改, 不需要浏览器插件
这个功能 mockm 默认是支持的, 以最简方式启动 mockm 就能拥有此功能, 只要在命令行输入下面这条命令即可.
1mm proxy=http://192.168.1.18:8080
你也可以使用配置文件的方式, 创建 mm.config.js 文件并录入以下内容, 然后命令行输入 mm 即可:
1module.exports = { 2 proxy: `http://192.168.1.18:8080`, 3};
然后更换原来的请求地址为自己的即可, 例如自己的 IP 为 127.0.0.1 则做以下更改:
如何创建一个自己的接口
与后端接口相同时, 会使用自己的
让我们以最简单的方式创建一个接口:
1module.exports = { 2 api: { 3 "/my/api": { 4 msg: `我的 api`, 5 }, 6 }, 7};
接口已完成, 访问 http://127.0.0.1:9000/my/api 查看效果.
详情请参考 config.api, 为了便于多人协作, 还能从浏览器里创建, 参考 接口编辑.
如何从接口获取请求信息
当我们需要根据接口传入的值来返回不同的内容时, 也是很容易:
1module.exports = { 2 api: { 3 "/my/value"(req, res) { 4 // req.params 是 url 上的路径参数 5 // req.query 是 url 上的查询参数 6 // req.body 是请求体中的参数 7 res.json({ desc: `你传入的值`, data: req.query }); 8 }, 9 }, 10};
接下访问接口传入一些 url 参数测试一下 http://localhost:9000/my/value?city=上海 结果为:
1{ 2 "desc": "你传入的值", 3 "query": { 4 "city": "上海" 5 } 6}
如何快速生成 Restful API
假设我要写一个博客文章的列表, 并且要实现添加文章, 查询文章, 分页, 模糊搜索, 删除, 修改等各种功能的接口. 那么只需添加以下内容:
1module.exports = { 2 db: { 3 blogs: [ 4 { 5 id: 1, 6 content: `mockm 是一款便于使用, 功能灵活的接口工具. 看起来不错~`, 7 title: `认识 mockm 的第一天`, 8 }, 9 ], 10 }, 11};
这时候上面要实现的所有接口已经实现了. 这里我用 httpie 作为请求工具简单表示几个功能, 你可以使用你喜欢的工具发送请求.
1# 查看 id 为 1 的博文详情 2http :9000/blogs/1 3 4# 创建一篇关于同事的文章 5http post :9000/blogs title=同事的一天 content=今天他的生活还是同样的苦涩 6 7# 获取所有文章 8http :9000/blogs 9 10# 查询所有含有 `苦涩` 的文章 11http :9000/blogs?q=苦涩 12 13# 查看 id 为 1 的博文详情 14http :9000/blogs/1 15 16# 创建一篇关于同事的文章 17http post :9000/blogs title=同事的一天 content=今天他的生活还是同样的苦涩 18 19# 获取所有文章 20http post :9000/blogs 21 22# 查询所有含有 `苦涩` 的文章 23post :9000/blogs?q=苦涩 24
所有生成的接口请参考 config.db.
如何生成逼真的数据
mockjs 是一个不错的数据生成工具, mockm 默认集成了它, 下面用它生成一批用户信息.
1module.exports = (util) => { 2 return { 3 db: { 4 users: util.libObj.mockjs.mock({ 5 "data|15-23": [ 6 // 随机生成 15 至 23 条数据 7 { 8 "id|+1": 1, // id 从 1 开始自增 9 name: `@cname`, // 随机生成中文名字 10 "sex|1": [`男`, `女`, `保密`], // 性别从这三个选项中随机选择一个 11 }, 12 ], 13 }).data, 14 }, 15 }; 16};
现在访问 http://localhost:9000/users 已经可以看到很多逼真的用户数据了.
如何更改后端返回的数据
很多时候后端不方便直接修改数据, 因为会涉及很多逻辑, 前端直接写在代码里既麻烦又容易引发问题.
假设后台接口 http://192.168.1.18:8080/api/user get 请求返回的数据是这样的:
1{ 2 "code": 200, 3 "data": { 4 "books": [ 5 { 6 "page": 52, 7 "type": "css" 8 }, 9 { 10 "page": 26, 11 "type": "js" 12 } 13 ], 14 "name": "张三" 15 }, 16 "success": true 17} 18
如果要修改 books 索引为 1 的 type 为 html, 那么配置如下:
1module.exports = { 2 proxy: { 3 "/": `http://192.168.1.18:8080`, 4 "/api/user": [`data.books[1].type`, `html`], // 数组第一个参数是修改的路径, 第二个参数是修改后的值 5 }, 6};
如果要直接替换整个返回值为 html , 可以这样:
1module.exports = { 2 proxy: { 3 "/": `http://192.168.1.18:8080`, 4 "/api/user": [`html`], // 如果只提供一个参数, 则直接替换 5 }, 6};
更多操作方式请参考 config.proxy
如何延迟后端接口的响应时间
示例延迟 http://192.168.1.18:8080/api/user 这个接口的响应时间为 5 秒之后:
1module.exports = { 2 proxy: { 3 "/": `http://192.168.1.18:8080`, 4 "/api/user": { 5 mid(req, res, next) { 6 setTimeout(next, 5000); 7 }, 8 }, 9 }, 10};
如何创建一个下载文件的接口
实现一个文件下载接口 http://127.0.0.1:9000/file, 发送某文件给客户端.
1module.exports = { 2 api: { 3 "/file"(req, res, next) { 4 res.download(`这里写要下载的文件路径`); 5 }, 6 }, 7};
如何创建 websocket 接口
实现一个 websocket 接口 ws://127.0.0.1:9000/wsecho, 当连接成功时发送 连接成功, 并把客户端发送的信息再原样返回给客户端.
1api: { 2 'ws /wsecho' (ws, req) { 3 ws.send(`连接成功`) 4 ws.on('message', (msg) => { 5 ws.send(msg) 6 }) 7 } 8},
客户端连接代码, 可以直接打开浏览器 console 测试:
1function startWs(wsLink) { 2 window.ws = new WebSocket(wsLink); 3 ws.onopen = (evt) => { 4 ws.send(`客户端发送的消息`); 5 }; 6 ws.onmessage = (evt) => { 7 console.log(`服务器返回的消息`, evt.data); 8 }; 9 ws.onclose = (evt) => { 10 // 断线重连 11 setTimeout(() => startWs(wsLink), 1000); 12 }; 13} 14startWs(`ws://127.0.0.1:9000/wsecho`); 15// ws.send(`发送新消息`)
如何实现动态的接口路径参数
实现一个接口 http://127.0.0.1:9000/status/code, 其中 code 的位置是一个动态参数, 并返回接收到的 code.
1module.exports = { 2 api: { 3 "/status/:code"(req, res, next) { 4 const { params, query, body } = req; 5 res.json({ statusCode: params.code }); 6 }, 7 }, 8};
如何向后端展示接口参数
告别截图, 告别一问一答, 告别参数太多无法复制
默认情况下, 每次请求会生成一条链接在响应头中的 x-test-api 上, 把这个链接发给后端即可.
-
方法 1 直接在启动 mockm 的命令行里可能看到.
-
方法 2 在 http://127.0.0.1:9005 页面上的列表中查找.
-
方法 3 如果你使用 chrome 开发工具, 可以在 Network 中找到请求的接口在 Response Headers 中找到 x-test-api.
如何远程使用接口
把 config.remote 设置为 true 就能拥有域名的和 https 证书的公网接口, 能够在微信公众号上使用, 或者发给其他人远程使用..
在控制台会显示 远程服务信息, x-test-api 和接口都会生成对应的远程访问链接.
如何恢复后端好了又坏的接口
如果某个接口之前是好的, 但是由于某些问题现在坏了, 后端又没来得及修复, 可是前端现在有页面依赖这个接口, 怎么办?
在 http://127.0.0.1:9005 页面选择对应接口的好的那条请求历史, 点击 webApi => 使用此记录 即可.
如何在后端关闭时不影响页面
页面要展示的内容来源于数据, 如果后端服务器出现问题, 所有接口无法使用, 这时候修改请求地址为 http://127.0.0.1:9001 即可让页面使用之前服务器返回的数据.
从界面上操作 mockm
你也可以从 UI 输入创建接口或操作请求历史，以下展示部分截图，详细文档请参考界面说明.
请求记录详情
某个 api 的请求历史
从界面上创建 api
区别
| 工具 | 简述 | 备注 |
|---|---|---|
| mockjs | 前端拦截 xhr 请求, 生成数据 | 不能在网络控制台看到请求 |
| json-server | 用 json 生成 Restful api | 没有集成数据生成功能 |
| yapi/rap2 | 管理接口文档, 生成接口和数据 | 安装麻烦, 不方便与前端项目同步 |
友情链接
| 项目 | 简介 |
|---|---|
| taroify | Taroify 是移动端组件库 Vant 的 Taro 版本，两者基于相同的视觉规范，提供一致的 API 接口，助力开发者快速搭建小程序应用。 |
| wot-design-uni | 一个基于Vue3+TS开发的uni-app组件库，提供70+高质量组件，支持暗黑模式、国际化和自定义主题。 |
许可
Copyright (c) 2017-present, xw
No vulnerabilities found.
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
no binaries found in the repo
Reason
2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
Project has not signed or included provenance with any releases.
Details
- Warn: release artifact v1.1.27-alpha.2 not signed: https://api.github.com/repos/wll8/mockm/releases/117296225
- Warn: release artifact 1.1.25-alpha.17.2 not signed: https://api.github.com/repos/wll8/mockm/releases/49787054
- Warn: release artifact 1.1.3 not signed: https://api.github.com/repos/wll8/mockm/releases/34737859
- Warn: release artifact v1.1.27-alpha.2 does not have provenance: https://api.github.com/repos/wll8/mockm/releases/117296225
- Warn: release artifact 1.1.25-alpha.17.2 does not have provenance: https://api.github.com/repos/wll8/mockm/releases/49787054
- Warn: release artifact 1.1.3 does not have provenance: https://api.github.com/repos/wll8/mockm/releases/34737859
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'dev'
- Warn: branch protection not enabled for branch 'master'
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
91 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-whgm-jr23-g3j9
- Warn: Project is vulnerable to: GHSA-wf5p-g6vw-rhxx
- Warn: Project is vulnerable to: GHSA-jr5f-v2jv-69x6
- Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-w8qv-6jwh-64r5
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-phwq-j96m-2c2q
- Warn: Project is vulnerable to: GHSA-ghr5-ch3p-vcr6
- Warn: Project is vulnerable to: GHSA-434g-2637-qmqr
- Warn: Project is vulnerable to: GHSA-49q7-c7j4-3p7m
- Warn: Project is vulnerable to: GHSA-977x-g7h5-7qgw
- Warn: Project is vulnerable to: GHSA-f7q4-pwc6-w24p
- Warn: Project is vulnerable to: GHSA-fc9h-whq2-v747
- Warn: Project is vulnerable to: GHSA-vjh7-7g9h-fjfh
- Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
- Warn: Project is vulnerable to: GHSA-c7qv-q95q-8v27
- Warn: Project is vulnerable to: GHSA-33f9-j839-rf8h
- Warn: Project is vulnerable to: GHSA-c36v-fmgq-m8hx
- Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
- Warn: Project is vulnerable to: GHSA-76p3-8jx3-jpfq
- Warn: Project is vulnerable to: GHSA-3rfm-jhwj-7488
- Warn: Project is vulnerable to: GHSA-hhq3-ff78-jv3g
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
- Warn: Project is vulnerable to: GHSA-5rrq-pxf6-6jx5
- Warn: Project is vulnerable to: GHSA-8fr3-hfg3-gpgp
- Warn: Project is vulnerable to: GHSA-gf8q-jrpm-jvxq
- Warn: Project is vulnerable to: GHSA-2r2c-g63r-vccr
- Warn: Project is vulnerable to: GHSA-cfm4-qjh2-4765
- Warn: Project is vulnerable to: GHSA-x4jg-mjrx-434g
- Warn: Project is vulnerable to: GHSA-r8f7-9pfq-mjmv
- Warn: Project is vulnerable to: GHSA-rp65-9cf3-cjxr
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
- Warn: Project is vulnerable to: GHSA-h7cp-r72f-jxh6
- Warn: Project is vulnerable to: GHSA-v62p-rq8g-8h59
- Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-7mwh-4pqv-wmr8
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
- Warn: Project is vulnerable to: GHSA-g4rg-993r-mgx7
- Warn: Project is vulnerable to: GHSA-3jfq-g458-7qm9
- Warn: Project is vulnerable to: GHSA-5955-9wpr-37jh
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-7p7h-4mm5-852v
- Warn: Project is vulnerable to: GHSA-wr3j-pwj9-hqq6
- Warn: Project is vulnerable to: GHSA-4v9v-hfq4-rm2v
- Warn: Project is vulnerable to: GHSA-9jgg-88mc-972h
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-x9w5-v3q2-3rhw
- Warn: Project is vulnerable to: GHSA-w573-4hg7-7wgq
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
- Warn: Project is vulnerable to: GHSA-6h5x-7c5m-7cr7
- Warn: Project is vulnerable to: GHSA-rv95-896h-c2vc
- Warn: Project is vulnerable to: GHSA-jchw-25xp-jwwc
- Warn: Project is vulnerable to: GHSA-cxjh-pqwp-8mfp
- Warn: Project is vulnerable to: GHSA-pfrx-2q88-qq97
- Warn: Project is vulnerable to: GHSA-7wwv-vh3v-89cq
- Warn: Project is vulnerable to: GHSA-pfq8-rq6v-vf5m
- Warn: Project is vulnerable to: GHSA-rc47-6667-2j5j
- Warn: Project is vulnerable to: GHSA-4www-5p9h-95mh
- Warn: Project is vulnerable to: GHSA-9gqv-wp59-fq42
- Warn: Project is vulnerable to: GHSA-78xj-cgh5-2h22
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-6vfc-qv3f-vr6c
- Warn: Project is vulnerable to: GHSA-x7hr-w5r2-h6wg
- Warn: Project is vulnerable to: GHSA-4wf5-vphf-c2xc
- Warn: Project is vulnerable to: GHSA-5j4c-8p2g-v4jx
- Warn: Project is vulnerable to: GHSA-g3ch-rx76-35fx
- Warn: Project is vulnerable to: GHSA-4gmj-3p3h-gm8h
- Warn: Project is vulnerable to: GHSA-x565-32qp-m3vf
- Warn: Project is vulnerable to: GHSA-cchq-frgv-rjh5
- Warn: Project is vulnerable to: GHSA-g644-9gfx-q4q4
- Warn: Project is vulnerable to: GHSA-76p7-773f-r4q5
- Warn: Project is vulnerable to: GHSA-h5c3-5r3r-rr8q
- Warn: Project is vulnerable to: GHSA-rmvr-2pp2-xj38
- Warn: Project is vulnerable to: GHSA-xx4v-prfh-6cgc
- Warn: Project is vulnerable to: GHSA-3j8f-xvm3-ffx4
- Warn: Project is vulnerable to: GHSA-j9fq-vwqv-2fm2
- Warn: Project is vulnerable to: GHSA-pqw5-jmp5-px4v
Score
1.7
/10
Last Scanned on 2025-06-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More