@bleedingdev/modern-js-app-tools 3.5.0-ultramodern.102 → 3.5.0-ultramodern.103

package/docs/configure/app/bff/effect.md

@@ -50,7 +50,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.102 @effect/opentelemetry@4.0.0-beta.102
+pnpm add effect@4.0.0-beta.107 @effect/opentelemetry@4.0.0-beta.107
 ```
 
 The pin is exact because UltraModern ships Effect as one lockstep cohort. Apps
@@ -214,27 +214,25 @@ through `pnpm-workspace.yaml` overrides. For the current UltraModern cohort,
 generated apps use:
 
 ```yaml
-minimumReleaseAgeExclude:
-  - 'effect@4.0.0-beta.102'
-  - '@effect/opentelemetry@4.0.0-beta.102'
-
 trustPolicyExclude:
-  - 'effect@4.0.0-beta.102'
-  - '@effect/opentelemetry@4.0.0-beta.102'
+  - 'effect@4.0.0-beta.107'
+  - '@effect/opentelemetry@4.0.0-beta.107'
 
 overrides:
-  '@effect/opentelemetry': 4.0.0-beta.102
-  '@effect/vitest': 4.0.0-beta.102
-  effect: 4.0.0-beta.102
+  '@effect/opentelemetry': 4.0.0-beta.107
+  '@effect/vitest': 4.0.0-beta.107
+  effect: 4.0.0-beta.107
 ```
 
 Do not add a different direct `effect` version in an app package. A mismatched
 Effect beta can fail while building layers or HTTP middleware because runtime
-services come from different package instances. Keep the generated
-policy exclusion entries with the same Effect cohort; they handle the
-framework-selected Effect beta versions before the 24-hour maturity window and
-the `effect`/`@effect/opentelemetry` trusted-publisher to provenance metadata
-transition without weakening UltraModern API architecture checks.
+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
+target. `trustPolicyExclude` is a separate policy:
+its exact `effect` and `@effect/opentelemetry` exceptions cover their
+trusted-publisher to provenance metadata transition and are not release-age
+approvals.
 
 ## Contract tests
 

package/docs/configure/app/server/rsc.md

@@ -3,24 +3,20 @@
 - **Type:** `boolean`
 - **Default:** `false`
 
-Enable React Server Components (RSC) configuration.
+Configure React Server Components (RSC).
 
-When set to `true`, enables React Server Components support in Modern.js. This allows components to be rendered on the server, providing better performance and developer experience.
+:::warning UltraModern availability
+RSC is not shipped or supported in the current UltraModern company distribution. Keep this option `false`. The Rspack Flight runtime remains under upstream review, and enabling RSC intentionally fails unless an application supplies the complete optional toolchain.
+
+Do not install `react-server-dom-rspack` or add an application-level pnpm patch to bypass this boundary.
+:::
 
 ```ts title="modern.config.ts"
 export default defineConfig({
   server: {
-    rsc: true,
+    rsc: false,
   },
 });
 ```
 
-:::tip Prerequisites
-Before enabling RSC, ensure:
-
-1. React and React DOM are upgraded to version 19 (recommended 19.2.4 or above)
-2. Install the `react-server-dom-rspack@0.0.2` dependency
-
-:::
-
-For more information about using RSC, see the [React Server Components guide](/guides/basic-features/render/rsc.md).
+The [React Server Components guide](/guides/basic-features/render/rsc.md) is retained as reference material for future upstream adoption.

package/docs/guides/basic-features/render/rsc.md

@@ -17,29 +17,20 @@ Before starting, we recommend reading React's official [Server Components docume
 
 ## Quick Start
 
-1. **Ensure React and React DOM are upgraded to version 19** (recommended version 19.2.4 or above)
-
-2. **Install the `react-server-dom-rspack@0.0.2` dependency**
-
-```bash
-npm install react-server-dom-rspack@0.0.2
-```
-
-:::warning Notes
-
-1. Currently, [Server Functions](https://react.dev/reference/rsc/server-functions) are not supported in SPA projects
-2. Currently, when building with Rspack, the output chunks and bundle size are not yet optimal. We will further optimize this in the near future
+:::warning UltraModern availability
+RSC is not shipped or supported in the current UltraModern company distribution. The framework keeps [`server.rsc`](/configure/app/server/rsc.md) disabled while the Rspack Flight runtime is completed upstream. Do not install `react-server-dom-rspack` or carry an application-level pnpm patch to enable it early.
 
+The remainder of this page is retained as reference material for future upstream adoption.
 :::
 
-3. Set [`server.rsc`](/configure/app/server/rsc.md) to `true`:
+Keep [`server.rsc`](/configure/app/server/rsc.md) set to `false`:
 
 ```ts title="modern.config.ts"
 import { defineConfig } from '@modern-js/app-tools';
 
 export default defineConfig({
   server: {
-    rsc: true,
+    rsc: false,
   },
 });
 ```

package/docs/guides/get-started/quick-start.md

@@ -38,7 +38,7 @@ Additionally, after installing nvm or fnm, when there is a `.nvmrc` file contain
 It is recommended to use [pnpm](https://pnpm.io/installation) to manage dependencies:
 
 ```bash
