feat(dts-plugin): support tspc (#3662)

Author: 2heal1

.changeset/tasty-horses-juggle.md

@@ -0,0 +1,5 @@
+---
+'@module-federation/sdk': patch
+---
+
+feat(dts-plugin): support tspc

apps/website-new/docs/en/configure/dts.mdx

@@ -125,11 +125,11 @@ Whether to delete the generated type folder
 
 #### compilerInstance
 
-- Type: `'tsc' | 'vue-tsc'`
+- Type: `'tsc' | 'vue-tsc' | 'tspc' | string`
 - Required: No
 - Default value: `'tsc'`
 
-Example of compiled type
+Instance of compiled type
 
 ### consumeTypes
 

apps/website-new/docs/en/guide/troubleshooting/type/_meta.json

@@ -0,0 +1,4 @@
+[
+  "overview",
+  "TYPE-001"
+]

apps/website-new/docs/en/guide/troubleshooting/type/overview.md

@@ -0,0 +1,44 @@
+# Overview
+
+Type errors are divided into two types: fixed error code errors and scenario-related errors.
+
+## Fixed error code errors
+
+This type of error can be clearly captured in the code, and a fixed error code is assigned to each error. The error code consists of the error type and ID, such as `TYPE-001`. You can find the specified page based on the error code to understand the cause of the error and the solution.
+
+### Error code list
+
+* [TYPE-001](./TYPE-001)
+
+## Scenario-related errors
+
+This type of error is generated based on the user's specific scenario and has no fixed error code. The error message and handling method will vary depending on the scenario.
+
+### Generated type contains aliases
+
+**Phenomenon description**
+
+The type generated by the producer contains aliases and cannot be processed normally in the consumer.
+
+**How ​​to solve**
+
+1. Install [typescript-transform-paths](https://www.npmjs.com/package/typescript-transform-paths) and [ts-patch](https://www.npmjs.com/package/ts-patch)
+
+2. Apply `typescript-transform-paths` in `tsconfig.json`
+
+```diff
+{
+"compilerOptions": {
++ "plugins": [
++ { "transform": "typescript-transform-paths" },
++ {
++ "transform": "typescript-transform-paths",
++ "afterDeclarations": true
++ }
++ ],
+},
+}
+```
+
+3. Set [dts.generateTypes.compilerInstance](../../../configure/dts#compilerinstance) to `tspc`(`ts-patch` cli) 
+4. Regenerate types

apps/website-new/docs/zh/configure/dts.mdx

@@ -125,7 +125,7 @@ tsconfig 配置文件路径
 
 #### compilerInstance
 
-- 类型：`'tsc' | 'vue-tsc'`
+- 类型：`'tsc' | 'vue-tsc' | 'tspc' | string`
 - 是否必填：否
 - 默认值：`'tsc'`
 

apps/website-new/docs/zh/guide/troubleshooting/type/_meta.json

@@ -0,0 +1,4 @@
+[
+  "overview",
+  "TYPE-001"
+]

apps/website-new/docs/zh/guide/troubleshooting/type/overview.md

@@ -0,0 +1,43 @@
+# 概览
+
+类型错误分为两种类型：固定错误码错误和场景相关错误。
+
+## 固定错误码错误
+
+这类错误在代码中能够被明确捕获，并且会为每个错误分配一个固定的错误码。错误码由错误类型和 ID 组成，例如 `TYPE-001`。你可以根据错误码找到指定的页面，了解错误原因和解决方案。
+
+### 错误码列表
+
+* [TYPE-001](./TYPE-001)
+
+## 场景相关错误
+
+这类错误是根据用户的具体场景产生的，没有固定的错误码。其错误信息和处理方式会根据不同的场景而有所变化。
+
+### 生成类型包含别名
+
+**现象描述**
+
+生产者生成的类型含有别名，在消费者中无法正常处理。
+
+**如何解决**
+
+1. 安装 [typescript-transform-paths](https://www.npmjs.com/package/typescript-transform-paths) 和 [ts-patch](https://www.npmjs.com/package/ts-patch)
+2. 在 `tsconfig.json` 中应用 `typescript-transform-paths`
+
+```diff
+{
+  "compilerOptions": {
++   "plugins": [
++     { "transform": "typescript-transform-paths" },
++     {
++       "transform": "typescript-transform-paths",
++       "afterDeclarations": true
++     }
++   ],
+  },
+}
+```
+
+3. 设置 [dts.generateTypes.compilerInstance](../../../configure/dts#compilerinstance) 为 `tspc`(`ts-patch` cli) 
+4. 重新生成类型

packages/sdk/src/types/plugins/ModuleFederationPlugin.ts

@@ -165,7 +165,7 @@ export interface DtsRemoteOptions {
   deleteTypesFolder?: boolean;
   additionalFilesToCompile?: string[];
   compileInChildProcess?: boolean;
-  compilerInstance?: 'tsc' | 'vue-tsc';
+  compilerInstance?: 'tsc' | 'vue-tsc' | 'tspc' | string;
   generateAPITypes?: boolean;
   extractThirdParty?: boolean;
   extractRemoteTypes?: boolean;