vite-plugin-mock-dev-server 0.3.16 → 0.3.17

package/README.md

@@ -37,7 +37,10 @@
 - ⚖️ Use `server.proxy`
 - 🍕 Support `viteConfig.define` in mock file
 - 📤 Support `multipart` content-type，mock upload file.
-- 🌈 Support `vite preview` mode.
+- 🌈 Support `vite preview` mode
+- 🗂 Support for building small mock services that can be deployed independently
+
+
 ## Documentation
 
 See the [documentation](https://vite-plugin-mock-dev-server.netlify.app/) to learn more.
@@ -163,6 +166,29 @@ export default defineConfig({
   })
   ```
 
+- `options.build`
+  
+  When building a small, independently deployable mock service.
+
+  Type： `boolean | ServerBuildOptions` 
+
+  Default：`false`
+
+  ```ts
+  interface ServerBuildOptions {
+    /**
+     * server port
+     * @default 8080
+     */
+    serverPort?: number
+    /**
+     * build output dir
+     @default 'mockServer'
+     */
+    dist?: string
+  }
+  ```
+
 ### defineMock(config)
 
 Mock Type Helper
@@ -474,6 +500,26 @@ export default defineMock({
 })
 ```
 
+## Mock Services
+
+In some scenarios, you may need to use the data support provided by the mock service for display purposes, but it is possible that the project has been packaged and deployed as a build and is out of the mock service support provided by `vite` and this plugin. Since this plugin was designed to support the import of `node` modules into mock files, it cannot package mock files inline into client-side build code.
+
+To cater for such scenarios, the plugin provides support under `vite preview` as well as the ability to build a small, independently deployable mock service application at `vite build` that can be deployed to the relevant environment. The mock support is then implemented by proxy forwarding to the actual port by another http server such as `nginx`.
+
+Build the default output into the `dist/mockServer` directory and generate the following file:
+```sh
+./mockServer
+├── index.js
+├── mock-data.js
+└── package.json
+```
+
+In this directory, after `npm install` to install the dependencies, `npm start` can be executed to start the mock server.
+
+default port: `8080`。
+
+Access the associated `mock` interface via `localhost:8080/`.
+
 ## Archives
 
 [awesome-vite](https://github.com/vitejs/awesome-vite#helpers)

package/README.zh-CN.md

@@ -38,7 +38,8 @@
 - ⚖️ 使用 `server.proxy` 配置
 - 🍕 支持在 mock文件中使用 `viteConfig.define`配置字段
 - 📤 支持 multipart 类型，模拟文件上传
-- 🌈 支持 `vite preview` 模式.
+- 🌈 支持 `vite preview` 模式
+- 🗂 支持构建可独立部署的小型mock服务
 
 
 ## 文档
@@ -166,6 +167,28 @@ export default defineConfig({
   })
   ```
 
+- `options.build`
+  
+  构建可独立部署的小型mock服务时配置。
+
+  类型： `boolean | ServerBuildOptions` 
+
+  默认值：`false`
+
+  ```ts
+  interface ServerBuildOptions {
+    /**
+     * 服务端口
+     * @default 8080
+     */
+    serverPort?: number
+    /**
+     * 构建输出目录
+     @default 'mockServer'
+     */
+    dist?: string
+  }
+  ```
 
 ### defineMock(config)
 
@@ -479,6 +502,24 @@ export default defineMock({
 })
 ```
 
+## 独立部署的小型mock服务
+
+在一些场景中，可能会需要使用mock服务提供的数据支持，用于展示，但可能项目已完成打包构建部署，已脱离 `vite` 和本插件提供的 mock服务支持。由于本插件在设计之初，支持在mock文件中引入各种 `node` 模块，所以不能将 mock文件打包内联到客户端构建代码中。
+
+为了能够满足这类场景，插件一方面提供了 `vite preview` 下的支持，同时还提供了在 `vite build` 时，也构建一个可独立部署的 小型mock服务应用，可以将这个应用部署到相关的环境，后通过其他http服务器如nginx做代理转发到实际端口实现mock支持。
+
+构建默认输出到 `dist/mockServer` 目录中，并生成如下文件：
+```sh
+./mockServer
+├── index.js
+├── mock-data.js
+└── package.json
+```
+
+在该目录下，执行 `npm install` 安装依赖后，可执行 `npm start` 即可启动 mock server。
+默认端口为 `8080`。
+可通过 `localhost:8080/` 访问相关的 `mock` 接口。
+
 ## Archives
 
 [awesome-vite](https://github.com/vitejs/awesome-vite#helpers)