-mise use pnpm@11.17.0
+mise use pnpm@11.21.0
 ```
 
 :::note

package/docs/guides/get-started/ultramodern.md

@@ -138,13 +138,25 @@ 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.102`, `@effect/opentelemetry@4.0.0-beta.102`,
-and `@effect/vitest@4.0.0-beta.102`. 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.102` and
-`@effect/opentelemetry@4.0.0-beta.102` so the framework-selected Effect beta
-cohort is not blocked by the 24-hour age gate or trusted-publisher to
-provenance metadata transition.
+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
+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
+target. Independently, exact `trustPolicyExclude` entries for `effect`
+and `@effect/opentelemetry` cover their trusted-publisher to provenance
+metadata transition; they are not release-age approvals.
+
+### Current generated dependency baseline
+
+| 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`                                                |
 
 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

package/docs/guides/get-started/upgrade.md

@@ -81,16 +81,11 @@ When a nested dependency of the project has a problem and Modern.js cannot be up
 
 ### pnpm
 
-For projects using pnpm, add the following configuration to the `package.json` in the **root directory** of the project, and then run `pnpm install` again:
+For projects using pnpm, add the following configuration to `pnpm-workspace.yaml` in the **root directory** of the project, and then run `pnpm install` again:
 
-```json title="package.json"
-{
-  "pnpm": {
-    "overrides": {
-      "package-name": "^1.0.0"
-    }
-  }
-}
+```yaml title="pnpm-workspace.yaml"
+overrides:
+  package-name: ^1.0.0
 ```
 
 ### Yarn
@@ -118,6 +113,6 @@ For projects using Npm, add the following configuration to the `package.json` in
 ```
 
 :::info
-For Monorepo repositories, you can only lock dependency versions in the `package.json` in the root directory of the project, and it will affect all packages in the Monorepo.
+For Monorepo repositories, lock dependency versions in the package-manager configuration at the project root. The override affects every package in the Monorepo.
 
 :::

package/docs/llms.txt

@@ -167,7 +167,7 @@
 - [port](/configure/app/server/port.md): Type: numberDefault: 8080 When running the dev and serve commands, Modern.js will start with 8080 as the default port and automatically increase the port number when the port is occupied. You can use this configuration to modify the port number that the Server starts with:
 - [publicRoutes](/configure/app/server/public-routes.md): Type: ObjectDefault: Server-side routing rules generated based on file conventions, with one route rule generated for each file. This configuration option only applies to server-side routing and can customize the access route of resources under config/public/. The key of the object is the relative file path of the config/public/ (without using ./), and the value can be a string.
 - [routes](/configure/app/server/routes.md): Type: ObjectDefault: Server-side routing rules generated based on file conventions, with one route rule generated for each entry, and the entry name is equal to the route path. This configuration option only applies to server-side routing and can customize the access route of application entries.
-- [rsc](/configure/app/server/rsc.md): Type: booleanDefault: false Enable React Server Components (RSC) configuration. When set to true, enables React Server Components support in Modern.js. This allows components to be rendered on the server, providing better performance and developer experience. For more information about using RSC, see the React Server Components guide.
+- [rsc](/configure/app/server/rsc.md): Type: booleanDefault: false Configure React Server Components (RSC). The React Server Components guide is retained as reference material for future upstream adoption.
 - [ssrByEntries](/configure/app/server/ssr-by-entries.md): Type: ObjectDefault: undefined Set SSR options by entry, and the properties inside the option are the same as ssr. The specified value will be replaced and merged with the content of the SSR attribute, for example: In the above configuration, the project enables SSR as a whole, but the SSR rendering ability is disabled for the page-a entry.
 - [ssr](/configure/app/server/ssr.md): Type: boolean | ObjectDefault: false Enable SSR configuration. Boolean Type When the value type is boolean, it indicates whether to enable SSR deployment mode. The default is false to disable it. Object Type When the value type is Object, the following properties can be configured: Active Fallback In a production environment, there are scenarios where it is necessary to actively fallback an SSR project to CSR. Examples include When the SSR fails, a fallback to the CSR is required to ensure product availability.When the SSR is working normally, but there are rendering failures during csr, debugging is required.When the SSR server is under heavy load, it may be necessary to fallback some traffic directly to the CSR to avoid service downtime. By configuring server.ssr.forceCSR to true in the project, you can control this behavior through query strings or request headers. For example, in a custom Web Server middleware, you can actively fallback when traffic exceeds a certain threshold:
 - [tsconfigPath](/configure/app/server/tsconfig-path.md): Type: stringDefault: <appDirectory>/tsconfig.json Specifies the tsconfig file used by server-side TypeScript processes. This option affects: BFF / API compilation (@modern-js/plugin-bff)Custom server compilation (*.ts files under server/)Runtime Node-native TypeScript registration, such as SSR, modern.config.ts, and .ts files under config/ When this option is not set, <appDirectory>/tsconfig.json is used by default.

