chore: update

Timeless0911 · Timeless0911 · commit f5b339c13cec · 2025-06-27T13:54:30.000+08:00
diff --git a/biome.json b/biome.json
@@ -1,5 +1,5 @@
 {
-  "$schema": "https://biomejs.dev/schemas/2.0.4/schema.json",
+  "$schema": "https://biomejs.dev/schemas/2.0.5/schema.json",
   "assist": {
     "actions": {
       "source": {
diff --git a/website/docs/en/blog/introducing-rslib.mdx b/website/docs/en/blog/introducing-rslib.mdx
@@ -133,7 +133,6 @@ Beyond common JavaScript library development solutions, based on Rspack and the
 - **Share Rspack and Rsbuild Ecosystem**
 
   Based on the Rspack and Rsbuild ecosystem, Rslib can reuse a series of ecosystem features, including but not limited to:
-
   - Use [Storybook](https://storybook.rsbuild.rs/guide/integrations/rslib.html) to directly read Rslib's configuration files for UI component library development debugging.
   - Use [Rsdoctor](https://rsdoctor.rs/) for build performance and output analysis.
   - Use [Node.js polyfill](https://github.com/rspack-contrib/rsbuild-plugin-node-polyfill) plugin to develop cross-runtime libraries.
diff --git a/website/docs/en/guide/advanced/dts.mdx b/website/docs/en/guide/advanced/dts.mdx
@@ -19,7 +19,6 @@ TypeScript Declaration Files provide type information for JavaScript code. Decla
 Bundle declaration files involves bundling multiple TypeScript declaration files into a single declaration file.
 
 - **Pros:**
-
   - **Simplified Management**: Simplifies the management and referencing of type files.
   - **Easy Distribution**: Reduces the number of files users need to handle when using the library.
 
@@ -32,7 +31,6 @@ Bundle declaration files involves bundling multiple TypeScript declaration files
 Bundleless declaration files involves generating a separate declaration file for each module in the library, just like `tsc` does.
 
 - **Pros:**
-
   - **Modular**: Each module has its own type definitions, making maintenance and debugging easier.
   - **Flexibility**: Suitable for large projects, avoiding the complexity of a single file.
 
diff --git a/website/docs/en/guide/advanced/module-federation.mdx b/website/docs/en/guide/advanced/module-federation.mdx
@@ -175,7 +175,6 @@ Then run the `dev` command can start the Module Federation development mode, ena
 First, set up Storybook with the Rslib project. You can refer to the [Storybook chapter](/guide/advanced/storybook) to learn how to do this. In this chapter, we will use React as the framework for our example.
 
 1. Install the following Storybook addons to let Storybook work with Rslib Module Federation:
-
    - [storybook-addon-rslib](https://www.npmjs.com/package/storybook-addon-rslib): Storybook addon that let Storybook to load the Rslib config.
    - [@module-federation/storybook-addon](https://www.npmjs.com/package/@module-federation/rsbuild-plugin): Storybook addon that set up the Module Federation config for Storybook.
 
diff --git a/website/docs/en/guide/advanced/output-compatibility.mdx b/website/docs/en/guide/advanced/output-compatibility.mdx
@@ -99,7 +99,6 @@ export default defineConfig({
 
 - For projects with `bundle` enabled, the Node Polyfill will be injected and included in the output.
 - For projects with `bundle` disabled, polyfills are not injected into the output by default. To avoid inlining the polyfill in every module, the modules are externalized and need to be added to dependencies manually, follow these steps:
-
   1. Configure `output.external` with `resolvedPolyfillToModules`, which you can import from [@rsbuild/plugin-node-polyfill](https://github.com/rspack-contrib/rsbuild-plugin-node-polyfill). This will externalize the polyfill modules to the installed polyfill dependencies.
   2. Install used polyfill modules as dependencies.
 
diff --git a/website/docs/en/guide/advanced/storybook.mdx b/website/docs/en/guide/advanced/storybook.mdx
@@ -24,7 +24,6 @@ Set up a Storybook project with an existing Rslib project. To use React, Vue 3,
 Using React as an example, at this step you need to:
 
 1. Install the dependencies for Storybook Rsbuild React framework. The essential ones include
-
    - [storybook](https://www.npmjs.com/package/storybook): The Storybook core.
    - [@storybook/addon-essentials](https://www.npmjs.com/package/@storybook/addon-essentials): a curated collection of addons to bring out the best of Storybook.
    - [@rsbuild/core](https://www.npmjs.com/package/@rsbuild/core): Storybook builder.
diff --git a/website/docs/en/guide/basic/output-format.mdx b/website/docs/en/guide/basic/output-format.mdx
@@ -50,14 +50,12 @@ shipping only ESM is the best choice for libraries that are intended to be used
 The community is migrating to ESM, but there are still many projects using CJS. If you want to support both ESM and CJS, you can publish a dual package. For most library authors, offering dual formats is a safer and smoother way to access the best of both worlds. You could read antfu' blog post [Publish ESM and CJS packages](https://antfu.me/posts/publish-esm-and-cjs) for more details.
 
 - **Pros:**
-
   - Wider compatibility: Dual packages support both modern ESM environments and legacy CJS environments, ensuring broader usage across different ecosystems.
   - Gradual migration: Developers can gradually transition from CJS to ESM without breaking existing projects, allowing for smoother adoption of the new standard.
   - Flexibility for consumers: Users of the package can choose which module system best fits their project, providing flexibility in different build tools and environments.
   - Cross-runtime support: Dual packages can work in multiple runtimes, such as Node.js and browsers, without requiring additional bundling or transpilation.
 
 - **Cons:**
-
   - Increased complexity: Maintaining two module formats adds complexity to the build process, requiring additional configuration and testing to ensure both versions work correctly.
   - Dual package hazard: Mixing ESM and CJS can lead to issues such as broken instanceof checks or unexpected behavior when dependencies are loaded in different formats.
 
diff --git a/website/docs/zh/blog/introducing-rslib.mdx b/website/docs/zh/blog/introducing-rslib.mdx
@@ -133,7 +133,6 @@ Rslib 提供了一套全面的库构建解决方案，涵盖了目前大部分
 - **共享 Rspack 和 Rsbuild 生态**
 
   基于 Rspack 和 Rsbuild 生态，Rslib 能复用一系列生态能力，包括但不限于：
-
   - 使用 [Storybook](https://storybook.rsbuild.rs/guide/integrations/rslib.html) 直接读取 Rslib 的配置文件进行 UI 组件库开发调试。
   - 使用 [Rsdoctor](https://rsdoctor.rs/) 进行构建性能及产物分析。
   - 使用 [Node.js polyfill](https://github.com/rspack-contrib/rsbuild-plugin-node-polyfill) 插件开发跨运行时的库。
diff --git a/website/docs/zh/guide/advanced/dts.mdx b/website/docs/zh/guide/advanced/dts.mdx
@@ -19,7 +19,6 @@ TypeScript 类型声明文件提供 JavaScript 代码的类型信息。类型声
 Bundle 类型将多个 TypeScript 声明文件打包到一个声明文件中。
 
 - **优势:**
-
   - **简化管理**: 简化类型文件的管理和引用。
   - **容易分发**: 减少用户使用库时需要处理的文件数量。
 
@@ -32,7 +31,6 @@ Bundle 类型将多个 TypeScript 声明文件打包到一个声明文件中。
 Bundleless 类型为库中的每个模块生成单独的声明文件，就像 `tsc` 一样。
 
 - **优势:**
-
   - **模块化**: 每个模块都有自己的类型定义，使维护和调试更容易。
   - **灵活**: 适合大型项目，避免单个文件的复杂性。
 
diff --git a/website/docs/zh/guide/advanced/module-federation.mdx b/website/docs/zh/guide/advanced/module-federation.mdx
@@ -175,7 +175,6 @@ Rslib 支持使用 Storybook 开发 Rslib 模块联邦项目。
 首先，在 Rslib 项目中配置 Storybook。你可以参考 [Storybook 章节](/guide/advanced/storybook)来了解如何执行此操作。在本章中，我们将使用 React 框架作为示例。
 
 1. 安装以下 Storybook addon，让 Storybook 与 Rslib 模块联邦一起使用:
-
    - [storybook-addon-rslib](https://www.npmjs.com/package/storybook-addon-rslib): Storybook addon 会让 Storybook 加载 Rslib 配置.
    - [@module-federation/storybook-addon](https://www.npmjs.com/package/@module-federation/rsbuild-plugin): Storybook 插件，为 Storybook 设置模块联邦配置。
 
diff --git a/website/docs/zh/guide/advanced/output-compatibility.mdx b/website/docs/zh/guide/advanced/output-compatibility.mdx
@@ -99,7 +99,6 @@ export default defineConfig({
 
 - 对于启用了 `bundle` 的项目，Node Polyfill 将被注入并包含在输出中。
 - 对于未启用 `bundle` 的项目，默认情况下不会注入 polyfill。为了避免在每个模块中内联 polyfill，模块需要被 external，并手动添加到依赖中，请按照以下步骤操作：
-
   1. 配置 `output.external` 和 `resolvedPolyfillToModules`，你可以从 [@rsbuild/plugin-node-polyfill](https://github.com/rspack-contrib/rsbuild-plugin-node-polyfill) 导入。这将 polyfill 模块 external 到已安装的 polyfill 依赖中。
   2. 安装使用的 polyfill 模块作为依赖。
 
diff --git a/website/docs/zh/guide/advanced/storybook.mdx b/website/docs/zh/guide/advanced/storybook.mdx
@@ -24,7 +24,6 @@ import { Tab, Tabs } from 'rspress/theme';
 以 React 为例，在这一步你需要：
 
 1. 安装 Storybook Rsbuild React 框架的依赖。必要的依赖包括
-
    - [storybook](https://www.npmjs.com/package/storybook)：Storybook core 包。
    - [@storybook/addon-essentials](https://www.npmjs.com/package/@storybook/addon-essentials)：精选的插件集合，以充分发挥 Storybook 的作用。
    - [@rsbuild/core](https://www.npmjs.com/package/@rsbuild/core)：Storybook 构建器。
diff --git a/website/docs/zh/guide/basic/output-format.mdx b/website/docs/zh/guide/basic/output-format.mdx
@@ -50,14 +50,12 @@ Rslib 支持多种 JavaScript 文件的输出格式：[ESM](#esm--cjs)、[CJS](#
 社区正在向 ESM 迁移，但仍有许多项目在使用 CJS。如果你想同时支持 ESM 和 CJS，可以发布一个双重包。对于大多数库作者来说，提供双重格式是一种更安全、更平滑的方式，可以同时享受两种格式的优点。你可以阅读 antfu 的博客文章 [在一个包中发布 ESM 和 CJS](https://antfu.me/posts/publish-esm-and-cjs) 了解更多详情。
 
 - **优点:**
-
   - 更广泛的兼容性：双重包支持现代 ESM 环境和旧版 CJS 环境，确保在不同生态系统中更广泛的使用。
   - 渐进式迁移：开发者可以逐步从 CJS 迁移到 ESM，而无需破坏现有项目，从而更平滑地采用新标准。
   - 灵活性：用户可以根据自己的项目选择最适合的模块系统，在不同的构建工具和环境中提供灵活性。
   - 跨运行时支持：双重包可以在多个运行时中工作，例如 Node.js 和浏览器，而无需额外的打包或转译。
 
 - **缺点:**
-
   - 增加复杂性：维护两种模块格式会增加构建过程的复杂性，需要额外的配置和测试，以确保两种版本都能正常工作。
   - 双重包风险：混合 ESM 和 CJS 可能会导致实例检查失败或依赖项在不同格式中加载时出现意外行为。
 

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,5 @@`
`1`	`1`	`{`
`2`		`- "$schema": "https://biomejs.dev/schemas/2.0.4/schema.json",`
	`2`	`+ "$schema": "https://biomejs.dev/schemas/2.0.5/schema.json",`
`3`	`3`	`"assist": {`
`4`	`4`	`"actions": {`
`5`	`5`	`"source": {`