@bleedingdev/modern-js-app-tools 3.5.0-ultramodern.99 → 3.8.1-ultramodern.1

package/docs/guides/topic-detail/module-federation/{ssr.mdx → ssr.md}

@@ -4,7 +4,7 @@
 
 ## Enable SSR
 
-Using the application created in [Using Module Federation](/guides/topic-detail/module-federation/usage) as an example, you only need to add the `server.ssr` configuration to both the producer and the consumer:
+Using the application created in [Using Module Federation](/guides/topic-detail/module-federation/usage.md) as an example, you only need to add the `server.ssr` configuration to both the producer and the consumer:
 
 ```ts title="modern.config.ts"
 import { appTools, defineConfig } from '@modern-js/app-tools';
@@ -74,14 +74,19 @@ Before enabling this for broad production traffic, verify the following scenario
 ## Example Rollout Scenarios
 
 1. Baseline enablement (host + remote):
-  - Configure both sides with `server.ssr.mode: 'stream'` and `moduleFederationAppSSR: true`.
-  - Verify SSR HTML contains either remote shell markers or an explicit typed fallback contract that names the client-hydrated remotes.
+
+- Configure both sides with `server.ssr.mode: 'stream'` and `moduleFederationAppSSR: true`.
+- Verify SSR HTML contains either remote shell markers or an explicit typed fallback contract that names the client-hydrated remotes.
+
 2. Remote unavailable fallback:
-  - Keep host flag enabled, stop one remote service, request a remote route.
-  - Verify response is still `200`, fallback boundary renders, and server does not crash.
+
+- Keep host flag enabled, stop one remote service, request a remote route.
+- Verify response is still `200`, fallback boundary renders, and server does not crash.
+
 3. Timeout and contract-error drill:
-  - Inject a delayed remote/data response and a malformed payload in CI.
-  - Verify deterministic fallback UI and matching telemetry reason codes.
+
+- Inject a delayed remote/data response and a malformed payload in CI.
+- Verify deterministic fallback UI and matching telemetry reason codes.
 
 ## Data Fetching
 

package/docs/guides/topic-detail/module-federation/{usage.mdx → usage.md}

@@ -2,15 +2,32 @@
 
 To use Module Federation in Modern.js, we recommend using the official plugin `@module-federation/modern-js-v3`.
 
-This section will introduce how to set up both producer and consumer applications using the official plugin. First, create two applications by following the [Modern.js Quick Start](/guides/get-started/quick-start).
+This section will introduce how to set up both producer and consumer applications using the official plugin. First, create two applications by following the [Modern.js Quick Start](/guides/get-started/quick-start.md).
 
 ## Install the Plugin
 
 After creating the applications, install the plugin for both projects:
 
-import { PackageManagerTabs } from '@theme';
 
-<PackageManagerTabs command="add @module-federation/modern-js-v3" />
+```sh [npm]
+npm add @module-federation/modern-js-v3
+```
+
+```sh [yarn]
+yarn add @module-federation/modern-js-v3
+```
+
+```sh [pnpm]
+pnpm add @module-federation/modern-js-v3
+```
+
+```sh [bun]
+bun add @module-federation/modern-js-v3
+```
+
+```sh [deno]
+deno add npm:@module-federation/modern-js-v3
+```
 
 ## Register the Plugin
 

package/docs/guides/troubleshooting/{builder.mdx → builder.md}

@@ -1,12 +1,8 @@
----
-sidebar_position: 3
----
-
 # Build FAQ
 
 If you encounter any build-related issues, you can refer to the current document for troubleshooting.
 
----
+***
 
 ### Rsbuild FAQ
 
@@ -16,7 +12,7 @@ Modern.js is internally based on [Rsbuild](https://v2.rsbuild.rs/) and encapsula
 - [Rsbuild - Exceptions FAQ](https://v2.rsbuild.rs/guide/faq/exceptions)
 - [Rsbuild - HMR FAQ](https://v2.rsbuild.rs/guide/faq/hmr)
 
----
+***
 
 ### How to view the final generated Rspack configuration?
 
@@ -31,7 +27,7 @@ Inspect config succeed, open following files to view the content:
   - Rspack Config (web): /root/my-project/dist/rspack.config.web.mjs
 ```
 
