chore: delete vmok docs releated content (#3429)

module-federation · Jan 8, 2025 · ec63773 · ec63773
1 parent 8c7d739
commit ec63773
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 17 deletions.
diff --git a/apps/website-new/docs/en/guide/basic/runtime.mdx b/apps/website-new/docs/en/guide/basic/runtime.mdx
@@ -313,15 +313,15 @@ init({
   remotes: [
     {
       name: '@demo/sub1',
-      entry: 'http://localhost:2001/vmok-manifest.json',
+      entry: 'http://localhost:2001/mf-manifest.json',
     },
     {
       name: '@demo/sub2',
-      entry: 'http://localhost:2002/vmok-manifest.json',
+      entry: 'http://localhost:2002/mf-manifest.json',
     },
     {
       name: '@demo/sub3',
-      entry: 'http://localhost:2003/vmok-manifest.json',
+      entry: 'http://localhost:2003/mf-manifest.json',
     },
   ],
 });
@@ -460,7 +460,7 @@ There are the following differences between `Federation Runtime` and `Build Plug
 | `shared` must provide specific version and instance information                                                              | `shared` only requires configuration rules, no specific version or instance information needed |
 | `shared` dependencies can only be used externally, cannot use external `shared` dependencies                                 | `shared` dependencies can be shared bidirectionally according to specific rules                |
 | Can affect the loading process through `runtime`'s `plugin` mechanism                                                        | Can affect the loading process through `runtimePlugin` configuration                           |
-| Pure runtime does not support remote type hints                                                                              | Supports remote type hints                                                                     |
+| Supports remote module type hints                                                                              | Supports remote module type hints                                                                     |
 
 ### Why Runtime
 

diff --git a/apps/website-new/docs/zh/guide/basic/runtime.mdx b/apps/website-new/docs/zh/guide/basic/runtime.mdx
@@ -293,15 +293,15 @@ init({
   remotes: [
     {
       name: '@demo/sub1',
-      entry: 'http://localhost:2001/vmok-manifest.json',
+      entry: 'http://localhost:2001/mf-manifest.json',
     },
     {
       name: '@demo/sub2',
-      entry: 'http://localhost:2002/vmok-manifest.json',
+      entry: 'http://localhost:2002/mf-manifest.json',
     },
     {
       name: '@demo/sub3',
-      entry: 'http://localhost:2003/vmok-manifest.json',
+      entry: 'http://localhost:2003/mf-manifest.json',
     },
   ],
 });
@@ -369,10 +369,12 @@ interface RemoteWithVersion {
 }
 ```
 
-- 细节
-  **info**: 设置 `force:true` 时请小心 !
+:::warning
+请谨慎设置 `force:true`!
+
+在你设置 `force: true` 后我们将合并远程（包括已加载的远程），并移除已加载的远程缓存，同时我们将使用 `console.warn` 来警告此操作可能存在风险。
+:::
 
-如果设置 `force: true`，它将合并远程（包括已加载的远程），并移除已加载的远程缓存，同时会使用 `console.warn` 来警告此操作可能存在风险。
 
 - Example
 
@@ -440,7 +442,7 @@ registerPlugins([runtimePlugin()]);
 | 设置 `shared` 必须提供具体版本和实例信息                                 | 设置 `shared` 只需要配置规则即可，无须提供具体版本及实例信息 |
 | `shared` 依赖只能供外部使用，无法使用外部 `shared` 依赖                  | `shared` 依赖按照特定规则双向共享                            |
 | 可以通过 `runtime` 的 `plugin` 机制影响加载流程                          | 可以通过 `runtimePlugin` 配置影响加载流程                    |
-| 纯运行时不支持远程类型提示                                               | 支持远程类型提示                                             |
+| 支持远程模块类型提示                                               | 支持远程模块类型提示                                             |
 
 ### Why Runtime
 

diff --git a/apps/website-new/docs/zh/guide/basic/type-prompt.mdx b/apps/website-new/docs/zh/guide/basic/type-prompt.mdx
@@ -89,9 +89,4 @@ A: 大概率是编译器监听了类型文件夹或者 `dist` 里的变动导致
 config.watchOptions = {
   ignored: ['**/node_modules/**', '**/@mf-types/**'],
 };
-```
-
-2. 动态类型未能正常获取
-
-* 请确保 `Vmok` 版本大于等于 `1.9.0`。
-* 动态类型需要访问页面加载指定模块后才会获取，请确保已经加载了对应模块。
+```