npm - @bleedingdev/modern-js-main-doc - Versions diffs - 3.5.0-ultramodern.6 → 3.5.0-ultramodern.76 - Mend

@bleedingdev/modern-js-main-doc 3.5.0-ultramodern.6 → 3.5.0-ultramodern.76

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (22) hide show

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

@@ -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 CHANGED Viewed

@@ -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/components/prerequisites.mdx CHANGED Viewed

@@ -9,7 +9,7 @@ import NodeVersion from '@site-docs-en/components/nodeVersion.mdx';
 It is recommended to use [pnpm](https://pnpm.io/installation) to manage dependencies:
 ```bash
-mise use pnpm@11.7.0
+mise use pnpm@11.16.0
 ```
 :::note

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

@@ -197,21 +197,22 @@ 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.6`, generated
-apps use:
+through `pnpm-workspace.yaml` overrides. For the current UltraModern cohort,
+generated apps use:
 ```yaml
 minimumReleaseAgeExclude:
-  - 'effect@4.0.0-beta.91'
-  - '@effect/opentelemetry@4.0.0-beta.91'
+  - 'effect@4.0.0-beta.97'
+  - '@effect/opentelemetry@4.0.0-beta.97'
 trustPolicyExclude:
-  - 'effect@4.0.0-beta.91'
-  - '@effect/opentelemetry@4.0.0-beta.91'
+  - 'effect@4.0.0-beta.97'
+  - '@effect/opentelemetry@4.0.0-beta.97'
 overrides:
-  '@effect/vitest': 4.0.0-beta.91
-  effect: 4.0.0-beta.91
+  '@effect/opentelemetry': 4.0.0-beta.97
+  '@effect/vitest': 4.0.0-beta.97
+  effect: 4.0.0-beta.97
 ```
 Do not add a different direct `effect` version in an app package. A mismatched

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

@@ -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/configure/app/tools/ts-checker.mdx CHANGED Viewed

@@ -19,7 +19,7 @@ const defaultOptions = {
     // use TypeScript Go checker by default
     tsgo: true,
     // use TS-Go native preview of user project
-    typescriptPath: require.resolve('@typescript/native-preview/package.json'),
+    typescriptPath: require.resolve('typescript/package.json'),
   },
   issue: {
     exclude: [
@@ -80,11 +80,11 @@ export default {
 Type checking runs on [TypeScript Go](https://github.com/microsoft/typescript-go) (`tsgo`) by default in this fork. The capability is provided by [`ts-checker-rspack-plugin`](https://github.com/rstackjs/ts-checker-rspack-plugin), which is integrated by [`@rsbuild/plugin-type-check`](https://github.com/rstackjs/rsbuild-plugin-type-check), and reduces type-checking time by about 5-10x.
-`@typescript/native-preview` ships with the builder, so no extra install is needed. To pin your own version, install it in your project:
+Modern.js prefers the project's stable `typescript` package when it is TypeScript 7 or newer, and falls back to `@typescript/native-preview` for projects still on the preview lane. To pin stable TypeScript 7, install it in your project:
-<PackageManagerTabs command="install @typescript/native-preview -D" />
+<PackageManagerTabs command="install typescript -D" />
-When `tsgo` is enabled, the default `typescript.typescriptPath` resolves to `@typescript/native-preview/package.json`. If you manually set `typescript.typescriptPath`, it must be an absolute path to `@typescript/native-preview/package.json`.
+When `tsgo` is enabled, the default `typescript.typescriptPath` resolves to `typescript/package.json` for TypeScript 7 projects. If you manually set `typescript.typescriptPath`, it must be an absolute path to `typescript/package.json` or `@typescript/native-preview/package.json`.
 To fall back to the classic TypeScript checker, set `typescript.tsgo` to `false` and make sure `typescript` is installed in your project:

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

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -78,20 +78,58 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
-Strict generated API migration requires `3.5.0-ultramodern.6` 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.6` 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.6 ultramodern \
-  migrate-strict-effect --version 3.5.0-ultramodern.6
+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,10 +143,11 @@ 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 generated pnpm policy exclusions for `effect@4.0.0-beta.91` and
-`@effect/opentelemetry@4.0.0-beta.91` so the framework-selected Effect beta
+overrides: `effect@4.0.0-beta.97`, `@effect/opentelemetry@4.0.0-beta.97`,
+and `@effect/vitest@4.0.0-beta.97`. 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.97` and
+`@effect/opentelemetry@4.0.0-beta.97` so the framework-selected Effect beta
 cohort is not blocked by the 24-hour age gate or trusted-publisher to
 provenance metadata transition.
@@ -171,8 +210,8 @@ Older repos with nested Effect entries and `verbatimModuleSyntax` should update
 the latest BleedingDev cohort instead of adding app-level `"type": "module"`
 metadata, Module Federation shims, or custom server wrappers. The framework BFF
 compiler normalizes CommonJS server output while generated app packages keep
-stable `typescript` for Module Federation DTS generation and use the pinned
-`@typescript/native-preview` toolchain for TS-Go checks.
+stable TypeScript 7 so Module Federation DTS generation and TS-Go checks use
+the same modern compiler lane.
 Cloudflare SSR deploys are also split by runtime responsibility: `.output` is an
 ESM module-worker package, while `.output/worker` remains a CommonJS package
@@ -189,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
@@ -311,10 +351,9 @@ Overlays are explicit CodeSmith generators that run after base workspace or
 MicroVertical generation. They extend generated output; they do not replace,
 inherit, or shadow the base templates. The generator and CodeSmith adapter are
 plain Node generator surfaces. The package build emits declaration files through
-the TS-Go toolchain. Generated app packages keep stable `typescript` for classic
-compiler consumers such as Module Federation DTS generation, while TS-Go uses
-the pinned `@typescript/native-preview` toolchain; runtime code does not depend
-on native-preview compiler internals.
+the TS-Go toolchain. Generated app packages keep stable `typescript` on TS7 so
+Module Federation DTS generation and TS-Go use the same compiler lane; runtime
+code does not depend on compiler internals.
 ### Runtime Contracts
@@ -341,7 +380,7 @@ The generated contract writes `.modernjs/ultramodern.json` with a
 - `packages/shared-design-tokens` owns the shared token layer and exports `./tokens.css`.
 - Shell CSS owns only shell base and overlay layers under `[data-app-id="shell-super-app"]`.
 - Each vertical owns one CSS layer, for example `[data-app-id="vertical-transportation"]` with app-local class prefixes.
-- Tailwind CSS v4 is local to each generated app through `@tailwindcss/postcss`; shared base styles must not be duplicated by verticals.
+- Tailwind CSS v4 is local to each generated app through `@rsbuild/plugin-tailwindcss`; shared base styles must not be duplicated by verticals.
 - SSR first paint requires shared token CSS and app-owned CSS to be emitted by Modern/Rspack assets. Vertical CSS is loaded through manifest ownership, not copied into shell source.
 Version switching must select UI, API, CSS, i18n JSON, and MF manifest evidence from the same vertical build marker. A shell render that only changes the UI marker is not enough.
@@ -363,7 +402,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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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/components/prerequisites.mdx CHANGED Viewed

@@ -9,7 +9,7 @@ import NodeVersion from '@site-docs/components/nodeVersion.mdx';
 推荐使用 [pnpm](https://pnpm.io/installation) 来管理依赖：
 ```bash
-mise use pnpm@11.7.0
+mise use pnpm@11.16.0
 ```
 :::note

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

@@ -195,20 +195,21 @@ export default defineConfig({
 ## Effect 版本组
 UltraModern 生成的 workspace 会通过 `pnpm-workspace.yaml` overrides 锁定与框架兼容的
-Effect 版本组。`3.5.0-ultramodern.6` 使用：
+Effect 版本组。当前 UltraModern 版本组使用：
 ```yaml
 minimumReleaseAgeExclude:
-  - 'effect@4.0.0-beta.91'
-  - '@effect/opentelemetry@4.0.0-beta.91'
+  - 'effect@4.0.0-beta.97'
+  - '@effect/opentelemetry@4.0.0-beta.97'
 trustPolicyExclude:
-  - 'effect@4.0.0-beta.91'
-  - '@effect/opentelemetry@4.0.0-beta.91'
+  - 'effect@4.0.0-beta.97'
+  - '@effect/opentelemetry@4.0.0-beta.97'
 overrides:
-  '@effect/vitest': 4.0.0-beta.91
-  effect: 4.0.0-beta.91
+  '@effect/opentelemetry': 4.0.0-beta.97
+  '@effect/vitest': 4.0.0-beta.97
+  effect: 4.0.0-beta.97
 ```
 不要在应用包里添加不同版本的直接 `effect` 依赖。Effect beta 不一致时，Layer 或 HTTP

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

@@ -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/configure/app/tools/ts-checker.mdx CHANGED Viewed

@@ -19,7 +19,7 @@ const defaultOptions = {
     // use TypeScript Go checker by default
     tsgo: true,
     // use TS-Go native preview of user project
-    typescriptPath: require.resolve('@typescript/native-preview/package.json'),
+    typescriptPath: require.resolve('typescript/package.json'),
   },
   issue: {
     exclude: [
@@ -80,11 +80,11 @@ export default {
 类型检查默认使用 [TypeScript Go](https://github.com/microsoft/typescript-go)（`tsgo`）。该能力由 [`@rsbuild/plugin-type-check`](https://github.com/rstackjs/rsbuild-plugin-type-check) 底层集成的 [`ts-checker-rspack-plugin`](https://github.com/rstackjs/ts-checker-rspack-plugin) 提供，可以将类型检查耗时减少约 5-10 倍。
-`@typescript/native-preview` 已随构建器内置，无需额外安装。如需固定版本，可在项目中自行安装：
+Modern.js 会优先使用项目内稳定版 `typescript`（TypeScript 7 或更新版本），仍在预览通道的项目会回退到 `@typescript/native-preview`。如需固定稳定版 TypeScript 7，可在项目中安装：
-<PackageManagerTabs command="install @typescript/native-preview -D" />
+<PackageManagerTabs command="install typescript -D" />
-开启 `tsgo` 后，默认的 `typescript.typescriptPath` 会解析到 `@typescript/native-preview/package.json`。如果你手动设置了 `typescript.typescriptPath`，它必须是指向 `@typescript/native-preview/package.json` 的绝对路径。
+开启 `tsgo` 后，TypeScript 7 项目默认的 `typescript.typescriptPath` 会解析到 `typescript/package.json`。如果你手动设置了 `typescript.typescriptPath`，它必须是指向 `typescript/package.json` 或 `@typescript/native-preview/package.json` 的绝对路径。
 如需回退到经典 TypeScript 检查器，请将 `typescript.tsgo` 设置为 `false`，并确保项目中安装了 `typescript`：

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

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -71,18 +71,52 @@ mise exec -- pnpm check
 mise exec -- pnpm build
 ```
-严格生成 API 迁移要求 `3.5.0-ultramodern.6` 或更新版本。
+### 迁移到 `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.6` 或更新版本。
+`3.5.0-ultramodern.10` 或更新版本。
 手写 package alias 或生成 metadata 之前，先在目标 workspace 运行框架迁移命令：
 ```bash
-pnpm dlx @bleedingdev/modern-js-create@3.5.0-ultramodern.6 ultramodern \
-  migrate-strict-effect --version 3.5.0-ultramodern.6
+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@4.0.0-beta.91` 和 `@effect/opentelemetry@4.0.0-beta.91` 添加例外，避免框架选定的
-Effect beta 版本组被 24 小时成熟期检查，或从 trusted-publisher metadata 迁移到
-provenance attestation 时被 no-downgrade 检查误拦截。
+`effect@4.0.0-beta.97`、`@effect/opentelemetry@4.0.0-beta.97` 和
+`@effect/vitest@4.0.0-beta.97`。不要添加与这些 overrides 冲突的 app 本地直接
+Effect 版本。生成的 pnpm policy 还会为 `effect@4.0.0-beta.97` 和
+`@effect/opentelemetry@4.0.0-beta.97` 添加例外，避免框架选定的 Effect beta
+版本组被 24 小时成熟期检查，或从 trusted-publisher metadata 迁移到 provenance
+attestation 时被 no-downgrade 检查误拦截。
 渐进迁移意味着尚未迁移的旧 Modern.js app 可以保留现有 runtime，直到被转换为
 UltraModern。一个 surface 一旦生成为或迁移为 UltraModern HTTP API，就只能使用
@@ -151,8 +186,8 @@ API group layer 一起提供。
 带有 Effect BFF 入口和 `verbatimModuleSyntax` 的旧仓库，应升级到最新的
 BleedingDev cohort，而不是给 app package 增加 `"type": "module"`、Module
 Federation shim 或自定义 server wrapper。框架 BFF compiler 会把服务端输出规范化为
-CommonJS，同时生成的 app package 继续为 Module Federation DTS 保留稳定的
-`typescript`，并使用固定的 `@typescript/native-preview` 工具链执行 TS-Go 检查。
+CommonJS，同时生成的 app package 会使用稳定版 TypeScript 7，让 Module Federation
+DTS 与 TS-Go 检查走同一条现代 compiler 通道。
 安装新 cohort 后，先运行生成的 `pnpm api:check` 与
 `scripts/validate-ultramodern-workspace.mts` 契约校验，再接受人工改动。topology、
@@ -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 共享可变构建状态。
 ## 人类工作流
@@ -272,9 +308,8 @@ JSON 契约缺失或不是对象、Tailwind 前缀冲突，都会报告归属契
 Overlays 是显式配置的 CodeSmith 生成器，会在基础 workspace 或 MicroVertical
 生成之后运行。它们只扩展生成结果，不替换、不继承、也不遮蔽基础模板。公开生成器与
 CodeSmith adapter 都是普通 Node 生成器入口。包构建通过 TS-Go 工具链产出声明文件；
-生成出来的 app package 为 Module Federation DTS 等传统 compiler consumer 保留稳定的
-`typescript`，TS-Go 则使用固定的 `@typescript/native-preview` 工具链；运行时代码不依赖
-native-preview compiler 内部实现。
+生成出来的 app package 会把稳定版 `typescript` 固定在 TS7，让 Module Federation
+DTS 与 TS-Go 使用同一条 compiler 通道；运行时代码不依赖 compiler 内部实现。
 ### 运行时契约
@@ -298,7 +333,7 @@ JSON-LD。公开路由 owner 可以在本地化路径旁显式添加 `jsonLd`，
 - `packages/shared-design-tokens` 拥有共享 token layer，并导出 `./tokens.css`。
 - Shell CSS 只拥有 `[data-app-id="shell-super-app"]` 下的 shell base 和 overlay layer。
 - 每个 vertical 拥有自己的 CSS layer，例如 `[data-app-id="vertical-transportation"]` 和应用本地 class 前缀。
-- Tailwind CSS v4 通过 `@tailwindcss/postcss` 保持在每个生成应用内部；共享 base style 不应由 vertical 重复定义。
+- Tailwind CSS v4 通过 `@rsbuild/plugin-tailwindcss` 保持在每个生成应用内部；共享 base style 不应由 vertical 重复定义。
 - SSR 首屏依赖 Modern/Rspack 产出共享 token CSS 和应用自己的 CSS。Vertical CSS 通过 manifest 归属加载，不复制到 shell 源码中。
 版本切换必须从同一个 vertical build marker 选择 UI、API、CSS、i18n JSON 与 MF manifest 证据。只切换 shell 渲染里的 UI marker 不足以证明完整版本切换。
@@ -320,7 +355,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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -19,32 +19,31 @@
     "modern.js",
     "ultramodern.js"
   ],
