@bleedingdev/modern-js-main-doc 3.5.0-ultramodern.3 → 3.5.0-ultramodern.31

package/docs/en/apis/app/hooks/src/routes.mdx

@@ -85,6 +85,6 @@ export default () => {
 ```
 
 :::note
-`<Outlet>` is a new API in React Router 7. For details, see [Outlet](https://reactrouter.com/en/main/components/outlet#outlet).
+`<Outlet>` is an API provided by React Router. For details, see [Outlet](https://reactrouter.com/en/main/components/outlet#outlet).
 
 :::

package/docs/en/apis/app/runtime/router/router.mdx

@@ -6,7 +6,7 @@ sidebar_position: 1
 # router
 
 :::info
-The router solution based on [react-router v7](https://reactrouter.com/).
+The router solution based on [react-router](https://reactrouter.com/).
 
 This page documents the React Router runtime export (`@modern-js/runtime/router`).  
 If your app uses TanStack Router (`--router tanstack`), use `@modern-js/plugin-tanstack/runtime` and refer to TanStack Router API docs.

package/docs/en/configure/app/bff/effect.mdx

@@ -197,24 +197,31 @@ The generated `api.client.*` API only exists for loader-materialized `@api/index
 ## Effect cohort
 
 UltraModern-generated workspaces pin the framework-compatible Effect cohort
-through `pnpm-workspace.yaml` overrides. For `3.5.0-ultramodern.3`, generated
-apps use:
+through `pnpm-workspace.yaml` overrides. For the current UltraModern cohort,
+generated apps use:
 
 ```yaml
+minimumReleaseAgeExclude:
+  - 'effect@4.0.0-beta.92'
+  - '@effect/opentelemetry@4.0.0-beta.92'
+
 trustPolicyExclude:
-  - '@effect/opentelemetry@4.0.0-beta.91'
+  - 'effect@4.0.0-beta.92'
+  - '@effect/opentelemetry@4.0.0-beta.92'
 
 overrides:
-  '@effect/vitest': 4.0.0-beta.91
-  effect: 4.0.0-beta.91
+  '@effect/opentelemetry': 4.0.0-beta.92
+  '@effect/vitest': 4.0.0-beta.92
+  effect: 4.0.0-beta.92
 ```
 
 Do not add a different direct `effect` version in an app package. A mismatched
 Effect beta can fail while building layers or HTTP middleware because runtime
 services come from different package instances. Keep the generated
-`trustPolicyExclude` entry with the same Effect cohort; it handles the
-`@effect/opentelemetry` trusted-publisher to provenance metadata transition
-without weakening UltraModern API architecture checks.
+policy exclusion entries with the same Effect cohort; they handle the
+framework-selected Effect beta versions before the 24-hour maturity window and
+the `effect`/`@effect/opentelemetry` trusted-publisher to provenance metadata
+transition without weakening UltraModern API architecture checks.
 
 ## Contract tests
 

package/docs/en/configure/app/performance/build-cache.mdx

@@ -28,6 +28,11 @@ type BuildCacheConfig =
 
 Controls the caching behavior during the build process.
 
+When persistent Rspack cache is enabled, Modern.js treats `cacheDirectory` as a
+base directory and stores each Rsbuild/Rspack environment in its own child
+directory, such as `client`, `server`, or `workerSSR`. This avoids concurrent
+environment compilers writing to the same filesystem cache root.
+
 Modern.js will enable build cache by default to improve the compile speed. You can disable the build cache by setting it to `false`:
 
 ```js

package/docs/en/guides/basic-features/routes/routes.mdx

@@ -4,7 +4,7 @@ sidebar_position: 2
 
 # Routing
 
-Modern.js supports conventional routing on top of both [React Router v7](https://reactrouter.com/en/main) and [TanStack Router](https://tanstack.com/router), offering file convention-based routing capabilities and supporting the industry-popular **nested routing** pattern. When an entry is recognized as [conventional routing](/guides/concept/entries.html#conventional-routing), Modern.js automatically generates the corresponding routing structure based on the file system.
+Modern.js supports conventional routing on top of both [React Router](https://reactrouter.com/en/main) and [TanStack Router](https://tanstack.com/router), offering file convention-based routing capabilities and supporting the industry-popular **nested routing** pattern. When an entry is recognized as [conventional routing](/guides/concept/entries.html#conventional-routing), Modern.js automatically generates the corresponding routing structure based on the file system.
 
 :::note
 
@@ -93,7 +93,7 @@ export default () => {
 
 :::note
 
-`<Outlet>` is an API provided by React Router v7. For more details, see [Outlet](https://reactrouter.com/en/main/components/outlet#outlet).
+`<Outlet>` is an API provided by React Router. For more details, see [Outlet](https://reactrouter.com/en/main/components/outlet#outlet).
 
 :::
 

package/docs/en/guides/concept/entries.mdx

@@ -156,7 +156,7 @@ If there is an `App.tsx?` file in the entry, this entry is a self-controlled rou
 │   └── App.tsx
 ```
 
-For the entry defined as `src/App.tsx`, Modern.js does not perform additional routing operations. Developers can use the [React Router v7](https://reactrouter.com/en/main) API to set up client-side routes, or not set up client-side routes. For example, the following code sets up client-side routes in the application:
+For the entry defined as `src/App.tsx`, Modern.js does not perform additional routing operations. Developers can use the [React Router](https://reactrouter.com/en/main) API to set up client-side routes, or not set up client-side routes. For example, the following code sets up client-side routes in the application:
 
 ```tsx title="src/App.tsx"
 import { BrowserRouter, Route, Routes } from '@modern-js/runtime/router';

package/docs/en/guides/get-started/tech-stack.mdx

@@ -19,7 +19,7 @@ Rsbuild supports building Vue applications. If you need to use Vue, you can refe
 Modern.js provides two first-party routing frameworks:
 
 - [TanStack Router](https://tanstack.com/router) (UltraModern default), via `@modern-js/plugin-tanstack/runtime`.
-- [React Router v7](https://reactrouter.com/en/main) (compatibility path), via `@modern-js/runtime/router`.
+- [React Router](https://reactrouter.com/en/main), via `@modern-js/runtime/router`.
 
 When creating an UltraModern project, TanStack Router is included by default:
 

package/docs/en/guides/get-started/ultramodern.mdx

@@ -78,20 +78,58 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
 
-Strict generated API migration requires `3.5.0-ultramodern.3` or newer.
+### Migrating to `3.5.0-ultramodern.18`
+
+Use `3.5.0-ultramodern.18` or newer for localized Cloudflare SSR workspaces.
+This cohort moves bare locale-root redirects into the framework-owned
+Cloudflare Worker entry and the i18n server runtime. A request for `/` is
+redirected server-side with `302` to the negotiated locale path, for example
+`/cs` for `Accept-Language: cs-CZ` or `/en` for English and fallback traffic.
+
+Existing generated workspaces should upgrade the whole BleedingDev Modern
+package cohort together:
+
+```bash
+pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.18 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.18
+pnpm install
+pnpm check
+pnpm build
+pnpm cloudflare:build
+```
+
+For deployed Cloudflare Workers, redeploy after the cohort update and verify
+the root response before accepting the migration:
+
+```bash
+curl -I -H 'Accept-Language: cs-CZ,cs;q=0.9,en;q=0.1' https://<worker-host>/
+```
+
+The expected response is `302` with `Location: /cs` or the matching locale,
+`Cache-Control: private, no-store`, and `Vary` covering the locale detection
+headers. Following the redirect should return the SSR locale page with the
+matching document language and i18n SSR data.
+
+Do not fix older root `404` responses by adding app-owned root route files,
+client-side redirects, custom navigation wrappers, Cloudflare Worker
+postprocessing, generated output edits, or local redirect shims. If `/` still
+returns `404` after upgrading, confirm the production build log shows
+`Modern.js Framework v3.5.0-ultramodern.18` or newer and redeploy the Worker.
+
+Strict generated API migration requires `3.5.0-ultramodern.10` or newer.
 `3.4.0-ultramodern.20` and earlier cohorts do not include this full direct
 `api/index.ts` generator, generated `.mts` checks, strict Oxlint boundary rule
 set, Effect cohort overrides, and strict Effect migration command. Agents that
 cannot install that BleedingDev cohort yet should use the local Modern.js
-workspace for migration validation; otherwise pin `3.5.0-ultramodern.3` or
+workspace for migration validation; otherwise pin `3.5.0-ultramodern.10` or
 newer with `--ultramodern-package-version`.
 
 Before hand-editing package aliases or generated metadata, run the framework
 migration command from the target workspace:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.3 ultramodern \
-  migrate-strict-effect --version 3.5.0-ultramodern.3
+pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.10 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.10
 pnpm api:check
 pnpm contract:check
 ```
@@ -105,11 +143,13 @@ migration work: move code to `shared/api.ts`, `api/index.ts`, and
 and `src/effect`.
 
 Generated strict Effect workspaces pin the compatible Effect cohort with pnpm
-overrides: `effect@4.0.0-beta.91` and `@effect/vitest@4.0.0-beta.91`. Do not
-add app-local direct Effect versions that disagree with those overrides. They
-also carry a generated pnpm trust-policy exclusion for
-`@effect/opentelemetry@4.0.0-beta.91` so pnpm no-downgrade checks do not block
-the Effect beta cohort's trusted-publisher to provenance metadata transition.
+overrides: `effect@4.0.0-beta.92`, `@effect/opentelemetry@4.0.0-beta.92`,
+and `@effect/vitest@4.0.0-beta.92`. Do not add app-local direct Effect
+versions that disagree with those overrides. They also carry generated pnpm
+policy exclusions for `effect@4.0.0-beta.92` and
+`@effect/opentelemetry@4.0.0-beta.92` so the framework-selected Effect beta
+cohort is not blocked by the 24-hour age gate or trusted-publisher to
+provenance metadata transition.
 
 Gradual migration means old, unmigrated Modern.js apps can keep their existing
 runtime until they are converted. Once a surface is generated or migrated as
@@ -188,9 +228,10 @@ instead of patching generated output by hand.
 Cloudflare D1 bindings are first-class on `deploy.worker.d1Databases`; use that
 config instead of app-local postprocessing when a generated app owns D1
 migrations. Cloudflare public output excludes server-only `api` and `shared`
-directories by default, and generated Modern/Rspack caches are isolated per app
-and build target so local `build` and `cloudflare:build` runs do not share the
-same Rspack cache directory.
+directories by default, and generated Modern/Rspack output roots, temp
+directories, and caches are isolated per app, build target, and Rspack
+environment so local `build`, `cloudflare:build`, and multi-environment
+compilers do not share mutable build state.
 
 ## Human Workflow
 
@@ -362,7 +403,7 @@ Cloudflare and Zephyr proof:
 ULTRAMODERN_PUBLIC_URL_SHELL_SUPER_APP=https://shell-super-app.example.workers.dev \
 ULTRAMODERN_PUBLIC_URL_TRANSPORTATION=https://transportation.example.workers.dev \
 ULTRAMODERN_PUBLIC_URL_PAYMENTS=https://payments.example.workers.dev \
-mise exec -- pnpm cloudflare:proof -- --require-public-urls
+mise exec -- pnpm cloudflare:proof --require-public-urls
 ```
 
 Live Cloudflare and Zephyr proof requires public Worker URLs and Zephyr credentials. Without those, the repo can validate generated contracts, local builds, local Cloudflare output, dry-run Zephyr evidence plans, and local evidence schemas, but it cannot prove shell-driven live version selection.

package/docs/en/tutorials/examples/csr-auth.mdx

@@ -4,7 +4,7 @@ title: Route Authorization
 
 # Route Authorization
 
-Modern.js defaults to the convention-based routing based on React Router v7. For more details, please refer to [Routing](/guides/basic-features/routes/routes#routing).
+Modern.js defaults to the convention-based routing based on React Router. For more details, please refer to [Routing](/guides/basic-features/routes/routes#routing).
 
 In a web application, if there are multiple routes, we may need to authorize access to some of them before accessing them. For example, in the following scenario:
 

package/docs/zh/apis/app/hooks/src/routes.mdx

@@ -85,6 +85,6 @@ export default () => {
 ```
 
 :::note
-`<Outlet>` 是 React Router v7 中新的 API，详情可以查看 [Outlet](https://reactrouter.com/en/main/components/outlet#outlet).
+`<Outlet>` 是 React Router 提供的 API，详情可以查看 [Outlet](https://reactrouter.com/en/main/components/outlet#outlet).
 
 :::

package/docs/zh/configure/app/bff/effect.mdx

@@ -195,22 +195,28 @@ export default defineConfig({
 ## Effect 版本组
 
 UltraModern 生成的 workspace 会通过 `pnpm-workspace.yaml` overrides 锁定与框架兼容的
-Effect 版本组。`3.5.0-ultramodern.3` 使用：
+Effect 版本组。当前 UltraModern 版本组使用：
 
 ```yaml
+minimumReleaseAgeExclude:
+  - 'effect@4.0.0-beta.92'
+  - '@effect/opentelemetry@4.0.0-beta.92'
+
 trustPolicyExclude:
-  - '@effect/opentelemetry@4.0.0-beta.91'
+  - 'effect@4.0.0-beta.92'
+  - '@effect/opentelemetry@4.0.0-beta.92'
 
 overrides:
-  '@effect/vitest': 4.0.0-beta.91
-  effect: 4.0.0-beta.91
+  '@effect/opentelemetry': 4.0.0-beta.92
+  '@effect/vitest': 4.0.0-beta.92
+  effect: 4.0.0-beta.92
 ```
 
 不要在应用包里添加不同版本的直接 `effect` 依赖。Effect beta 不一致时，Layer 或 HTTP
-middleware 构建可能因为运行时 service 来自不同包实例而失败。保留生成的
-`trustPolicyExclude` 条目并让它跟随同一个 Effect 版本组；它用于处理
-`@effect/opentelemetry` 从 trusted-publisher metadata 迁移到 provenance attestation
-时的 pnpm no-downgrade 检查。
+middleware 构建可能因为运行时 service 来自不同包实例而失败。保留生成的 policy
+exclusion 条目并让它跟随同一个 Effect 版本组；它用于处理框架选定 Effect beta 版本在
+24 小时成熟期内的安装，以及 `effect` 和 `@effect/opentelemetry` 从 trusted-publisher
+metadata 迁移到 provenance attestation 时的 pnpm no-downgrade 检查。
 
 ## 契约测试
 

package/docs/zh/configure/app/performance/build-cache.mdx

@@ -28,6 +28,10 @@ type BuildCacheConfig =
 
 控制 Modern.js 在构建过程中的缓存行为。
 
+启用 Rspack 持久化缓存时，Modern.js 会把 `cacheDirectory` 视为基础目录，并为每个
+Rsbuild/Rspack environment 写入独立子目录，例如 `client`、`server` 或
+`workerSSR`。这样可以避免并发 environment compiler 写入同一个文件系统 cache 根目录。
+
 在构建时，Modern.js 默认会开启构建缓存来提升二次构建的速度。如果不希望缓存，你可以将 `buildCache` 置为 `false` 将其禁用掉：
 
 ```js

package/docs/zh/guides/basic-features/routes/routes.mdx

@@ -4,7 +4,7 @@ sidebar_position: 2
 
 # 路由基础
 
-Modern.js 的约定式路由支持基于 [React Router 7](https://reactrouter.com/en/main) 和 [TanStack Router](https://tanstack.com/router) 两套框架，提供基于文件约定的路由能力，并支持业界流行的约定式路由模式：**嵌套路由**。当入口被识别为 [约定式路由](/guides/concept/entries.html#约定式路由) 时，Modern.js 会自动基于文件系统，生成对应的路由结构。
+Modern.js 的约定式路由支持基于 [React Router](https://reactrouter.com/en/main) 和 [TanStack Router](https://tanstack.com/router) 两套框架，提供基于文件约定的路由能力，并支持业界流行的约定式路由模式：**嵌套路由**。当入口被识别为 [约定式路由](/guides/concept/entries.html#约定式路由) 时，Modern.js 会自动基于文件系统，生成对应的路由结构。
 
 :::note
 
@@ -91,7 +91,7 @@ export default () => {
 
 :::note
 
-`<Outlet>` 是 React Router v7 中提供的 API，详情可以查看 [Outlet](https://reactrouter.com/en/main/components/outlet#outlet)。
+`<Outlet>` 是 React Router 提供的 API，详情可以查看 [Outlet](https://reactrouter.com/en/main/components/outlet#outlet)。
 
 :::
 

package/docs/zh/guides/concept/entries.mdx

@@ -156,7 +156,7 @@ src/
 │   └── App.tsx
 ```
 
-以 `src/App.tsx` 为约定的入口，Modern.js 不会对路由做额外的操作，开发者可以使用 [React Router v7](https://reactrouter.com/en/main) 的 API 设置客户端路由，或不设置客户端路由。例如以下代码，在应用中自行设置了客户端路由：
+以 `src/App.tsx` 为约定的入口，Modern.js 不会对路由做额外的操作，开发者可以使用 [React Router](https://reactrouter.com/en/main) 的 API 设置客户端路由，或不设置客户端路由。例如以下代码，在应用中自行设置了客户端路由：
 
 ```tsx title="src/App.tsx"
 import { BrowserRouter, Route, Routes } from '@modern-js/runtime/router';

package/docs/zh/guides/get-started/tech-stack.mdx

@@ -19,7 +19,7 @@ Modern.js 底层的 Rsbuild 支持构建 Vue 应用，如果你需要使用 Vue
 Modern.js 提供两套一方路由方案：
 
 - 默认使用 [TanStack Router](https://tanstack.com/router)，通过 `@modern-js/plugin-tanstack/runtime` 导出 API。
-- 兼容 [React Router 7](https://reactrouter.com/en/main)，通过 `@modern-js/runtime/router` 导出 API。
+- 兼容 [React Router](https://reactrouter.com/en/main)，通过 `@modern-js/runtime/router` 导出 API。
 
 创建 UltraModern 项目时，默认会包含 TanStack Router：
 

package/docs/zh/guides/get-started/ultramodern.mdx

@@ -71,18 +71,52 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
 
-严格生成 API 迁移要求 `3.5.0-ultramodern.3` 或更新版本。
+### 迁移到 `3.5.0-ultramodern.18`
+
+本地化 Cloudflare SSR workspace 应使用 `3.5.0-ultramodern.18` 或更新版本。这个
+cohort 将裸 locale root 重定向移动到框架拥有的 Cloudflare Worker entry 和 i18n
+server runtime 中。请求 `/` 时，框架会按语言协商在服务端返回 `302`，例如
+`Accept-Language: cs-CZ` 会跳转到 `/cs`，英语或 fallback 流量会跳转到 `/en`。
+
+既有生成 workspace 应整体升级同一个 BleedingDev Modern package cohort：
+
+```bash
+pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.18 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.18
+pnpm install
+pnpm check
+pnpm build
+pnpm cloudflare:build
+```
+
+Cloudflare Workers 已部署环境需要在 cohort 更新后重新部署，并在接受迁移前验证 root
+响应：
+
+```bash
+curl -I -H 'Accept-Language: cs-CZ,cs;q=0.9,en;q=0.1' https://<worker-host>/
+```
+
+期望响应是 `302`，并带有 `Location: /cs` 或匹配的 locale、
+`Cache-Control: private, no-store`，以及覆盖语言检测 Header 的 `Vary`。继续跟随该
+redirect 后，应返回匹配语言的 SSR 页面，文档语言和 i18n SSR 数据也应一致。
+
+不要通过 app 自有 root route、客户端 redirect、自定义导航 wrapper、Cloudflare Worker
+postprocess、生成产物编辑或本地 redirect shim 来修复旧版本的 root `404`。如果升级后
+`/` 仍然返回 `404`，先确认生产构建日志显示
+`Modern.js Framework v3.5.0-ultramodern.18` 或更新版本，然后重新部署 Worker。
+
+严格生成 API 迁移要求 `3.5.0-ultramodern.10` 或更新版本。
 `3.4.0-ultramodern.20` 及更早 cohort 还没有这套完整的直接
 `api/index.ts` 生成器、生成的 `.mts` 检查、严格 Oxlint 边界规则、Effect 版本组
 overrides 和严格 Effect 迁移命令。还不能安装该 BleedingDev cohort 的 agent 应使用本地
 Modern.js workspace 做迁移校验；否则用 `--ultramodern-package-version` 固定
-`3.5.0-ultramodern.3` 或更新版本。
+`3.5.0-ultramodern.10` 或更新版本。
 
 手写 package alias 或生成 metadata 之前，先在目标 workspace 运行框架迁移命令：
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.3 ultramodern \
-  migrate-strict-effect --version 3.5.0-ultramodern.3
+pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.10 ultramodern \
+  migrate-strict-effect --version 3.5.0-ultramodern.10
 pnpm api:check
 pnpm contract:check
 ```
@@ -94,11 +128,12 @@ pnpm overrides/trust policy 和 pnpm lockfile。剩余失败就是源码迁移
 `api/lambda`、`shared/effect` 和 `src/effect`。
 
 严格 Effect 生成 workspace 会通过 pnpm overrides 固定兼容版本组：
-`effect@4.0.0-beta.91` 和 `@effect/vitest@4.0.0-beta.91`。不要添加与这些
-overrides 冲突的 app 本地直接 Effect 版本。生成的 pnpm policy 还会为
-`@effect/opentelemetry@4.0.0-beta.91` 添加 trust-policy exclusion，避免 Effect beta
-版本组从 trusted-publisher metadata 迁移到 provenance attestation 时被 pnpm
-no-downgrade 检查误拦截。
+`effect@4.0.0-beta.92`、`@effect/opentelemetry@4.0.0-beta.92` 和
+`@effect/vitest@4.0.0-beta.92`。不要添加与这些 overrides 冲突的 app 本地直接
+Effect 版本。生成的 pnpm policy 还会为 `effect@4.0.0-beta.92` 和
+`@effect/opentelemetry@4.0.0-beta.92` 添加例外，避免框架选定的 Effect beta
+版本组被 24 小时成熟期检查，或从 trusted-publisher metadata 迁移到 provenance
+attestation 时被 no-downgrade 检查误拦截。
 
 渐进迁移意味着尚未迁移的旧 Modern.js app 可以保留现有 runtime，直到被转换为
 UltraModern。一个 surface 一旦生成为或迁移为 UltraModern HTTP API，就只能使用
@@ -161,8 +196,9 @@ Federation 冲突，都应在对应归属文件中修复，不要手写补丁覆
 
 Cloudflare D1 绑定使用一等配置 `deploy.worker.d1Databases`；生成 app 拥有 D1
 migration 时不要再用 app 本地 postprocess。Cloudflare public output 默认排除服务端
-`api` 和 `shared` 目录，并且生成的 Modern/Rspack cache 会按 app 与构建目标隔离，避免
-本地 `build` 与 `cloudflare:build` 共享同一个 Rspack cache 目录。
+`api` 和 `shared` 目录，并且生成的 Modern/Rspack 输出根目录、temp 目录和 cache
+会按 app、构建目标和 Rspack environment 隔离，避免本地 `build`、`cloudflare:build`
+以及多 environment compiler 共享可变构建状态。
 
 ## 人类工作流
 
@@ -320,7 +356,7 @@ Zephyr 证据：
 ULTRAMODERN_PUBLIC_URL_SHELL_SUPER_APP=https://shell-super-app.example.workers.dev \
 ULTRAMODERN_PUBLIC_URL_TRANSPORTATION=https://transportation.example.workers.dev \
 ULTRAMODERN_PUBLIC_URL_PAYMENTS=https://payments.example.workers.dev \
-mise exec -- pnpm cloudflare:proof -- --require-public-urls
+mise exec -- pnpm cloudflare:proof --require-public-urls
 ```
 
 Live Cloudflare 与 Zephyr 证明需要公开 Worker URL 和 Zephyr 凭据。没有这些凭据时，

package/docs/zh/tutorials/examples/csr-auth.mdx

@@ -4,7 +4,7 @@ title: 路由鉴权
 
 # 路由鉴权
 
-Modern.js 默认提供的路由方式是基于 React Router v7 的约定式路由，具体可查看[路由方案](/guides/basic-features/routes/routes#路由方案)。
+Modern.js 默认提供的路由方式是基于 React Router 的约定式路由，具体可查看[路由方案](/guides/basic-features/routes/routes#路由方案)。
 
 在一个 Web 应用中如果存在多个路由，我们可能需要对部分路由进行鉴权后才能访问。例如下面这个案例：
 

package/package.json

@@ -19,14 +19,14 @@
     "modern.js",
     "ultramodern.js"
   ],
-  "version": "3.5.0-ultramodern.3",
+  "version": "3.5.0-ultramodern.31",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"
   },
   "dependencies": {
     "mermaid": "^11.16.0",
-    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.3"
+    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.31"
   },
   "devDependencies": {
     "@rsbuild/plugin-sass": "2.0.0",