@bleedingdev/modern-js-main-doc 3.8.2-ultramodern.9 → 3.8.3-ultramodern.2

package/docs/en/community/showcase.mdx

@@ -1,14 +1,13 @@
 ---
 sidebar_position: 0
+title: Ecosystem
 ---
 
-# Showcase
+# Ecosystem
 
-Welcome to the Modern.js showcase page! Here, we present a collection of websites that have been built using Modern.js.
+UltraModern.js builds on a focused ecosystem of frameworks and tools. These projects provide the Effect, TanStack Router, build, documentation, and Module Federation foundations used by the fork.
 
-If you have built a website using Modern.js, we would love for you to share it with the community. Simply reply to the GitHub discussion thread with a link to your website. We will collect content on a regular basis and display it on the current page.
-
-## The Cases
+## Projects
 
 import { ShowcaseList } from '@site/src/components/ShowcaseList';
 

package/docs/en/components/init-app.mdx

@@ -3,26 +3,27 @@ workspaces. It does not require global installation and can be run on-demand
 using `pnpm dlx`.
 
 The supported pnpm command is the scoped package specifier:
-`pnpm dlx @bleedingdev/modern-js-create <target>`. Do not shorten it to
-`pnpm dlx modern-js-create`; there is no unscoped package by that name.
+`pnpm dlx @bleedingdev/modern-js-ultramodern-create <target>`. Do not shorten it
+to `pnpm dlx modern-js-ultramodern-create`; there is no unscoped package by
+that name.
 
 You can initialize the empty directory you are already in:
 
 ```bash
 mkdir myapp && cd myapp
-pnpm dlx @bleedingdev/modern-js-create .
+pnpm dlx @bleedingdev/modern-js-ultramodern-create .
 ```
 
 You can also create a project directly in a new directory:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create my-super-app
+pnpm dlx @bleedingdev/modern-js-ultramodern-create my-super-app
 ```
 
 To initialize with workspace protocol dependencies (for local monorepo testing of unreleased Modern.js packages):
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create my-super-app --workspace
+pnpm dlx @bleedingdev/modern-js-ultramodern-create my-super-app --workspace
 ```
 
 The BleedingDev create package will directly create the application without providing an interactive Q & A interface:
@@ -73,13 +74,13 @@ The default workspace starts shell-only and installs the published BleedingDev
 package aliases:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create my-super-app
+pnpm dlx @bleedingdev/modern-js-ultramodern-create my-super-app
 ```
 
 From a generated SuperApp workspace, add a business MicroVertical in place:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create transportation --vertical
+pnpm dlx @bleedingdev/modern-js-ultramodern-create transportation --vertical
 ```
 
 The `--vertical` command mutates the current workspace: it adds the vertical

package/docs/en/components/init-rspack-app.mdx

@@ -1,5 +1,3 @@
 ```bash
-$ pnpm dlx @bleedingdev/modern-js-create myapp
-? Please select the programming language: TS
-? Please select the package manager: pnpm
+$ pnpm dlx @bleedingdev/modern-js-ultramodern-create myapp
 ```

package/docs/en/components/prerequisites.mdx

@@ -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.21.0
+mise use pnpm@11.24.0
 ```
 
 :::note

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

@@ -54,7 +54,7 @@ would give your app a second Effect identity. Before setting
 `/effect-server`, `/effect-edge` or `/effect-client`, install the exact cohort:
 
 ```bash
-pnpm add effect@4.0.0-beta.107 @effect/opentelemetry@4.0.0-beta.107
+pnpm add effect@4.0.0-rc.112 @effect/opentelemetry@4.0.0-rc.112
 ```
 
 The pin is exact because UltraModern ships Effect as one lockstep cohort. Apps
@@ -219,17 +219,17 @@ generated apps use:
 
 ```yaml
 trustPolicyExclude:
-  - 'effect@4.0.0-beta.107'
-  - '@effect/opentelemetry@4.0.0-beta.107'
+  - 'effect@4.0.0-rc.112'
+  - '@effect/opentelemetry@4.0.0-rc.112'
 
 overrides:
-  '@effect/opentelemetry': 4.0.0-beta.107
-  '@effect/vitest': 4.0.0-beta.107
-  effect: 4.0.0-beta.107
+  '@effect/opentelemetry': 4.0.0-rc.112
+  '@effect/vitest': 4.0.0-rc.112
+  effect: 4.0.0-rc.112
 ```
 
 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
+Effect prerelease can fail while building layers or HTTP middleware because runtime
 services come from different package instances. The strict 24-hour release-age
 gate applies to installed packages; the current cohort has no Effect age
 exemption, and override-only `@effect/vitest` is not an installed approval

package/docs/en/guides/advanced-features/bff/frameworks.mdx

@@ -122,7 +122,7 @@ const response = await api.client.hello.ping({});
 
 The `api.client.*` surface is materialized by the BFF loader for `@api/index` imports. Do not import `api/index` directly and expect `client` to run in server code, scripts, or tests; direct entry imports expose the server runtime definition, and `client` is only a typed placeholder there.
 
-For UltraModern, Effect `HttpApi` plus Effect BFF is the single blessed authored HTTP path. Use `HttpApi` endpoints with `query`, `params`, `payload`, `success`, and declared errors such as `HttpApiSchema.status(...)`; implement them with `HttpApiBuilder.group(...).handle(...)` and `HttpApiBuilder.layer(...).pipe(Layer.provide(...))`, then default-export the entry as `defineEffectBff({ api, layer })`. See `packages/cli/plugin-bff/tests/effect-httpapi-schema-validation.test.ts` for the real shapes.
+For UltraModern, Effect `HttpApi` plus Effect BFF is the single blessed authored HTTP path. Use `HttpApi` endpoints with `query`, `params`, `payload`, `success`, and declared errors such as `HttpApiSchema.status(...)`; implement them with `HttpApiBuilder.group(...).handle(...)` and `HttpApiBuilder.layer(...).pipe(Layer.provide(...))`, then default-export the entry as `defineEffectBff({ api, layer })`. See `packages/server/bff-effect/tests/effect-edge-runtime.test.ts` for the live runtime shape.
 
 Hono and `api/lambda/**` are internal compatibility only and feature-frozen.
 

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

@@ -267,11 +267,11 @@ First, you need to configure the **Root Directory** as `packages/app` on the Ver
 
 <img src="https://sf16-sg.tiktokcdn.com/obj/eden-sg/lmeh7nuptpfnuhd/vercel-root-directory.png" />
 
-Specify Node.js runtime as `20.x`:
+Specify Node.js runtime as `26.7.0` or newer:
 
 ```json title="package.json"
 "engines": {
-  "node": "20.x"
+  "node": ">=26.7.0"
 }
 ```
 

package/docs/en/guides/get-started/quick-start.mdx

@@ -27,7 +27,7 @@ import DebugApp from '@site-docs-en/components/debug-app';
 
 ## Configuration
 
-In an UltraModern.js project created using `@bleedingdev/modern-js-create`, a `modern.config.ts` file is generated by default.
+In an UltraModern.js project created using `@bleedingdev/modern-js-ultramodern-create`, a `modern.config.ts` file is generated by default.
 
 You can modify the configuration through this file to override the default behavior of Modern.js. For example, to enable SSR, add the following configuration:
 

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

@@ -24,7 +24,7 @@ Modern.js provides two first-party routing frameworks:
 When creating an UltraModern project, TanStack Router is included by default:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create myapp
+pnpm dlx @bleedingdev/modern-js-ultramodern-create myapp
 ```
 
 Modern.js supports conventional routing, self-controlled routing, or other routing schemes. Please refer to ["Routing"](/guides/basic-features/routes/routes) to make your choice.

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

@@ -69,9 +69,9 @@ For an older generated workspace, migrate by treating the published cohort as
 the source of truth:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create@latest --help
-pnpm dlx @bleedingdev/modern-js-create@latest catalog --vertical --dry-run
-pnpm dlx @bleedingdev/modern-js-create@latest catalog --vertical
+pnpm dlx @bleedingdev/modern-js-ultramodern-create@latest --help
+pnpm dlx @bleedingdev/modern-js-ultramodern-create@latest catalog --vertical --dry-run
+pnpm dlx @bleedingdev/modern-js-ultramodern-create@latest catalog --vertical
 mise install
 mise exec -- pnpm install
 mise exec -- pnpm check
@@ -91,8 +91,8 @@ package cohort together. Resolve the current cohort version first, then run
 the matching migration:
 
 ```bash
-COHORT="$(npm view @bleedingdev/modern-js-create version)"
-pnpm dlx "@bleedingdev/modern-js-create@$COHORT" ultramodern \
+COHORT="$(npm view @bleedingdev/modern-js-ultramodern-create version)"
+pnpm dlx "@bleedingdev/modern-js-ultramodern-create@$COHORT" ultramodern \
   migrate-strict-effect --version "$COHORT"
 pnpm install
 pnpm check
@@ -130,8 +130,8 @@ Before hand-editing package aliases or generated metadata, run the framework
 migration command from the target workspace:
 
 ```bash
-COHORT="$(npm view @bleedingdev/modern-js-create version)"
-pnpm dlx "@bleedingdev/modern-js-create@$COHORT" ultramodern \
+COHORT="$(npm view @bleedingdev/modern-js-ultramodern-create version)"
+pnpm dlx "@bleedingdev/modern-js-ultramodern-create@$COHORT" ultramodern \
   migrate-strict-effect --version "$COHORT"
 pnpm api:check
 pnpm contract:check
@@ -146,8 +146,8 @@ 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.107`, `@effect/opentelemetry@4.0.0-beta.107`,
-and `@effect/vitest@4.0.0-beta.107`. Do not add app-local direct Effect
+overrides: `effect@4.0.0-rc.112`, `@effect/opentelemetry@4.0.0-rc.112`,
+and `@effect/vitest@4.0.0-rc.112`. Do not add app-local direct Effect
 versions that disagree with those overrides. The strict 24-hour release-age
 gate applies to installed packages; this cohort carries no Effect age
 exemption, and override-only `@effect/vitest` is not an installed approval
@@ -159,12 +159,21 @@ metadata transition; they are not release-age approvals.
 
 | Surface | Pin |
 | --- | --- |
-| Effect runtime and test cohort | `effect`, `@effect/opentelemetry`, and `@effect/vitest`: `4.0.0-beta.107` |
-| Effect compiler | `@effect/tsgo@0.36.2` |
-| TanStack Router | `@tanstack/react-router@1.170.25`, `@tanstack/router-core@1.171.21`, `@tanstack/history@1.162.1` |
-| Module Federation | `bridge-react`, `manifest`, `modern-js-v3`, and `rspack`: `2.8.2`; `@module-federation/node@2.7.49` |
-| React Router | `react-router@7.18.2` |
-| Node and package tooling | Node `26.7.0`, `@types/node@^26.2.0`, pnpm `11.21.0` |
+| Effect runtime and test cohort | `effect`, `@effect/opentelemetry`, and `@effect/vitest`: `4.0.0-rc.112` |
+| Effect compiler | `@effect/tsgo@0.37.0` |
+| Oxc and Ultracite | `oxlint@1.80.0`, `oxfmt@0.65.0`, `ultracite@7.10.6` |
+| TanStack Router | `@tanstack/react-router@1.170.32`, `@tanstack/router-core@1.171.27`, `@tanstack/history@1.162.1` |
+| Module Federation | `bridge-react`, `manifest`, `modern-js-v3`, and `rspack`: `2.9.0`; `@module-federation/node@2.7.50` |
+| Tailwind CSS | `tailwindcss@4.3.3` |
+| Node and package tooling | Node `26.7.0`, `@types/node@^26.2.0`, pnpm `11.24.0` |
+
+Generated workspaces default to Module Federation bridge-react's router-free
+base entry (`bridge.enableBridgeRouter: false`), with TanStack Router as the
+application router. Declaring `react-router` (or `react-router-dom`) as a
+direct dependency of an app marks it a React Router consumer: the
+generator/migration then emit `enableBridgeRouter: true` for that app's
+federation config, the workspace validator accepts it, and the UltraModern
+preset aliases `react-router`'s entrypoints for the app's own routing.
 
 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
@@ -248,6 +257,94 @@ 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.
 
+## Configure the public preset
+
+Use `presetUltramodern(appConfig, presetOptions)` inside the normal Modern.js
+`defineConfig` call:
+
+```ts title="modern.config.ts"
+import { defineConfig, presetUltramodern } from '@modern-js/app-tools';
+
+export default defineConfig(
+  presetUltramodern(
+    {
+      output: {
+        precompress: false,
+      },
+      server: {
+        telemetry: {
+          failLoudStartup: true,
+        },
+      },
+    },
+    {
+      appId: 'catalog',
+      enableModuleFederationSSR: false,
+      enableTelemetryExporters: false,
+    },
+  ),
+);
+```
+
+The first argument is ordinary `AppUserConfig`. It contains app-owned config
+and wins where it supplies an override. The second argument controls the
+preset itself. Use its typed options, such as `enableBffRequestId: false`,
+`enableTelemetry: false`, `enableTelemetryExporters: false`, and
+`enableModuleFederationSSR: false`, to turn preset features off.
+
+Composition follows the Modern.js config merge rules:
+
+- Nested records merge, so changing one nested field keeps its preset
+  siblings.
+- Scalars and `false` supplied by the app override preset values. Omitting a
+  field, or leaving it `undefined`, keeps the preset value.
+- Arrays and config hooks compose in preset-first order. Non-function array
+  entries are deduplicated by deep equality, while function entries are all
+  retained. An empty array or empty record does not clear values already
+  supplied by the preset.
+
+There is no generic reset sentinel. Use a typed preset option for preset-owned
+behavior and a normal app config override for app-owned behavior.
+
+`createPresetUltramodernConfig(options)` is an advanced API for inspecting or
+materializing a fresh preset config. Do not spread its result into another
+config object. Object spread is shallow, so replacing `server`, `output`, or
+another nested record can silently discard preset siblings. Use
+`presetUltramodern(...)` for authoring `modern.config.ts`.
+
+### Bare preset and generated workspace policy
+
+The preset and the workspace generator own different parts of the config:
+
+| Source | Identity | Remaining config |
+| --- | --- | --- |
+| Bare `createPresetUltramodernConfig()` result | Uses `appId: 'app'` and has no `deliveryUnit` | Uses the preset defaults. Telemetry stays enabled, but no exporter is configured until its endpoint is set. |
+| Generated app | Supplies the app-specific `appId` and stamped `deliveryUnit` | Inherits the other strict defaults from `presetUltramodern(...)`. |
+| Application | Supplies the first `appConfig` argument | Overrides app-owned fields through the normal Modern.js merge. |
+
+Keep the generated `appId` and `deliveryUnit` options intact. To change
+preset-owned behavior, use typed options such as
+`enableTelemetryExporters: false`,
+`enableTelemetry: false`, `enableBffRequestId: false`, or
+`enableModuleFederationSSR: false`. To change an app-owned field, put the
+override in the first argument, as in the example above.
+
+Telemetry exporter endpoints are unset by default:
+
+- `MODERN_TELEMETRY_OTLP_ENDPOINT` enables only the OTLP exporter.
+- `MODERN_TELEMETRY_VICTORIA_ENDPOINT` enables only the VictoriaMetrics
+  exporter.
+- Setting both enables both. Leaving both unset keeps the telemetry pipeline
+  enabled without configuring an exporter.
+
+The typed `otlpEndpoint` and `victoriaMetricsEndpoint` preset options provide
+the same per-exporter behavior without environment variables.
+
+```bash
+MODERN_TELEMETRY_OTLP_ENDPOINT=https://otel.example.com/v1/logs \
+  mise exec -- pnpm dev
+```
+
 ## Human Workflow
 
 The public BleedingDev create package has one supported generated product. The
@@ -257,7 +354,7 @@ BFF, Module Federation topology, generated quality gates, and Cloudflare deploy
 basics:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create myapp
+pnpm dlx @bleedingdev/modern-js-ultramodern-create myapp
 cd myapp
 mise install
 mise exec -- pnpm install
@@ -269,10 +366,10 @@ generate a demo domain by default. Add real business MicroVerticals when they
 become real ownership boundaries:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create transportation --vertical
-pnpm dlx @bleedingdev/modern-js-create food-delivery --vertical
-pnpm dlx @bleedingdev/modern-js-create payments --vertical
-pnpm dlx @bleedingdev/modern-js-create maps --vertical
+pnpm dlx @bleedingdev/modern-js-ultramodern-create transportation --vertical
+pnpm dlx @bleedingdev/modern-js-ultramodern-create food-delivery --vertical
+pnpm dlx @bleedingdev/modern-js-ultramodern-create payments --vertical
+pnpm dlx @bleedingdev/modern-js-ultramodern-create maps --vertical
 mise exec -- pnpm check
 ```
 
@@ -288,10 +385,10 @@ Automation can use explicit MicroVertical syntax instead of relying on the
 positional form:
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create --vertical=transportation
-pnpm dlx @bleedingdev/modern-js-create --vertical-name transportation
-pnpm dlx @bleedingdev/modern-js-create transportation --vertical --dry-run
-pnpm dlx @bleedingdev/modern-js-create transportation --vertical \
+pnpm dlx @bleedingdev/modern-js-ultramodern-create --vertical=transportation
+pnpm dlx @bleedingdev/modern-js-ultramodern-create --vertical-name transportation
+pnpm dlx @bleedingdev/modern-js-ultramodern-create transportation --vertical --dry-run
+pnpm dlx @bleedingdev/modern-js-ultramodern-create transportation --vertical \
   --codesmith-overlay ./generators/vertical-overlay
 ```
 
@@ -310,7 +407,7 @@ import {
   addUltramodernVertical,
   generateUltramodernWorkspace,
   planUltramodernVertical,
-} from '@modern-js/create/ultramodern-workspace';
+} from '@modern-js/ultramodern-create/ultramodern-workspace';
 
 const workspace = generateUltramodernWorkspace({
   targetDir: '/tmp/my-workspace',
@@ -342,7 +439,7 @@ returns the same shape plus `dryRun`, `selectedPort`, `moduleFederationRemote`,
 CodeSmith consumers can use the adapter subpath:
 
 ```ts
-import ultramodernCodeSmith from '@modern-js/create/ultramodern-workspace/codesmith';
+import ultramodernCodeSmith from '@modern-js/ultramodern-create/ultramodern-workspace/codesmith';
 
 await ultramodernCodeSmith({
   config: {
@@ -426,18 +523,6 @@ BleedingDev packages are published through GitHub Actions trusted publishing.
 The public workflow is tokenless; do not publish packages manually from a
 developer machine.
 
-## Baseline Switches (Opt-out)
-
-The generated `presetUltramodern(...)` starter enables strict platform contracts. Use these env switches to opt out per app or per environment:
-
-- `MODERN_BASELINE_ENABLE_MF_SSR` (default: `true`): Enables app-level MF SSR baseline contract (`server.ssr.mode: 'stream'` + `moduleFederationAppSSR`). Disable when the app does not use app-level MF SSR, or when you need plain SSR/CSR behavior first.
-- `MODERN_BASELINE_ENABLE_BFF_REQUEST_ID` (default: `true`): Enables default BFF producer identity contract (`bff.requestId`). Disable when the app does not need cross-project producer isolation.
-- `MODERN_BASELINE_ENABLE_TELEMETRY_EXPORTERS` (default: `true`): Enables telemetry exporters in baseline config. Disable when the environment has no telemetry backend yet.
-- `MODERN_BASELINE_APP_ID` (default: `basename(process.cwd())`): Overrides baseline `bff.requestId` identity. Set this when you need a fixed platform-wide producer ID convention.
-- `MODERN_TELEMETRY_OTLP_ENDPOINT` (default: `http://127.0.0.1:4318/v1/logs`): OTLP exporter endpoint. Override when you route telemetry through a different collector endpoint.
-- `MODERN_TELEMETRY_VICTORIA_ENDPOINT` (default: `http://127.0.0.1:8428/api/v1/import/prometheus`): VictoriaMetrics exporter endpoint. Override when you use a different VM ingress endpoint.
-- `MODERN_TELEMETRY_FAIL_LOUD_STARTUP` (default: `true`): Fails startup if configured exporters fail startup health checks. Disable in local/dev environments where temporary telemetry outage should not block boot.
-
 ## Related Docs
 
 - [BFF Runtime Frameworks](/guides/advanced-features/bff/frameworks)

package/docs/en/guides/troubleshooting/cli.mdx

@@ -35,5 +35,5 @@ pnpm run command --options
 ```
 
 :::tip
-Modern.js requires Node.js >= 20.19.5, and pnpm v6 does not support Node.js 20, so please use pnpm v7 or higher.
+UltraModern.js requires Node.js >= 26.7.0 and pnpm >= 11. Use the repository's pinned mise toolchain so the CLI and native TypeScript runtime stay aligned.
 :::

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. For more details, please refer to [Routing](/guides/basic-features/routes/routes#routing).
+UltraModern.js uses convention-based routing backed by TanStack 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:
 
@@ -12,6 +12,7 @@ In a web application, if there are multiple routes, we may need to authorize acc
 - Access to the `/protected` route requires authorization. If there is no authorization, it will automatically redirect to the `/login` route. After successful login, it returns to `/protected`.
 
 import Sandpack from '@site/src/components/Sandpack';
+import { ultramodernSandpackFiles } from '@modern-js/ultramodern-sandpack-profile';
 import srcRoutesPageText from '../../../../src/sandbox/csr-auth/src/routes/page-tsx.txt';
 import srcRoutesLayoutText from '../../../../src/sandbox/csr-auth/src/routes/layout-tsx.txt';
 import srcRoutesAuthText from '../../../../src/sandbox/csr-auth/src/routes/Auth-tsx.txt';
@@ -20,6 +21,7 @@ import srcRoutesProtectedPageText from '../../../../src/sandbox/csr-auth/src/rou
 import srcRoutesLoginPageText from '../../../../src/sandbox/csr-auth/src/routes/login/page-tsx.txt';
 
 <Sandpack template="web-app" files={{
+  ...ultramodernSandpackFiles,
   '/src/routes/page.tsx': srcRoutesPageText,
   '/src/routes/layout.tsx': srcRoutesLayoutText,
   '/src/routes/Auth.tsx': srcRoutesAuthText,

package/docs/zh/community/showcase.mdx

@@ -1,14 +1,13 @@
 ---
 sidebar_position: 0
+title: 生态系统
 ---
 
-# 案例展示
+# 生态系统
 
-欢迎来到 Modern.js 的案例展示页面！在这里，我们展示了一些基于 Modern.js 所实现的网站。
+UltraModern.js 建立在一组聚焦的框架与工具之上。这些项目提供了本 fork 使用的 Effect、TanStack Router、构建、文档与 Module Federation 基础能力。
 
-如果你使用 Modern.js 构建了一个网站，欢迎你与社区分享它。只需回复 [GitHub 讨论贴](https://github.com/web-infra-dev/modern.js/discussions/3554) 并附上你网站的链接即可。我们会定期收集内容，并将它们展示在当前页面。
-
-## 案例
+## 项目
 
 import { ShowcaseList } from '@site/src/components/ShowcaseList';
 

package/docs/zh/components/init-app.mdx

@@ -1,26 +1,26 @@
 UltraModern.js 提供 BleedingDev create 包来创建 SuperApp workspace，不需要全局安装，直接使用 `pnpm dlx` 按需运行即可。
 
 pnpm 支持的命令契约是 scoped package specifier：
-`pnpm dlx @bleedingdev/modern-js-create <target>`。不要简写成
-`pnpm dlx modern-js-create`；npm 上没有这个未加 scope 的包。
+`pnpm dlx @bleedingdev/modern-js-ultramodern-create <target>`。不要简写成
+`pnpm dlx modern-js-ultramodern-create`；npm 上没有这个未加 scope 的包。
 
 你可以在当前已有的空目录中初始化项目：
 
 ```bash
 mkdir myapp && cd myapp
-pnpm dlx @bleedingdev/modern-js-create .
+pnpm dlx @bleedingdev/modern-js-ultramodern-create .
 ```
 
 也可以直接用新目录创建项目：
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create myapp
+pnpm dlx @bleedingdev/modern-js-ultramodern-create myapp
 ```
 
 使用 workspace 协议依赖初始化（用于在本地 monorepo 中联调未发布的 Modern.js 包）：
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create myapp --workspace
+pnpm dlx @bleedingdev/modern-js-ultramodern-create myapp --workspace
 ```
 
 BleedingDev create 包会直接创建应用，不再提供问答界面：
@@ -70,14 +70,14 @@ BleedingDev create 包会直接创建应用，不再提供问答界面：
 默认 workspace 从 shell 起步，并安装已发布的 BleedingDev 包别名：
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create my-super-app
+pnpm dlx @bleedingdev/modern-js-ultramodern-create my-super-app
 ```
 
 在已生成的 SuperApp workspace 根目录中，可以就地添加业务
 MicroVertical：
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create transportation --vertical
+pnpm dlx @bleedingdev/modern-js-ultramodern-create transportation --vertical
 ```
 
 `--vertical` 会修改当前 workspace：新增 vertical 包，并写入 topology、

package/docs/zh/components/init-rspack-app.mdx

@@ -1,5 +1,3 @@
 ```bash
-$ pnpm dlx @bleedingdev/modern-js-create myapp
-? 请选择开发语言：TS
-? 请选择包管理工具：pnpm
+$ pnpm dlx @bleedingdev/modern-js-ultramodern-create myapp
 ```

package/docs/zh/components/prerequisites.mdx

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

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

@@ -53,7 +53,7 @@ import EnableBFFCaution from "@site-docs/components/enable-bff-caution";
 `/effect-client` 之前，请安装精确版本的依赖组：
 
 ```bash
-pnpm add effect@4.0.0-beta.107 @effect/opentelemetry@4.0.0-beta.107
+pnpm add effect@4.0.0-rc.112 @effect/opentelemetry@4.0.0-rc.112
 ```
 
 采用精确版本是因为 UltraModern 以锁步依赖组的方式发布 Effect。只使用
@@ -214,16 +214,16 @@ Effect 版本组。当前 UltraModern 版本组使用：
 
 ```yaml
 trustPolicyExclude:
-  - 'effect@4.0.0-beta.107'
-  - '@effect/opentelemetry@4.0.0-beta.107'
+  - 'effect@4.0.0-rc.112'
+  - '@effect/opentelemetry@4.0.0-rc.112'
 
 overrides:
-  '@effect/opentelemetry': 4.0.0-beta.107
-  '@effect/vitest': 4.0.0-beta.107
-  effect: 4.0.0-beta.107
+  '@effect/opentelemetry': 4.0.0-rc.112
+  '@effect/vitest': 4.0.0-rc.112
+  effect: 4.0.0-rc.112
 ```
 
-不要在应用包里添加不同版本的直接 `effect` 依赖。Effect beta 不一致时，Layer 或 HTTP
+不要在应用包里添加不同版本的直接 `effect` 依赖。Effect 预发布版本不一致时，Layer 或 HTTP
 middleware 构建可能因为运行时 service 来自不同包实例而失败。严格的 24 小时发布年龄
 门禁适用于实际安装的包；当前版本组没有 Effect 年龄豁免，且仅用于 override 的
 `@effect/vitest` 不是已安装的审批目标。

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

@@ -258,11 +258,11 @@ Vercel 是一个面向现代 Web 应用的部署平台，它提供了丰富的
 
 <img src="https://sf16-sg.tiktokcdn.com/obj/eden-sg/lmeh7nuptpfnuhd/vercel-root-directory.png" />
 
-将 Node.js 运行时设置为 `20.x`：
+将 Node.js 运行时设置为 `26.7.0` 或更高版本：
 
 ```json title="package.json"
 "engines": {
-  "node": "20.x"
+  "node": ">=26.7.0"
 },
 ```
 

package/docs/zh/guides/get-started/quick-start.mdx

@@ -25,7 +25,7 @@ import DebugApp from '@site-docs/components/debug-app';
 
 ## 使用配置
 
-通过 `@bleedingdev/modern-js-create` 创建的 UltraModern.js 项目中，会默认生成 `modern.config.ts` 文件。
+通过 `@bleedingdev/modern-js-ultramodern-create` 创建的 UltraModern.js 项目中，会默认生成 `modern.config.ts` 文件。
 
 你可以通过该配置文件修改配置，覆盖 Modern.js 的默认行为。例如添加如下配置，开启 SSR：
 

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

@@ -24,7 +24,7 @@ Modern.js 提供两套一方路由方案：
 创建 UltraModern 项目时，默认会包含 TanStack Router：
 
 ```bash
-pnpm dlx @bleedingdev/modern-js-create myapp
+pnpm dlx @bleedingdev/modern-js-ultramodern-create myapp
 ```
 
 Modern.js 支持约定式路由、自控式路由或其他路由方案，请参考 [页面入口](/guides/concept/entries) 进行选择。