@bleedingdev/modern-js-main-doc 3.2.0-ultramodern.9 → 3.2.0-ultramodern.91

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

@@ -15,12 +15,12 @@ Currently, Modern.js only supports running in a Node.js environment. Support for
 
 ## Build Deployment Products
 
-Running the `modern deploy` command will automatically produce deployment products. This process includes optimizing Bundler build products and their dependencies, detecting the current deployment platform, and automatically generating deployment products that can run on that platform.
+Running the `ultramodern deploy` command will automatically produce deployment products. This process includes optimizing Bundler build products and their dependencies, detecting the current deployment platform, and automatically generating deployment products that can run on that platform.
 
-If you want to generate and test the output locally for a specific deployment platform, you can specify the platform by setting the environment variable: `modern deploy`:
+If you want to generate and test the output locally for a specific deployment platform, you can specify the platform by setting the environment variable: `ultramodern deploy`:
 
 ```bash
-MODERNJS_DEPLOY=netlify npx modern deploy
+MODERNJS_DEPLOY=netlify npx ultramodern deploy
 ```
 
 :::info
@@ -36,10 +36,10 @@ By default, Modern.js outputs builds that can be run in a Node.js environment wh
 Use the following command to build the project:
 
 ```bash
-npx modern deploy
+npx ultramodern deploy
 ```
 
-When running the `modern deploy` command, Modern.js will generate runnable products and output the following content in terminal:
+When running the `ultramodern deploy` command, UltraModern.js will generate runnable products and output the following content in terminal:
 
 ```bash
 Static directory: `.output/static`
@@ -67,7 +67,7 @@ Assume that the name in the `package.json` of the current project is `app`. Taki
 {
   "scripts": {
     "build:packages": "pnpm --filter 'app^...' run build",
-    "deploy": "pnpm run build:packages && modern deploy"
+    "deploy": "pnpm run build:packages && ultramodern deploy"
   }
 }
 ```
@@ -78,7 +78,7 @@ If you use Rush as your Monorepo management tool, you can add the following comm
 {
   "scripts": {
     "build:packages": "rush rebuild --to-except app",
-    "deploy": "rushx build:packages && modern deploy"
+    "deploy": "rushx build:packages && ultramodern deploy"
   }
 }
 ```
@@ -108,7 +108,7 @@ Add the following content to `netlify.toml`:
 ```toml
 [build]
   publish = "dist"
-  command = "modern deploy"
+  command = "ultramodern deploy"
 ```
 
 :::info
@@ -125,7 +125,7 @@ Full-stack projects refer to projects that use Custom Web Server, SSR or BFF. Th
 ```toml title="netlify.toml"
 [build]
   publish = "dist"
-  command = "modern deploy"
+  command = "ultramodern deploy"
 
 [functions]
   directory = ".netlify/functions"
@@ -173,7 +173,7 @@ Add the following script in `packages/app/package.json`, before executing the de
 {
   "scripts": {
     "build:packages": "pnpm --filter 'app^...' run build",
-    "deploy": "pnpm run build:packages && modern deploy"
+    "deploy": "pnpm run build:packages && ultramodern deploy"
   }
 }
 ```
@@ -213,7 +213,7 @@ Add the following content to `vercel.json`:
 
 ```json title="vercel.json"
 {
-  "buildCommand": "modern deploy",
+  "buildCommand": "ultramodern deploy",
   "outputDirectory": ".vercel/output"
 }
 ```
@@ -281,7 +281,7 @@ Add the following script to `packages/app/package.json` to run `build` command o
 {
   "scripts": {
     "build:packages": "pnpm --filter 'app^...' run build",
-    "deploy": "pnpm run build:packages && modern deploy"
+    "deploy": "pnpm run build:packages && ultramodern deploy"
   }
 }
 ```
@@ -326,7 +326,7 @@ For branch deployment, follow these steps:
 ```
 "scripts": {
   //...
-  "deploy:gh-pages": "MODERNJS_DEPLOY=ghPages modern deploy && gh-pages -d .output"
+  "deploy:gh-pages": "MODERNJS_DEPLOY=ghPages ultramodern deploy && gh-pages -d .output"
 }
 ```
 
@@ -334,7 +334,7 @@ For branch deployment, follow these steps:
 
 :::info
 