----
+***
 
 ### Failed import other modules in Monorepo?
 
@@ -41,24 +37,24 @@ Therefore, when you reference the source code of other sub-projects, you may enc
 
 There are several solutions to this problem:
 
-1. You can enable the source code build mode to compile other sub-projects within the monorepo. Please refer to [Source Code Build Mode](/guides/advanced-features/source-build.html) for more information.
-2. You can add the `source.include` configuration option to specify the directories or modules that need to be additionally compiled. Please refer to [Usage of source.include](/configure/app/source/include.html) for more information.
+1. You can enable the source code build mode to compile other sub-projects within the monorepo. Please refer to [Source Code Build Mode](/guides/advanced-features/source-build.md) for more information.
+2. You can add the `source.include` configuration option to specify the directories or modules that need to be additionally compiled. Please refer to [Usage of source.include](/configure/app/source/include.md) for more information.
 3. You can pre-build the sub-projects that need to be referenced, generate the corresponding build artifacts, and then reference the build artifacts in the current project instead of referencing the source code.
 
----
+***
 
 ### Find `exports is not defined` runtime error?
 
 If the compilation is succeed, but the `exports is not defined` error appears after opening the page, it is usually because a CommonJS module is compiled by Babel.
 
-Under normal circumstances, Modern.js will not use Babel to compile CommonJS modules. If the [source.include](/en/configure/app/source/include.html) configuration option is used in the project, some CommonJS modules may be added to the Babel compilation.
+Under normal circumstances, Modern.js will not use Babel to compile CommonJS modules. If the [source.include](/configure/app/source/include.md) configuration option is used in the project, some CommonJS modules may be added to the Babel compilation.
 
 There are two workarounds for this problem:
 
 1. Avoid adding CommonJS modules to Babel compilation.
 2. Set Babel's `sourceType` configuration to `unambiguous`.
 
----
+***
 
 ### Compile error "Error: ES Modules may not assign module.exports or exports.\*, Use ESM export syntax"?
 
