@bequestinc/wui

中文文档
7.1.7发布于 2026/08/20MITES Module近 30 天下载 2217
  1. Be sure to run yarn install and then yarn dev to spin up the project and be sure there aren't any errors. 2. When changing the version for release, you should change the version in the package.json. Then be sure to update both the peerDependencies
原始使用文档

Instructions on updating the version for this repo

  1. Be sure to run yarn install and then yarn dev to spin up the project and be sure there aren't any errors.
  2. When changing the version for release, you should change the version in the package.json. Then be sure to update both the peerDependencies as well as the devDependencies.

Local Testing Instructions

  1. Make whatever changes that you need to make.
  2. Download and install pnpm. Once installed run pnpm install and then pnpm build.
  3. Download and install yalc. Inside this repo run yalc publish. Take note of the package-name published to the store
  4. cd into the frontend directory of the repo that you are testing WUI with.
  5. Run yalc add package-name, this will create a .yalc directory with the package contents. Your package.json file should have been updated and have something like this: "@bequestinc/wui": "file:.yalc/@bequestinc/wui"
  6. We need to copy the contents of the local .yalc directory into our container. To do this add COPY .yalc /code/.yalc before the yarn install command is called inside of the frontend/Dockerfile.local file.

Troubleshooting Testing

There is a chance that you did everything correctly but you do not see the changes you made reflected. If that's the case you may need to clear any caching that docker has performed. This can be done by deleting the volume that contains the node_modules. To do that we need to do a few things, first you need to get the hash of the frontend container by running docker container ls. Once your have the name, run the following command and looks for the Mounts section: docker container inspect yourhash. Look at the entries in the Mounts section and find the entry that has a destination containing node_modules, note the name of this entry. Run docker volume rm volumehash. Rebuild your image docker compose build --no-cache, and run your containers, docker compose up, your changes should now be present

版本与发布记录

@bequestinc/wui 共发布 100 个版本,首次发布于 2019/11/20;过去 12 个月发布了 9 个版本。

版本发布日期距今
7.1.7latest2026/08/202 个月前
7.1.62026/08/132 个月前
7.1.52026/04/166 个月前
7.1.42026/01/319 个月前
7.1.32026/01/299 个月前
7.1.22026/01/249 个月前

其他发布通道:old-version → 1.5.9,next → 3.1.0-rc5。

关于 @bequestinc/wui 的常见问题

@bequestinc/wui 是什么?

Be sure to run yarn install and then yarn dev to spin up the project and be sure there aren't any errors. 2. When changing the version for release, you should change the version in the package.json. Then be sure to update both the peerDependencies

如何安装 @bequestinc/wui?

在项目目录运行 npm install @bequestinc/wui,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:@emotion/react(^11.14.0)、@emotion/styled(^11.14.0)、@mui/icons-material(^9.0.0)、@mui/lab(9.0.0-beta.2)、@mui/material(^9.0.0)、@mui/x-date-pickers(^9.0.0)、@tanstack/react-query(^5.74.4)、@tanstack/react-query-devtools(^5.74.6)、react(^19.1.1)、react-dom(^19.1.1)、react-hot-toast(^2.5.2)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@bequestinc/wui 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/bequestinc__wui 是否存在。

@bequestinc/wui 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@bequestinc/wui 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=18.0.0 <=21.6.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@bequestinc/wui 可以商用吗?

@bequestinc/wui 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@bequestinc/wui 的下载量有多少?

根据 npm 官方下载统计,@bequestinc/wui 在 2026/10/08 – 2026/11/06 这 30 天内被下载 2,217 次,日均约 74 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@bequestinc/wui 还在维护吗?

最新版本 7.1.7 发布于 2026/08/20(2 个月前);至今共发布 100 个版本,其中过去 12 个月发布了 9 个;首次发布于 2019/11/20。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。