-  "version": "3.5.0-ultramodern.6",
+  "version": "3.5.0-ultramodern.76",
   "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.6"
+    "@modern-js/sandpack-react": "npm:@bleedingdev/modern-js-sandpack-react@3.5.0-ultramodern.76",
+    "mermaid": "^11.16.0"
   },
   "devDependencies": {
-    "@rsbuild/plugin-sass": "2.0.0",
-    "@rspress/core": "2.0.15",
-    "@rspress/plugin-llms": "2.0.15",
-    "@rspress/shared": "2.0.15",
-    "@shikijs/transformers": "^4.3.0",
+    "@rsbuild/plugin-sass": "2.0.1",
+    "@rspress/core": "2.0.17",
+    "@rspress/plugin-llms": "2.0.17",
+    "@rspress/shared": "2.0.17",
+    "@shikijs/transformers": "^4.3.1",
     "@types/fs-extra": "11.0.4",
-    "@types/node": "^26.0.1",
-    "@typescript/native-preview": "7.0.0-dev.20260628.1",
+    "@types/node": "^26.1.1",
+    "@typescript/native-preview": "7.0.0-dev.20260707.2",
     "classnames": "^2.5.1",
     "clsx": "^2.1.1",
-    "fs-extra": "^11.3.5",
+    "fs-extra": "^11.3.6",
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
     "rsbuild-plugin-open-graph": "1.1.3",
     "ts-node": "^10.9.2",
-    "typescript": "^6.0.3"
+    "typescript": "^7.0.2"
   },
   "scripts": {
     "dev": "rspress dev",