-1. Running `MODERNJS_DEPLOY=ghPages modern deploy` will build the production output for GitHub in the .output directory.
+1. Running `MODERNJS_DEPLOY=ghPages ultramodern deploy` will build the production output for GitHub in the .output directory.
 2. You can refer to the [project](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/modern-js-deploy-csr)
    :::
 

package/docs/en/guides/basic-features/env-vars.mdx

@@ -16,8 +16,8 @@ The current path prefix of the asset, which is a read-only environment variable.
 
 The current execution environment and is a **read-only** environment variable whose have different values under different execution commands:
 
-- `production`: Default value when running `modern build` or `modern serve`.
-- `development`: Default value when running `modern dev`, also the default value in other cases.
+- `production`: Default value when running `ultramodern build` or `ultramodern serve`.
+- `development`: Default value when running `ultramodern dev`, also the default value in other cases.
 
 ### MODERN_ENV
 

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

@@ -271,7 +271,7 @@ Config routes can be used together with convention routes. You can merge routes
 
 :::info
 
-Current route structure can be viewed through the [`modern routes`](#debugging-routes) command
+Current route structure can be viewed through the [`ultramodern routes`](#debugging-routes) command
 
 :::
 
@@ -319,7 +319,7 @@ Since the final structure after route merging may not be intuitive, Modern.js pr
 
 ```bash
 # Generate route structure analysis report
-npx modern routes
+npx ultramodern routes
 ```
 
 This command will generate the final route structure in the `dist/routes-inspect.json` file, helping you understand the complete route information after merging.

package/docs/en/guides/basic-features/testing/_meta.json

@@ -1 +1 @@
-["playwright", "rstest", "vitest", "jest", "cypress"]
+["rstest", "playwright"]

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

@@ -26,10 +26,10 @@ Static asset files can be directly hosted by Modern.js' server, but it is highly
 
 Modern.js supports running built artifacts in any Node.js environment. Typically, the CI environment has already installed all application dependencies.
 
-You can run the [`modern build`](/apis/app/commands#modern-build) command to build the application and the [`modern serve`](/apis/app/commands#modern-serve) command to run the Web server, starting the Modern.js application.
+You can run the [`ultramodern build`](/apis/app/commands#ultramodern-build) command to build the application and the [`ultramodern serve`](/apis/app/commands#ultramodern-serve) command to run the Web server, starting the UltraModern.js application.
 
 ## Running in Production Environments
 
 When deploying to production, the artifact size should be as small as possible. The aforementioned method for running in CI environments keeps all artifacts from the original project. Therefore, it is not recommended to run the application using the above commands in a production environment.
 
-Modern.js offers a standalone deployment solution. When running the [`modern deploy`](/apis/app/commands#modern-deploy) command, the artifacts will include an entry file for running the Web server.
+UltraModern.js offers a standalone deployment solution. When running the [`ultramodern deploy`](/apis/app/commands#ultramodern-deploy) command, the artifacts will include an entry file for running the Web server.

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

@@ -27,7 +27,7 @@ import DebugApp from '@site-docs-en/components/debug-app';
 
 ## Configuration
 
-In a Modern.js project created using `@modern-js/create`, a `modern.config.ts` file is generated by default.
+In an UltraModern.js project created using `@bleedingdev/modern-js-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:
 
@@ -48,7 +48,7 @@ After running `pnpm run dev` again, you can find that the project has completed
 
 In a newly created project, the `@modern-js/app-tools` npm package is installed by default. It is the core package of the Modern.js framework and provides the following capabilities:
 
-- It offers commonly used CLI commands such as `modern dev`, `modern build`, and more.
+- It offers commonly used CLI commands such as `ultramodern dev`, `ultramodern build`, and more.
 - It integrates Rsbuild, providing build capabilities.
 - It integrates Modern.js Server, providing capabilities for development and production servers.
 

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

@@ -18,13 +18,13 @@ Rsbuild supports building Vue applications. If you need to use Vue, you can refe
 
 Modern.js provides two first-party routing frameworks:
 
-- [React Router v7](https://reactrouter.com/en/main) (default), via `@modern-js/runtime/router`.
-- [TanStack Router](https://tanstack.com/router), via `@modern-js/plugin-tanstack/runtime`.
+- [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`.
 
-When creating a project, you can choose TanStack Router by using:
+When creating an UltraModern project, TanStack Router is included by default:
 
 ```bash
-npx @modern-js/create@latest myapp --router tanstack
+pnpm dlx @bleedingdev/modern-js-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.
@@ -84,6 +84,12 @@ Modern.js can be used with any React UI component library from the community, su
 
 Modern.js supports the use of [Storybook](https://storybook.js.org/) for developing UI components. This feature is optional. Please refer to ["Using Storybook"](/guides/basic-features/debug/using-storybook) to enable it.
 
+## Testing Framework
+
+Modern.js recommends [Rstest](https://rstest.rs/) for unit tests and component tests. Rstest is built on Rspack for fast startup and execution, and it can reuse your Modern.js app configuration through [`@modern-js/adapter-rstest`](/guides/basic-features/testing/rstest).
+
+For end-to-end (E2E) tests, you can use [Playwright](/guides/basic-features/testing/playwright).
+
 ## Node.js Framework
 
 import TechStackNodeFramework from '@site-docs-en/components/tech-stack-node-framework';

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

@@ -36,7 +36,7 @@ UltraModern.js additions are designed as the default product surface for new Sup
 | BFF runtime choices | Hono runtime path only in Modern.js 3.0 baseline (no built-in Effect runtime path) | Sets Effect as default runtime, enforces strict runtime split (`effect` -> `api/effect`, `hono` -> `api/lambda`), and adds Effect-Schema-first contracts plus MF failure-injection reliability coverage |
 | Telemetry standardization | Observability wiring is often app-specific | Adds framework-level telemetry pipeline with OTLP/VictoriaMetrics exporters, redaction, batching, and backpressure controls |
 | App-level MF SSR handshake | No dedicated super-app app-level stability contract focus | Adds `server.ssr.moduleFederationAppSSR` plus integration-tested env/config handshake |
-| MF remote reliability | Retry/fallback patterns are often implemented per app | Adds deterministic timeout/network/contract-error reliability matrix and distributed OTEL continuity tests |
+| MF vertical loading reliability | Retry/fallback patterns are often implemented per app | Adds deterministic timeout/network/contract-error reliability matrix and distributed OTEL continuity tests |
 | Module onboarding governance | No module-certification evidence profile in baseline | Adds module SDK contracts, boundary anti-pattern guards, and release/module certification gate workflows |
 | Router runtime | Default runtime path centers on React Router | Adds first-class TanStack Router runtime/CLI path (React Router remains supported) |
 | Scaffolding templates | Default create templates center on React Router starter path | Adds TanStack-ready and Tailwind-ready create templates |
@@ -60,21 +60,98 @@ For teams already on Modern.js 3.0, the adoption path remains compatibility-awar
 
 This page is not a migration guide or codemod plan. Migration guidance for existing applications is intentionally deferred from the current Micro Verticals framework scope.
 
-## Micro Vertical Delivery Path
-
-`presetUltramodern(...)` is also the single public entrypoint for Micro Verticals. The intended adoption sequence is:
-
-1. start with one app and keep route/data ownership inside the shell,
-2. extract stable route subtrees into MF remotes once fallback and compatibility behavior are explicit,
-3. extract shared workflows into strict Effect services when request, identity, locale, and trace context must survive deployment boundaries,
-4. keep Hono only as an explicit compatibility lane for existing Modern.js-style BFF handlers.
-
-In this repo, the reference examples are:
-
-- `routes-tanstack-mf` for shell + remote composition and MF SSR contracts,
-- `bff-corss-project` for cross-project producer/consumer wiring,
-- `bff-runtime-parity` for generated-client build/serve parity,
-- `bff-hono` for the compatibility lane.
+## Human Workflow
+
+The public BleedingDev create package starts small. The default command creates
+one production-ready UltraModern app with `presetUltramodern(...)`, SSR,
+TanStack Router, Tailwind CSS v4, i18n, Effect BFF, generated quality gates, and
+Cloudflare deploy basics:
+
+```bash
+pnpm dlx @bleedingdev/modern-js-create myapp
+cd myapp
+mise install
+mise exec -- pnpm install
+mise exec -- pnpm ultramodern:check
+```
+
+Create a SuperApp workspace only when independent ownership is useful:
+
+```bash
+pnpm dlx @bleedingdev/modern-js-create my-super-app --ultramodern-workspace
+cd my-super-app
+mise install
+mise exec -- pnpm install
+mise exec -- pnpm ultramodern:check
+```
+
+The workspace starts from a shell and generated platform contracts. It does not
+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
+mise exec -- pnpm ultramodern:check
+```
+
+The `--vertical` command mutates the current workspace. It creates the vertical
+package and updates topology metadata, ownership records, shell Module
+Federation wiring, local development overlays, package dependencies, generated
+contracts, ports, route-owned i18n, CSS isolation, and the vertical-owned Effect
+BFF/client surface.
+
+### Runtime Contracts
+
+Generated apps and verticals keep SSR on the normal Modern.js path. SuperApp
+workspaces add `server.ssr.moduleFederationAppSSR` when Module Federation SSR is
+needed, but the flag remains an explicit contract rather than a requirement for
+every app.
+
+Each app emits `src/routes/ultramodern-route-metadata` with
+`ultramodernLocalisedUrls`. The i18n plugin reads that map in
+`localeDetection.localisedUrls` and serves dynamic backend JSON from
+`/locales/{{lng}}/{{ns}}.json`. The route owner changes localized paths and
+locale resource JSON together.
+
+The generated contract writes `.modernjs/ultramodern-generated-contract.json`
+with a `cssFederation` section:
+
+- `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.
+- 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, Effect 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.
+
+### Validation And Deploy
+
+Local gates:
+
+```bash
+mise exec -- pnpm ultramodern:check
+mise exec -- pnpm build
+mise exec -- pnpm cloudflare:build
+```
+
+Generated workspaces include `scripts/proof-cloudflare-version.mjs` for live
+Cloudflare and Zephyr proof:
+
+```bash
+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
+```
+
+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.
+
+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)
 

package/docs/en/guides/topic-detail/module-federation/application.mdx

@@ -103,7 +103,7 @@ export default RemoteApp;
 
 ## Start the Application
 
-Now, both the producer and consumer applications are set up. We can run `modern dev` locally to start both applications.
+Now, both the producer and consumer applications are set up. We can run `ultramodern dev` locally to start both applications.
 
 After startup, when the consumer application accesses the `/remote` route, it will enter the producer application. Accessing `http://localhost:8080/remote` will display a complete page of the producer's remote module in the browser.
 

package/docs/en/guides/topic-detail/module-federation/deploy.mdx

@@ -88,10 +88,10 @@ export default createModuleFederationConfig({
 
 ## Local Deployment Verification
 
-Modern.js provides the `modern deploy` command, which can easily generate products that can run in a Node.js environment.
+Modern.js provides the `ultramodern deploy` command, which can easily generate products that can run in a Node.js environment.
 
 ```bash
-modern deploy
+ultramodern deploy
 ```
 
 After executing the command, you can see the following output in the console:

package/docs/en/guides/topic-detail/module-federation/usage.mdx

@@ -154,7 +154,7 @@ The second part, `remoteExpose`, is the `key` configured in the `exposes` field
 
 ## Start the Applications
 
-Now, both the producer and consumer applications are set up. You can run `modern dev` locally to start both applications.
+Now, both the producer and consumer applications are set up. You can run `ultramodern dev` locally to start both applications.
 
 Once started, the imports of the producer's modules in the consumer will no longer throw errors, and the types will be downloaded to the consumer application.
 
@@ -164,7 +164,7 @@ After modifying the producer's code, the consumer will automatically fetch the p
 
 Access `http://localhost:8080/remote`, and you will see that the page includes the `Button` component from the producer's remote module.
 
-We can also execute `modern serve` locally to simulate the production environment.
+We can also execute `ultramodern serve` locally to simulate the production environment.
 
 Because the Module Federation plugin will automatically read Modern.js's `output.assetPrefix` configuration as the access address for remote modules, and this value defaults to `/` after building in the production environment.
 
@@ -180,7 +180,7 @@ export default defineConfig({
     port: 3051,
   },
   output: {
-    // Now this configuration is only used in the local when you run modern serve command.
+    // Now this configuration is only used in the local when you run ultramodern serve command.
     // If you want to deploy the application to the platform, use your own domain name.
     // Module federation will automatically write it to mf-manifest.json, which influences consumer to fetch remoteEntry.js.
     assetPrefix: 'http://127.0.0.1:3051',
@@ -189,10 +189,10 @@ export default defineConfig({
 });
 ```
 
-Now, in the producer, run `modern build && MODERN_MF_AUTO_CORS=true  modern serve`, and in the consumer, run `modern build && modern serve` to simulate the production environment locally and access the remote modules.
+Now, in the producer, run `ultramodern build && MODERN_MF_AUTO_CORS=true  ultramodern serve`, and in the consumer, run `ultramodern build && ultramodern serve` to simulate the production environment locally and access the remote modules.
 
 :::tip
-When using the `modern serve` command, you need to set the `MODERN_MF_AUTO_CORS=true` environment variable when starting the producer project to automatically handle CORS issues and ensure that consumers can properly access the producer's remote module resources.
+When using the `ultramodern serve` command, you need to set the `MODERN_MF_AUTO_CORS=true` environment variable when starting the producer project to automatically handle CORS issues and ensure that consumers can properly access the producer's remote module resources.
 :::
 
 You can refer to this example: [Modern.js & Module Federation Basic Example](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/module-federation/base).

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

@@ -23,7 +23,7 @@ Modern.js is internally based on [Rsbuild](https://v2.rsbuild.rs/) and encapsula
 Modern.js provides [inspect command](https://modernjs.dev/en/apis/app/commands.html) to view the final Modern.js configuration and Rspack configuration generated by the project.
 
 ```bash
-➜ npx modern inspect
+➜ npx ultramodern inspect
 
 Inspect config succeed, open following files to view the content:
 

package/docs/en/guides/upgrade/other.mdx

@@ -87,14 +87,14 @@ Modern.js 3.0 uses React Router v7 as the default routing library. React Router
 
 If you need to use React Router v5 or React Router v6, you need to use **self-controlled routing** mode. Self-controlled routing allows you to fully control routing configuration without being limited by Modern.js convention-based routing.
 
-## Using @modern-js/create to Create Monorepo and Modern.js Module
+## Using @bleedingdev/modern-js-create to Create Monorepo and Modern.js Module
 
-Modern.js 3.0 no longer supports creating Monorepo projects and Modern.js Module projects through `@modern-js/create`.
+Modern.js 3.0 no longer supports creating Monorepo projects and Modern.js Module projects through `@bleedingdev/modern-js-create`.
 
 **Changes**:
 
-- In [v2.53.0](https://github.com/web-infra-dev/modern.js/releases/tag/v2.53.0), the functionality to create Monorepo projects using `@modern-js/create` was removed
-- In [v2.61.0](https://github.com/web-infra-dev/modern.js/releases/tag/v2.61.0), the functionality to create Modern.js Module projects using `@modern-js/create` and `modern new` commands was removed
+- In [v2.53.0](https://github.com/web-infra-dev/modern.js/releases/tag/v2.53.0), the functionality to create Monorepo projects using `@bleedingdev/modern-js-create` was removed
+- In [v2.61.0](https://github.com/web-infra-dev/modern.js/releases/tag/v2.61.0), the functionality to create Modern.js Module projects using `@bleedingdev/modern-js-create` and `ultramodern new` commands was removed
 
 **Handling**:
 
@@ -103,12 +103,12 @@ Modern.js 3.0 no longer supports creating Monorepo projects and Modern.js Module
 
 ## new and upgrade Commands Removed
 
-Modern.js 3.0 removed the `modern new` and `modern upgrade` commands, and you need to perform operations manually according to the documentation.
+Modern.js 3.0 removed the `ultramodern new` and `ultramodern upgrade` commands, and you need to perform operations manually according to the documentation.
 
 **Changes**:
 
-- The `modern new` command is no longer supported in Modern.js 3.0, and you cannot add entries or enable features through commands
-- The `modern upgrade` command is no longer supported in Modern.js 3.0, and you cannot automatically upgrade dependencies through commands
+- The `ultramodern new` command is no longer supported in Modern.js 3.0, and you cannot add entries or enable features through commands
+- The `ultramodern upgrade` command is no longer supported in Modern.js 3.0, and you cannot automatically upgrade dependencies through commands
 
 **Handling**:
 

package/docs/zh/apis/app/commands.mdx

@@ -4,16 +4,16 @@ sidebar_position: 1
 
 # 命令
 
-Modern.js 内置了一些命令，可以帮助你快速启动开发服务器、构建生产环境代码等。
+UltraModern.js 内置了一些命令，可以帮助你快速启动开发服务器、构建生产环境代码等。
 
-通过本章节，你可以了解到 Modern.js 内置的命令有哪些，以及如何使用这些命令。
+通过本章节，你可以了解到 UltraModern.js 内置的命令有哪些，以及如何使用这些命令。
 
-## modern dev
+## ultramodern dev
 
-`modern dev` 命令用于启动一个本地开发服务器，对源代码进行开发环境编译。
+`ultramodern dev` 命令用于启动一个本地开发服务器，对源代码进行开发环境编译。
 
 ```bash
-Usage: modern dev [options]
+Usage: ultramodern dev [options]
 
 Options:
   -e --entry <entry>    指定入口，只编译特定的页面
@@ -23,10 +23,10 @@ Options:
   --api-only            仅启动 API 接口服务
 ```
 
-运行 `modern dev` 后，Modern.js 会监听源文件变化并进行模块热更新。
+运行 `ultramodern dev` 后，UltraModern.js 会监听源文件变化并进行模块热更新。
 
 ```bash
-$ modern dev
+$ ultramodern dev
 
 info    Starting dev server...
 
@@ -38,10 +38,10 @@ info    Starting dev server...
 
 在多页面（MPA）项目中，可以添加 `--entry` 参数来指定编译其中的一个或多个页面。这样可以只编译项目中的部分代码，从而提升 dev 启动速度。
 
-比如执行 `modern dev --entry`，在命令行界面中会展示入口选择框：
+比如执行 `ultramodern dev --entry`，在命令行界面中会展示入口选择框：
 
 ```bash
-$ modern dev --entry
+$ ultramodern dev --entry
 
 ? 请选择需要构建的入口
 ❯ ◯ foo
@@ -57,22 +57,22 @@ $ modern dev --entry
 
 ```bash
 # 编译 foo 页面
-modern dev --entry foo
+ultramodern dev --entry foo
 
 # 编译 foo 和 bar 页面
-modern dev --entry foo,bar
+ultramodern dev --entry foo,bar
 ```
 
-## modern start
+## ultramodern start
 
-`modern start` 是 `modern dev` 命令的别名，两者的功能和用法完全一致。
+`ultramodern start` 是 `ultramodern dev` 命令的别名，两者的功能和用法完全一致。
 
-## modern build
+## ultramodern build
 
-`modern build` 命令默认会在 `dist/` 目录下构建出可用于生产环境的产物。你可以通过修改配置 [`output.distPath`](/configure/app/output/dist-path) 指定产物的输出目录。
+`ultramodern build` 命令默认会在 `dist/` 目录下构建出可用于生产环境的产物。你可以通过修改配置 [`output.distPath`](/configure/app/output/dist-path) 指定产物的输出目录。
 
 ```bash
-Usage: modern build [options]
+Usage: ultramodern build [options]
 
 Options:
   -c --config <config>  指定配置文件路径，可以为相对路径或绝对路径
@@ -80,14 +80,14 @@ Options:
   -w --watch  开启 watch 模式, 监听文件变更并重新构建
 ```
 
-## modern new
+## ultramodern new
 
-`modern new` 命令用于在已有项目中添加项目元素。
+`ultramodern new` 命令用于在已有项目中添加项目元素。
 
 比如添加应用入口、启用一些可选功能如 BFF、微前端开发模式等。
 
 ```bash
-Usage: modern new [options]
+Usage: ultramodern new [options]
 
 Options:
   --config-file <configFile>  指定配置文件路径，可以为相对路径或绝对路径
@@ -104,7 +104,7 @@ Options:
 在 Modern.js 工程中，执行 `new` 命令添加入口的步骤如下：
 
 ```bash
-$ npx modern new
+$ npx ultramodern new
 ? 请选择你想要的操作 创建工程元素
 ? 请选择创建元素类型 新建「应用入口」
 ? 请填写入口名称 entry
@@ -115,7 +115,7 @@ $ npx modern new
 在 Modern.js 工程中，执行 `new` 命令启用可选能力的步骤如下：
 
 ```bash
-$ npx modern new
+$ npx ultramodern new
 ? 请选择你想要的操作 启用可选功能
 ? 请选择功能名称 (Use arrow keys)
 ❯ 启用「BFF」功能
@@ -133,12 +133,12 @@ import ServeCommand from '@site-docs/components/serve-command';
 
 <ServeCommand />
 
-## modern upgrade
+## ultramodern upgrade
 
-在项目根目录下执行命令 `npx modern upgrade`，会默认将当前执行命令项目的 `package.json` 中的 Modern.js 相关依赖更新至最新版本。
+在项目根目录下执行命令 `npx ultramodern upgrade`，会默认将当前执行命令项目的 `package.json` 中的 UltraModern.js 相关依赖更新至最新版本。
 
 ```bash
-Usage: modern upgrade [options]
+Usage: ultramodern upgrade [options]
 
 Options:
   -c --config <config>  指定配置文件路径，可以为相对路径或绝对路径
@@ -148,12 +148,12 @@ Options:
   -h, --help             display help for command
 ```
 
-## modern inspect
+## ultramodern inspect
 
-`modern inspect` 命令用于查看项目的 Modern.js 配置、[Rsbuild 配置](https://v2.rsbuild.rs/zh/config/index) 以及 Rspack 配置。
+`ultramodern inspect` 命令用于查看项目的 UltraModern.js 配置、[Rsbuild 配置](https://v2.rsbuild.rs/zh/config/index) 以及 Rspack 配置。
 
 ```bash
-Usage: modern inspect [options]
+Usage: ultramodern inspect [options]
 
 Options:
   --env <env>           查看指定环境下的配置 (default: "development")
@@ -163,14 +163,14 @@ Options:
   -h, --help            显示命令帮助
 ```
 
-在项目根目录下执行命令 `npx modern inspect` 后，会在项目的 `dist` 目录生成以下文件：
+在项目根目录下执行命令 `npx ultramodern inspect` 后，会在项目的 `dist` 目录生成以下文件：
 
 - `modern.js.config.mjs`: 表示当前使用的 Modern.js 配置。
 - `rsbuild.config.mjs`: 表示在构建时使用的 Rsbuild 配置。
 - `rspack.config.web.mjs`: 表示在构建时使用的 Rspack 配置。
 
 ```bash
-➜ npx modern inspect
+➜ npx ultramodern inspect
 
 Inspect config succeed, open following files to view the content:
 
@@ -184,7 +184,7 @@ Inspect config succeed, open following files to view the content:
 默认情况下，inspect 命令会输出开发环境的配置，你可以添加 `--env production` 选项来输出生产环境的配置：
 
 ```bash
-modern inspect --env production
+ultramodern inspect --env production
 ```
 
 ### 完整内容
@@ -192,7 +192,7 @@ modern inspect --env production
 默认情况下，inspect 命令会省略配置对象中的函数内容，你可以添加 `--verbose` 选项来输出函数的完整内容：
 
 ```bash
-modern inspect --verbose
+ultramodern inspect --verbose
 ```
 
 ### SSR 构建配置
@@ -200,7 +200,7 @@ modern inspect --verbose
 如果项目开启了 SSR 能力，则在 `dist` 目录会另外生成一份 `rspack.config.node.mjs` 文件，对应 SSR 构建时的 Rspack 配置。
 
 ```bash
-➜ npx modern inspect
+➜ npx ultramodern inspect
 
 Inspect config succeed, open following files to view the content:
 

package/docs/zh/community/blog/2022-0708-updates.md

@@ -17,7 +17,7 @@ Modern.js 7 ~ 8 月的最新版本为 v1.17.0，本双月的主要更新有：
 
 Modern.js 框架和相关插件完成对 React 18 的适配。现在，只需要将项目中的 `react`、`react-dom` 两个包的版本，升级到最新的 React 18 大版本，就可以使用 React 18 的新功能。
 
-注意，使用 `@modern-js/create` 命令默认创建的项目，安装的依赖 `react`、`react-dom` 的版本仍然为 17，如果希望使用 React 18，请手动升级这两个包的版本。
+注意，使用 `@bleedingdev/modern-js-create` 命令默认创建的项目，安装的依赖 `react`、`react-dom` 的版本仍然为 17，如果希望使用 React 18，请手动升级这两个包的版本。
 
 另外，SSR 流式渲染功能，目前尚在开发中，暂不支持。