@@ -70,7 +66,7 @@ Error: ES Modules may not assign module.exports or exports.*, Use ESM export syn
 
 For more information, please refer to issue: [babel#12731](https://github.com/babel/babel/issues/12731).
 
----
+***
 
 ### The compilation progress bar is stuck, but there is no Error log in the terminal?
 
@@ -83,7 +79,7 @@ If this problem occurs after you modify the Babel config, it is recommended to c
 1. You have configured a plugin or preset that does not exist, maybe the name is misspelled, or it is not installed correctly.
 2. Whether multiple babel-plugin-imports are configured, but the name of each babel-plugin-import is not declared in the third item of the array.
 
----
+***
 
 ### Compilation error after referencing a type from lodash
 

package/docs/guides/troubleshooting/{cli.mdx → cli.md}

@@ -1,7 +1,3 @@
----
-sidebar_position: 2
----
-
 # CLI FAQ
 
 ### Unable to pass command line arguments correctly when using pnpm?

package/docs/guides/troubleshooting/{dependencies.mdx → dependencies.md}

@@ -1,7 +1,3 @@
----
-sidebar_position: 1
----
-
 # Dependencies FAQ
 
 ### How to check the actual installed version of a dependency in the project?
@@ -34,7 +30,7 @@ devDependencies:
 └── @modern-js/plugin x.y.z
 ```
 
----
+***
 
 ### Getting "The engine "node" is incompatible" error during dependency installation?
 
@@ -65,7 +61,7 @@ nvm alias default 22
 
 For local development environments, it is recommended to use [fnm](https://github.com/Schniz/fnm), which has better performance than nvm and has similar usage.
 
----
+***
 
 ### Getting a ReactNode type error after upgrading dependencies?
 
@@ -88,9 +84,9 @@ The solution is to lock the `@types/react` and `@types/react-dom` in the project
 }
 ```
 
-For methods of locking dependency versions, please refer to [Lock nested dependency](/guides/get-started/upgrade.html#lock-nested-dependency).
+For methods of locking dependency versions, please refer to [Lock nested dependency](/guides/get-started/upgrade.md#lock-nested-dependency).
 
----
+***
 
 ### Getting peer dependencies warnings in the console after running `pnpm install`?
 
@@ -98,7 +94,7 @@ The reason for this warning is that the version range of peer dependencies decla
 
 In most cases, peer dependencies warnings will not affect the project operation and do not need to be processed separately. Please ignore the relevant warnings.
 
----
+***
 
 ### What is the minimum supported version of React for the Modern.js framework?
 
@@ -107,7 +103,7 @@ In most cases, peer dependencies warnings will not affect the project operation
 - **If you are using Modern.js runtime capabilities** (including SSR, Streaming SSR, data loading, routing, etc.), you must use React 18 or higher. React 16 and React 17 are no longer supported.
 - **If you are only using Modern.js build capabilities** (without runtime), React 16 or React 17 may theoretically work, but it is strongly recommended to upgrade to React 18 or higher for the best experience and full feature support.
 
----
+***
 
 ### Type error in Modern.js configuration file?
 
@@ -120,4 +116,4 @@ When you use the Modern.js framework, the above error occurs in the configuratio
 
 In the monorepo, the above error may also occur due to inconsistent versions of the Modern.js framework used by different sub-projects.
 
-For information on how to unify and upgrade dependency versions, please refer to the [Upgrading](/guides/get-started/upgrade) documentation.
+For information on how to unify and upgrade dependency versions, please refer to the [Upgrading](/guides/get-started/upgrade.md) documentation.

package/docs/guides/troubleshooting/{hmr.mdx → hmr.md}

@@ -1,7 +1,3 @@
----
-sidebar_position: 4
----
-
 # HMR FAQ
 
 ### How to troubleshooting HMR ineffective issues?
@@ -27,7 +23,7 @@ Open the browser console and check for the presence of the `[HMR] connected.` lo
 - If it is present, the WebSocket connection is working correctly. You can continue with the following steps.
 - If it is not present, open the Network panel in Chrome and check the status of the `ws://[host]:[port]/webpack-hmr` request. If the request is failed, this indicates that the HMR failed because the WebSocket connection was not successfully established.
 
-There can be various reasons why the WebSocket connection fails to establish, such as using a network proxy that prevents the WebSocket request from reaching the development server. You can check whether the WebSocket request address matches your development server address. If it does not match, you can configure the WebSocket request address using [tools.devServer.client](/configure/app/tools/dev-server.html#client).
+There can be various reasons why the WebSocket connection fails to establish, such as using a network proxy that prevents the WebSocket request from reaching the development server. You can check whether the WebSocket request address matches your development server address. If it does not match, you can configure the WebSocket request address using [tools.devServer.client](/configure/app/tools/dev-server.md#client).
 
 #### 2. Check the hot-update Requests
 
@@ -41,7 +37,7 @@ If the content of the request is incorrect, it is likely due to a network proxy.
 
 If the above two steps do not reveal any issues, it is possible that other factors are causing the HMR to fail. For example, it could be that the code does not meet React's requirements for HMR. You can refer to the following questions for further troubleshooting.
 
----
+***
 
 ### HMR not working when external React?
 
@@ -64,7 +60,7 @@ To solve this problem, you need to reference the development builds of React or
 
 If you are unsure about the type of React build you are using, you can refer to the [React documentation - Use the Production Build](https://legacy.reactjs.org/docs/optimizing-performance.html#use-the-production-build).
 
----
+***
 
 ### HMR not working when setting filename hash in development mode?
 
@@ -99,7 +95,7 @@ export default {
 };
 ```
 
----
+***
 
 ### HMR not working when updating React components?
 
@@ -133,7 +129,7 @@ const MyComponent = () => <div>Hello World</div>;
 export default MyComponent;
 ```
 
----
+***
 
 ### HMR not working when use https?
 

package/docs/guides/upgrade/{config.mdx → config.md}

@@ -334,7 +334,7 @@ export default {
 
 ### tools.rsdoctor
 
-**Change**: This configuration has been deprecated. In v3, use [`performance.rsdoctor`](/configure/app/performance/rsdoctor) to opt in to Rsdoctor diagnostics.
+**Change**: This configuration has been deprecated. In v3, use [`performance.rsdoctor`](/configure/app/performance/rsdoctor.md) to opt in to Rsdoctor diagnostics.
 
 **Migration Example**:
 
@@ -409,7 +409,7 @@ export default {
 
 ### tools.tailwindcss
 
-**Change**: This configuration has been deprecated, please refer to [Tailwind Plugin Changes](/guides/upgrade/tailwindcss) and use Rsbuild's approach to integrate Tailwind CSS.
+**Change**: This configuration has been deprecated, please refer to [Tailwind Plugin Changes](/guides/upgrade/tailwindcss.md) and use Rsbuild's approach to integrate Tailwind CSS.
 
 ### tools.tsLoader
 
@@ -580,9 +580,12 @@ server: {
 
 If none of the above exist, create a `.browserslistrc` file with the following content for browsers supporting ES6:
 
-import DefaultBrowserslist from '@site-docs/components/default-browserslist';
-
-<DefaultBrowserslist />
+```yaml title=".browserslistrc"
+chrome >= 87
+edge >= 88
+firefox >= 78
+safari >= 14
+```
 
 ### output.enableAssetFallback
 

package/docs/guides/upgrade/{entry.mdx → entry.md}

@@ -45,7 +45,7 @@ src/
 ```
 
 :::tip
-You can modify the entry scanning directory through the [source.entriesDir](/configure/app/source/entries-dir) configuration.
+You can modify the entry scanning directory through the [source.entriesDir](/configure/app/source/entries-dir.md) configuration.
 :::
 
 ## Migration Steps
@@ -456,8 +456,8 @@ export default defineRuntimeConfig(entryName => {
 
 ## Related Links
 
-- [Page Entries](/guides/concept/entries)
-- [Runtime Configuration](/configure/app/runtime/0-intro)
-- [Runtime Plugins](/plugin/introduction.html#runtime-插件)
-- [source.entries Configuration](/configure/app/source/entries)
-- [source.entriesDir Configuration](/configure/app/source/entries-dir)
+- [Page Entries](/guides/concept/entries.md)
+- [Runtime Configuration](/configure/app/runtime/0-intro.md)
+- [Runtime Plugins](/plugin/introduction.md#runtime-插件)
+- [source.entries Configuration](/configure/app/source/entries.md)
+- [source.entriesDir Configuration](/configure/app/source/entries-dir.md)

package/docs/guides/upgrade/{other.mdx → other.md}

@@ -22,10 +22,10 @@ If your project's deployment configuration specifies a particular entry file nam
 
 Modern.js 3.0 has adjusted some runtime paths, and related import paths need to be updated. The path mapping is as follows:
 
-| Old Path | New Path | Description |
-|---------|---------|------|
-| `@modern-js/runtime/bff` | `@modern-js/plugin-bff/runtime` | BFF runtime path |
-| `@modern-js/runtime/server` | `@modern-js/server-runtime` | Server-side runtime path |
+| Old Path                    | New Path                        | Description              |
+| --------------------------- | ------------------------------- | ------------------------ |
+| `@modern-js/runtime/bff`    | `@modern-js/plugin-bff/runtime` | BFF runtime path         |
+| `@modern-js/runtime/server` | `@modern-js/server-runtime`     | Server-side runtime path |
 
 ## useRuntimeContext Deprecated
 
@@ -67,13 +67,13 @@ function App() {
 - `context` structure simplified: only contains `request` and `response`, no longer includes `logger`, `metrics`, etc.
 - Return value includes new properties: `initialData`, `routes`, etc.
 
-For detailed API documentation, please refer to the [RuntimeContext documentation](/apis/app/runtime/core/runtime-context).
+For detailed API documentation, please refer to the [RuntimeContext documentation](/apis/app/runtime/core/runtime-context.md).
 
 ## Pages Directory Convention-Based Routing No Longer Supported
 
 Modern.js 3.0 no longer supports the `pages` directory convention-based routing introduced in Modern.js 1.0, and now uniformly uses the `routes` directory convention-based routing.
 
-If your project uses the `pages` directory, you need to rename the `src/pages` directory to `src/routes` and update all import paths in the project that reference the `pages` directory. For detailed migration steps, please refer to the [Convention-Based Routing documentation](/guides/basic-features/routes/routes).
+If your project uses the `pages` directory, you need to rename the `src/pages` directory to `src/routes` and update all import paths in the project that reference the `pages` directory. For detailed migration steps, please refer to the [Convention-Based Routing documentation](/guides/basic-features/routes/routes.md).
 
 ## SSR Mode Default Value Change
 
@@ -112,9 +112,9 @@ Modern.js 3.0 removed the `modern new` and `modern upgrade` commands, and you ne
 
 **Handling**:
 
-- **Adding Entries**: You need to manually create entry directories and files according to the documentation. For detailed steps, please refer to the [Page Entries documentation](/guides/concept/entries).
+- **Adding Entries**: You need to manually create entry directories and files according to the documentation. For detailed steps, please refer to the [Page Entries documentation](/guides/concept/entries.md).
 - **Enabling Features**: You need to manually install dependencies and configure according to the corresponding feature documentation. For example, to enable BFF functionality, you need to install the `@modern-js/plugin-bff` plugin and configure it in `modern.config.ts`.
-- **Upgrading Dependencies**: You need to manually update the versions of all `@modern-js/**` packages in `package.json`, then reinstall dependencies. For detailed steps, please refer to the [Version Upgrade documentation](/guides/get-started/upgrade).
+- **Upgrading Dependencies**: You need to manually update the versions of all `@modern-js/**` packages in `package.json`, then reinstall dependencies. For detailed steps, please refer to the [Version Upgrade documentation](/guides/get-started/upgrade.md).
 
 :::info Note
 The purpose of removing these commands is to make the documentation more aligned with the default implementation approach of AI Agents, not encapsulating operations, so that developers can more clearly understand the specific steps of each operation, and it is also convenient for AI Agents to directly execute corresponding operations according to the documentation.

package/docs/guides/upgrade/{overview.mdx → overview.md}

@@ -9,10 +9,10 @@ Modern.js 3.0 brings significant improvements and changes, including:
 - **Build Tool Upgrade**: Default use of [Rspack](https://rspack.dev) for building, no longer supporting Webpack. Build configuration is aligned with [Rsbuild](https://v2.rsbuild.rs).
 - **React Ecosystem Upgrade**: Full support for [React 19](https://react.dev/blog/2024/04/25/react-19) and [React Router v7](https://reactrouter.com).
 - **Plugin System Refactoring**: Redesigned plugin API, supporting custom plugins at CLI, Runtime, and Server layers to extend framework capabilities.
-- **React Server Component**: Support for using React Server Component in [CSR](/guides/get-started/glossary#csr) and [SSR](/guides/basic-features/render/ssr) projects.
-- **Internationalization Enhancement**: Provides out-of-the-box [i18n plugin](/guides/advanced-features/international) to simplify internationalization development workflow.
-- **SSG Capability Improvement**: Provides complete [Static Site Generation (SSG)](/guides/basic-features/render/ssg) support.
-- **Route Configuration Enhancement**: Supports [config-based routing](/guides/basic-features/routes/config-routes), which can be used alone or combined with [convention-based routing](/guides/basic-features/routes/routes), providing more flexible route definition.
+- **React Server Component**: Support for using React Server Component in [CSR](/guides/get-started/glossary.md#csr) and [SSR](/guides/basic-features/render/ssr.md) projects.
+- **Internationalization Enhancement**: Provides out-of-the-box [i18n plugin](/guides/advanced-features/international.md) to simplify internationalization development workflow.
+- **SSG Capability Improvement**: Provides complete [Static Site Generation (SSG)](/guides/basic-features/render/ssg.md) support.
+- **Route Configuration Enhancement**: Supports [config-based routing](/guides/basic-features/routes/config-routes.md), which can be used alone or combined with [convention-based routing](/guides/basic-features/routes/routes.md), providing more flexible route definition.
 
 ## Pre-upgrade Checklist
 

package/docs/guides/upgrade/{tailwindcss.mdx → tailwindcss.md}

@@ -89,4 +89,3 @@ Change the CSS import method to the `@tailwind` directive approach.
 @tailwind components;
 @tailwind utilities;
 ```
-

package/docs/guides/upgrade/web-server.md

@@ -53,17 +53,17 @@ const middleware: MiddlewareHandler = async (c, next) => {
 
 ### Context API Comparison
 
-| Legacy API               | New API                 | Description            |
-| -------------------- | ---------------------- | ------------- |
-| `c.request.cookie`   | `getCookie(c, 'key')`  | Cookie reading      |
-| `c.req.cookie()`     | `getCookie(c, 'key')`  | Hono v4 deprecated    |
-| `c.request.pathname` | `c.req.path`           | Request path          |
-| `c.request.host`     | `c.req.header('Host')` | Request host          |
-| `c.request.query`    | `c.req.query()`        | Query parameters          |
-| `c.request.headers`  | `c.req.header()`       | Request headers           |
-| `c.response.status`  | `c.status()`           | Response status code         |
-| `c.response.set`     | `c.res.headers.set`    | Set response headers         |
-| `c.response.raw`     | `c.text` / `c.json`    | Response body           |
+| Legacy API           | New API                | Description          |
+| -------------------- | ---------------------- | -------------------- |
+| `c.request.cookie`   | `getCookie(c, 'key')`  | Cookie reading       |
+| `c.req.cookie()`     | `getCookie(c, 'key')`  | Hono v4 deprecated   |
+| `c.request.pathname` | `c.req.path`           | Request path         |
+| `c.request.host`     | `c.req.header('Host')` | Request host         |
+| `c.request.query`    | `c.req.query()`        | Query parameters     |
+| `c.request.headers`  | `c.req.header()`       | Request headers      |
+| `c.response.status`  | `c.status()`           | Response status code |
+| `c.response.set`     | `c.res.headers.set`    | Set response headers |
+| `c.response.raw`     | `c.text` / `c.json`    | Response body        |
 
 ## afterRender Hook
 

package/docs/index.md

@@ -1,4 +1,33 @@
----
-pageType: home
----
-# UltraModern.js 3.0 - A SuperApp framework for Effect, TanStack, SSR, BFF, and Micro Verticals
+[NEWUltraModern.js 3.0 is ready for SuperApps→](/guides/get-started/ultramodern)
+
+# UltraModern.js 3.0The SuperApp framework for Effect, TanStack, SSR, BFF, and Micro Verticals
+
+[UltraModern Guide](/guides/get-started/ultramodern)[Start Building](/guides/get-started/quick-start)
+
+[Rust BundlerBuilt with Rspack bundler for faster build speed.](/guides/concept/builder)[Integrated BFFDevelop BFF code in the same project, enjoy simple function calls.](/guides/advanced-features/bff/index)[Nested RoutesFile-as-route, comes with lots performance optimizations.](/guides/basic-features/routes/routes)[Multi-Rendering ModeRSC, SSR, SSG, all out of the box for you.](/guides/basic-features/render/ssr)[CSS SolutionsCSS Modules, CSS-in-JS, Tailwind CSS, take your pick.](/guides/basic-features/css/css)[Easy to ConfigureLaunch with zero configuration, then everything is configurable.](/configure/app/usage)
+
+Guide
+
+- [Start Building](/guides/get-started/quick-start)
+- [Core Concept](/guides/concept/entries)
+- [Basic Features](/guides/basic-features/routes)
+- [Advanced Features](/guides/advanced-features/bff)
+
+API
+
+- [Configuration](/configure/app/usage)
+- [Command](/apis/app/commands)
+- [Runtime](/apis/app/runtime/core/bootstrap)
+- [Conventions](/apis/app/hooks/src/app)
+
+Topic
+
+- [Module Federation](/guides/topic-detail/module-federation/introduce)
+- [Plugin System](/plugin/plugin-system)
+
+Help
+
+- [Changelog](https://github.com/BleedingDev/ultramodern.js/releases)
+- [GitHub Issues](https://github.com/BleedingDev/ultramodern.js/issues)
+- [Github Discussion](https://github.com/BleedingDev/ultramodern.js/discussions)
+