package/package.json

@@ -17,7 +17,7 @@
     "modern",
     "modern.js"
   ],
-  "version": "3.5.0-ultramodern.102",
+  "version": "3.5.0-ultramodern.103",
   "types": "./dist/types/index.d.ts",
   "main": "./dist/cjs/index.js",
   "exports": {
@@ -134,16 +134,16 @@
     "@babel/traverse": "^8.0.0",
     "@babel/types": "^8.0.0",
     "@loadable/component": "5.16.7",
-    "@modern-js/builder": "npm:@bleedingdev/modern-js-builder@3.5.0-ultramodern.102",
-    "@modern-js/i18n-utils": "npm:@bleedingdev/modern-js-i18n-utils@3.5.0-ultramodern.102",
-    "@modern-js/plugin": "npm:@bleedingdev/modern-js-plugin@3.5.0-ultramodern.102",
-    "@modern-js/plugin-data-loader": "npm:@bleedingdev/modern-js-plugin-data-loader@3.5.0-ultramodern.102",
-    "@modern-js/prod-server": "npm:@bleedingdev/modern-js-prod-server@3.5.0-ultramodern.102",
-    "@modern-js/server": "npm:@bleedingdev/modern-js-server@3.5.0-ultramodern.102",
-    "@modern-js/server-core": "npm:@bleedingdev/modern-js-server-core@3.5.0-ultramodern.102",
-    "@modern-js/server-utils": "npm:@bleedingdev/modern-js-server-utils@3.5.0-ultramodern.102",
-    "@modern-js/types": "npm:@bleedingdev/modern-js-types@3.5.0-ultramodern.102",
-    "@modern-js/utils": "npm:@bleedingdev/modern-js-utils@3.5.0-ultramodern.102",
+    "@modern-js/builder": "npm:@bleedingdev/modern-js-builder@3.5.0-ultramodern.103",
+    "@modern-js/i18n-utils": "npm:@bleedingdev/modern-js-i18n-utils@3.5.0-ultramodern.103",
+    "@modern-js/plugin": "npm:@bleedingdev/modern-js-plugin@3.5.0-ultramodern.103",
+    "@modern-js/plugin-data-loader": "npm:@bleedingdev/modern-js-plugin-data-loader@3.5.0-ultramodern.103",
+    "@modern-js/prod-server": "npm:@bleedingdev/modern-js-prod-server@3.5.0-ultramodern.103",
+    "@modern-js/server": "npm:@bleedingdev/modern-js-server@3.5.0-ultramodern.103",
+    "@modern-js/server-core": "npm:@bleedingdev/modern-js-server-core@3.5.0-ultramodern.103",
+    "@modern-js/server-utils": "npm:@bleedingdev/modern-js-server-utils@3.5.0-ultramodern.103",
+    "@modern-js/types": "npm:@bleedingdev/modern-js-types@3.5.0-ultramodern.103",
+    "@modern-js/utils": "npm:@bleedingdev/modern-js-utils@3.5.0-ultramodern.103",
     "@rsbuild/core": "2.1.5",
     "@swc/core": "1.15.43",
     "@swc/helpers": "^0.5.23",
@@ -161,7 +161,7 @@
     "@rslib/core": "0.23.2",
     "@scripts/rstest-config": "2.66.0",
     "@types/babel__traverse": "7.28.0",
-    "@types/node": "^26.1.1",
+    "@types/node": "^26.2.0",
     "@typescript/native-preview": "7.0.0-dev.20260707.2",
     "ts-node": "^10.9.2",
     "tsconfig-paths": "^4.2.0",