@modern-js/main-doc 2.0.3-alpha.0 → 2.2.0

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/framework-plugin/relationship.md

@@ -1,118 +0,0 @@
----
-title: 插件之间的关系
-sidebar_position: 4
----
-
-Modern.js 的插件配置对象提供了一系列的字段，用于控制插件顺序、互斥等能力，可用的字段如下：
-
-- `name`: `string`，设置当前插件的名称。
-- `pre`: `string[]`，这些插件最终会调整到当前插件前面。
-- `post`: `string[]`，这些插件最终会调整到当前插件后面。
-- `rivals`: `string[]`，互斥插件，遇到这些插件时会报错。
-- `required`: `string[]`，必需插件，插件列表中没有对应的插件时会报错。
-- `usePlugin`: `CliPlugin[]`，注册其他插件。
-
-通过以上参数可以实现插件的前置、后置、互斥、必需等逻辑。
-
-## 插件排序
-
-Modern.js 的插件通过 `pre`、`post` 参数来实现了插件排序的功能。
-
-### 前置插件
-
-默认情况下，插件会按照添加顺序依次执行，通过 `pre` 字段可以声明前置执行的插件。
-
-比如有下面两个插件：
-
-```ts title=foo.ts
-const foo = {
-  name: 'plugin-foo',
-};
-```
-
-```ts title=bar.ts
-const bar = {
-  name: 'plugin-bar',
-  pre: ['plugin-foo'],
-};
-```
-
-`bar` 插件在 `pre` 字段中配置了 `foo` 插件，因此 `foo` 插件一定会在 `bar` 插件之前执行。
-
-### 后置插件
-
-同样的，通过 `post` 字段可以声明后置执行的插件。
-
-```ts title=foo.ts
-const foo = {
-  name: 'plugin-foo',
-};
-```
-
-```ts title=bar.ts
-const bar = {
-  name: 'plugin-bar',
-  post: ['plugin-foo'],
-};
-```
-
-`bar` 插件在 `post` 字段中配置了 `foo` 插件，因此 `foo` 插件一定会在 `bar` 插件之后执行。
-
-## 互斥插件
-
-通过 `rivals` 字段可以声明插件间的互斥关系。
-
-有下面两个插件：
-
-```ts title=foo.ts
-const foo = {
-  name: 'plugin-foo',
-};
-```
-
-```ts title=bar.ts
-const bar = {
-  name: 'plugin-bar',
-  rivals: ['plugin-foo'],
-};
-```
-
-`bar` 插件在 `rivals` 字段中配置了 `foo` 插件，因此同时添加了 `foo` 插件和 `bar` 插件就会报错。
-
-## 必需插件
-
-通过 `required` 字段可以声明插件间的依赖关系。
-
-有下面两个插件：
-
-```ts title=foo.ts
-const foo = {
-  name: 'plugin-foo',
-};
-```
-
-```ts title=bar.ts
-const bar = {
-  name: 'plugin-bar',
-  required: ['plugin-foo'],
-};
-```
-
-`bar` 插件在 `required` 字段中配置了 `foo` 插件，因此使用 `bar` 插件时，如果未配置 `foo` 插件就会报错。
-
-## 注册插件
-
-当插件之间存在依赖关系时，我们也可以在一个插件中通过 `usePlugin` 主动注册另一个插件：
-
-```ts title=foo.ts
-const foo = () => ({
-  name: 'plugin-foo',
-});
-
-const bar = () => ({
-  name: 'plugin-bar',
-  usePlugin: [foo()],
-});
-```
-
-当使用者配置了 `bar` 插件时，`foo` 插件也会自动注册生效，使用者就不需要去额外注册 `foo` 插件了。

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/api/app.md

@@ -1,152 +0,0 @@
----
-sidebar_position: 1
----
-
-# @modern-js/codesmith-api-app
-
-The combination encapsulation of APIs commonly used in the development of microgenerators, including APIs encapsulation of other packages such as fs, git, npm, etc. When the requirements can be met, it is recommended to use the API of the npm package.
-
-## Use
-
-```typescript
-import { AppAPI } from '@modern-js/codesmith-api-app';
-
-export default async (context: GeneratorContext, generator: GeneratorCore) => {
-  const appApi = new AppAPI(context, generator);
-  await appApi.runInstall();
-}
-```
-
-- Create AppAPI instance, the parameter is the generator of the microgenerator function parameter, please see the composition of the microgenerator project for details.
-- Just call the API on its example.
-
-## API
-
-### checkEnvironment
-
-Check the current generator operating environment, the check items are:
-
-1. The node and node versions, the default is greater than 12.22.12, and the node version can be executed by passing parameters.
-2. Yarn, pnpm or npm can be used.
-
-Parameter:
-
-- nodeVersion?: `string`. Node version want to check.
-
-### runInstall
-
-To install dependency, you can pass in the install dependency command, which defaults to the `packageManager` value in config.
-
-Parameter:
-
-- command?: `string`, Install dependency command.
-
-### runGitAndInstall
-
-This function performs the following actions:
-
-1. Check whether the current generator execution directory is a git repository.
-2. If not a git repository, initialization is a git repository.
-3. Install dependencies.
-4. Commit the initial commit in a non-monorepo project (judging the condition, `isMonorepoSubProject` does not exist or is false in the config), the commit information is feat: init, and customize is supported.
-
-
-Parameter:
-- commitMessage?: `string`, Initialization commit message
-- installFunc?: `() => Promise<void>`. Install dependency function
-
-### forgeTemplate
-
-Render generator template file.
-
-Parameter:
-
-- templatePattern: `string`. Template files match regularities,for example: `templates/base-templates/**/*` .
-- filter?: `(resourceKey: string) => boolean`. Filter function, the parameter is the file path matching the `templatePattern`, return true to render the file, return false to render the file.
-- rename?: `(resourceKey: string) => string`. Rename function, the parameter is the file path matching `templatePattern`, and the new filename is returned. The templates directory at the beginning of `resourceKey` and the `.handlebars` suffix at the end will be replaced by default.
-- parameters?: `Record<string, any>`. Render parameter, when there is a handlebars or ejs variable in the template, use it to pass the corresponding variable value.
-- type?: `'handlebars' | 'ejs'`. Template file type, defaults to handlebars.
-
-For example:
-
-```typescript
-await appApi.forgeTemplate(
-    'templates/base-templates/**/*',
-    undefined,
-    resourceKey =>
-      resourceKey
-        .replace('templates/base-templates/', '')
-        .replace('.handlebars', ''),
-  );
-
- await appApi.forgeTemplate(
-    'templates/base-template/**/*',
-    resourceKey => !resourceKey.include('eslintrc.json'),
-    resourceKey =>
-      resourceKey
-        .replace('templates/base-template/', projectPath)
-        .replace('language', language as string)
-        .replace('.handlebars', ''),
-    {
-      name: packageName as string,
-      language,
-      isTs: language === Language.TS,
-      packageManager: getPackageManagerText(packageManager as any),
-    },
-  );
-```
-
-### showSuccessInfo
-
-Display success information.
-
-Parameter:
-
-- successInfo?: `string`. Default is Success.
-
-### runSubGenerator
-
-Run the subgenerator.
-
-Parameter:
-
-- subGenerator: `string`. Subgenerator name or path.
-- relativePwdPath?: `string`. The relative path to which the'string 'subgenerator runs.
-- config?: `Record<string, unknown>`. Default config configuration for subgenerator runs.
-
-For example:
-
-```typescript
-  await appApi.runSubGenerator(
-    getGeneratorPath('@modern-js/repo-generator', context.config.distTag),
-    undefined,
-    { ...context.config, hasPlugin: false },
-  );
-```
-
-### getInputBySchema
-
-User interaction input is done through schema.
-
-Parameter:
-
-- schema: `FormilySchema | Question[]`. Question list, supports Formily schema and inquirer types.
-- type: `'formily' | 'inquirer'`. Schema type, the default value is formily.
-- configValue: `Record<string, unknown> = {}`. Schema default value, the problem corresponding to the schema field passed in this value will no longer interact with the user.
-- validateMap?: `Record<string, (input: unknown, data?: Record<string, unknown>) => { success: boolean; error?: string }>`. Validation function for special fields in schema.
-- initValue?: `Record<string, any>`. Schema the initialization value of the field.
-
-For Formily Schema type support, please refer to [Customize input related type definition](/docs/guides/topic-detail/generator/plugin/api/input/type).
-
-### getInputBySchemaFunc
-
-By schema to complete user interaction input, schema parameter value as function, the user handles globalization problems, and only supports Formily schema.
-
-Parameter:
-
-- schema: `config?: Record<string, any>) => FormilySchema`. Get the problem list function, the config parameter is the config configuration information in the current generator.
-- configValue: `Record<string, unknown> = {}`. Schema default value, the problem corresponding to the schema field passed in this value will no longer interact with the user.
-- validateMap?: `Record<string, (input: unknown, data?: Record<string, unknown>) => { success: boolean; error?: string }>`. Validation function for special fields in schema.
-- initValue?: `Record<string, any>`. Schema the initialization value of the field.
-
-For Formily Schema type support, please refer to [Customize input related type definition](/docs/guides/topic-detail/generator/plugin/api/input/type).

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/api/ejs.md

@@ -1,56 +0,0 @@
----
-sidebar_position: 6
----
-
-# @modern-js/codesmith-api-ejs
-
-An API wrapper for file operations using [ejs] (https://ejs.co/) in microgenerators, providing a way to render individual template files and folders.
-
-## Use
-
-```typescript
-import { EjsAPI } from '@modern-js/codesmith-api-ejs';
-
-export default async (context: GeneratorContext, generator: GeneratorCore) => {
-  const ejsAPI = new EjsAPI(generator);
-  await ejsAPI.renderTemplate(
-     material.get('templates/a.js'),
-     target: 'b.js',
-     { data: "data" }
-   );
-}
-```
-
-- Create EjsAPI instance, the parameter is the generator of the microgenerator function parameter, please see the composition of the microgenerator project for details.
-- Just call the API on its example.
-
-## API
-
-### renderTemplate
-
-Render a single template file.
-
-Parameter:
-
-- templateResource: `FsResource`. Template file resource, used by  `context.materials.get(<filename>)`.
-- target: `string`. Target file path name.
-- parameters?: `Record<string, string>`. Render parameter.
-
-### renderTemplateDir
-
-Render template folder.
-
-Parameter:
-
-- material: `FsMaterial`. The material context of the current microgenerator execution.
-- findGlob: `string`. Template file matches the regular.
-- target: `(globMatch: string) => string`. The target file path generation function, the parameter is `resourceKey.`
-- options?: `RenderTemplateDirOptions`. Glob Find the file configuration, the specific function viewable is here [glob] (https://www.npmjs.com/package/glob).
-
-```typescript
-type RenderTemplateDirOptions = {
-  nodir?: boolean;
-  dot?: boolean;
-  ignore?: string | readonly string[];
-};
-```

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/api/fs.md

@@ -1,54 +0,0 @@
----
-sidebar_position: 3
----
-
-# @modern-js/codesmith-api-fs
-
-API wrapper for file operations in microgenerators, providing methods to render individual template files and folders. FsAPI is usually used to handle binaries or template files that cannot be handled with handlebars, ejs.
-
-## Use
-
-```typescript
-import { FsAPI } from '@modern-js/codesmith-api-fs';
-
-export default async (context: GeneratorContext, generator: GeneratorCore) => {
-  const handlebarApi = new HandlebarsAPI(generator);
-  await handlebarsAPI.renderFile(
-     material.get('templates/a.js'),
-     target: 'b.js'
-   );
-}
-```
-
-- Create FsAPI instance, the parameter is the generator of the microgenerator function parameter, please see the composition of the microgenerator project for details.
-- Just call the API on its example.
-
-## API
-
-### renderFile
-
-Render a single template file.
-
-Parameter:
-
-- resource: `FsResource`. Template file resource, used by  `context.materials.get(<filename>)`.
-- target: `string`. Target file path name.
-
-### renderDir
-
-Render template folder.
-
-Parameter:
-
-- material: `FsMaterial`. The material context of the current microgenerator execution.
-- findGlob: `string`. Template file matches the regular.
-- target: `(globMatch: string) => string`. The target file path generation function, the parameter is `resourceKey.`
-- options?: `RenderTemplateDirOptions`. Glob Find the file configuration, the specific function viewable is here [glob] (https://www.npmjs.com/package/glob).
-
-```typescript
-type RenderTemplateDirOptions = {
-  nodir?: boolean;
-  dot?: boolean;
-  ignore?: string | readonly string[];
-};
-```

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/api/git.md

@@ -1,49 +0,0 @@
----
-sidebar_position: 4
----
-
-# @modern-js/codesmith-api-git
-
-The API encapsulation of git-related operations in the micro-generator provides methods for judging git repository, initialization and commit code.
-
-## Use
-
-```typescript
-import { GitAPI } from '@modern-js/codesmith-api-git';
-
-export default async (context: GeneratorContext, generator: GeneratorCore) => {
-  const gitApi = new GitAPI(generatorCore, generatorContext);
-  await gitApi.initGitRepo();
-}
-```
-
-- Create GitAPI instance, the parameter is the generator of the microgenerator function parameter, please see the composition of the microgenerator project for details.
-
-- Just call the API on its example.
-
-## API
-
-### isInGitRepo
-
-Whether the current directory is a git repository.
-
-Parameter:
-
-- cwd?: `string`. The execution directory of the git command, the default is microgenerator `outputPath`.
-
-### initGitRepo
-
-The initialization is the git repository. The default branch name for init can be configured via `defaultBranch` in the generator config.
-
-Parameter:
-
-- cwd?: `string`. The execution directory of the git command, the default is microgenerator `outputPath`.
-- force?: `boolean`. Use this parameter to force git init when the current directory is already a git repository.
-
-### addAndCommit
-
-Execute `git add .` and `git commit` commit the current changes.
-
-Parameter:
-- commitMessage: `string`. Commit information.
-- cwd?: `string`. The execution directory of the git command, the default is microgenerator `outputPath`.

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/api/handlebars.md

@@ -1,58 +0,0 @@
----
-sidebar_position: 5
----
-
-# @modern-js/codesmith-api-handlebars
-
-An API wrapper for file operations using [handlebars] (https://handlebarsjs.com/) in the microgenerator, providing a way to render individual template files and folders.
-
-## Use
-
-```typescript
-import { HandlebarsAPI } from '@modern-js/codesmith-api-handlebars';
-
-export default async (context: GeneratorContext, generator: GeneratorCore) => {
-  const handlebarApi = new HandlebarsAPI(generator);
-  await handlebarsAPI.renderTemplate(
-     material.get('templates/a.js'),
-     target: 'b.js',
-     { data: "data" }
-   );
-}
-```
-
-- Create HandlebarsAPI instance, the parameter is the generator of the microgenerator function parameter, please see the composition of the microgenerator project for details.
-
-- Just call the API on its example.
-
-
-## API
-
-### renderTemplate
-
-Render a single template file.
-
-Parameter:
-
-- templateResource: `FsResource`. Template file resource, used by  `context.materials.get(<filename>)`.
-- target: `string`. Target file path name.
-- parameters?: `Record<string, string>`. Render parameter.
-
-### renderTemplateDir
-
-Render template folder.
-
-Parameter:
-
-- material: `FsMaterial`. The material context of the current microgenerator execution.
-- findGlob: `string`. Template file matches the regular.
-- target: `(globMatch: string) => string`. The target file path generation function, the parameter is `resourceKey.`
-- options?: `RenderTemplateDirOptions`. Glob Find the file configuration, the specific function viewable is here [glob] (https://www.npmjs.com/package/glob).
-
-```typescript
-type RenderTemplateDirOptions = {
-  nodir?: boolean;
-  dot?: boolean;
-  ignore?: string | readonly string[];
-};
-```

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/api/json.md

@@ -1,59 +0,0 @@
----
-sidebar_position: 2
----
-
-# @modern-js/codesmith-api-json
-
-The JSON API encapsulation in the microgenerator provides common JSON file operation methods.
-
-## Use
-
-```typescript
-import { JsonAPI } from '@modern-js/codesmith-api-json';
-
-export default async (context: GeneratorContext, generator: GeneratorCore) => {
-  const jsonAPI = new JsonAPI(generator);
-  await jsonAPI.update(
-    context.materials.default.get('package.json'),
-    {
-      query: {},
-      update: {
-        $set: {
-          'dependencies.@modern-js/plugin-bff': `^2.0.0`,
-        },
-      },
-    },
-  );
- }
-```
-
-- Create JsonAPI instance, the parameter is the generator of the microgenerator function parameter, please see the composition of the microgenerator project for details.
-- Just call the API on its example.
-
-
-## API
-
-### get
-
-Get the JSON file content.
-
-Parameter:
-- resource: `FsResource`. A file resource，get by `context.materials.default.get(<filename>)`.
-
-### extend
-
-Merge objects into a JSON file.
-
-Parameter:
-
-- resource: `FsResource`. A file resource，get by `context.materials.default.get(<filename>)`.
-- obj: `Record<string, any>`. Object to be merged.
-
-### update
-
-pdate object fields to JSON file.
-
-Parameter:
-
-- resource: `FsResource`. A file resource，get by `context.materials.default.get(<filename>)`.
-- operation: `{ query: Record<string, any>; update: Record<string, any> }`. Update operation, use gesture to view [declaration-update](https://www.npmjs.com/package/declaration-update) in detail.

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/api/npm.md

@@ -1,49 +0,0 @@
----
-sidebar_position: 7
----
-
-# @modern-js/codesmith-api-npm
-
-The NPM API encapsulation in the microgenerator provides a common method for installing dependencies of different NPM package management tools.
-
-## Use
-
-```typescript
-import { NpmAPI } from '@modern-js/codesmith-api-npm';
-
-export default async (context: GeneratorContext, generator: GeneratorCore) => {
-  const npmApi = new NpmAPI(generator);
-  await npmApi.pnpmInstall();
-}
-```
-
-- Create NpmAPI instance, the parameter is the generator of the microgenerator function parameter, please see the composition of the microgenerator project for details.
-
-- Just call the API on its example.
-
-
-## API
-
-### npmInstall
-
-Install dependency using npm.
-
-Parameter:
-
-- cwd?: `string`. The execution directory of the install command, the default is microgenerator `outputPath`.
-
-### yarnInstall
-
-Install dependency using yarn.
-
-Parameter:
-
-- cwd?: `string`. The execution directory of the install command, the default is microgenerator `outputPath`.
-
-### pnpmInstall
-
-Install dependency using pnpm.
-
-Parameter:
-
-- cwd?: `string`. The execution directory of the install command, the default is microgenerator `outputPath`.

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/develop.md

@@ -1,52 +0,0 @@
----
-sidebar_position: 3
----
-
-# Develop a microgenerator project
-
-## Create project
-
-Modern.js provides a microgenerator to create a microgenerator project, you can directly create a microgenerator project with the following commands:
-
-```bash
-$ mkdir <projectDir>
-$ npx @modern-js/codesmith-cli @modern-js/generator-generator
-
-? Package Name <generatorName>
-? Package Management Tool pnpm
-? Development Language TS
-```
-
-## Add template file
-
-In the templates folder of the project directory, it is used to store the template files required by the generator. If there is no template file, this step can be skipped.
-
-## Develop generator core logic
-
-In the project generated by default, it has been implemented to directly copy the templates directory file to the target project, and the core logic development of the generator can be completed directly in the `handleTemplateFile` function.
-
-## Test microgenerator
-
-After the development of the microgenerator is completed, you need to execute `pnpm run build` to compile the code. In development mode, you can use `pnpm run build --watch`.
-
-Codesmith provides the cli tool for running and testing the microgenerator. Execute it in the target directory with the following command:
-
-```bash
-npx @modern-js/codesmith-cli <generatorPath>
-```
-
-Where `generatorPath` is the absolute path of the above generator project.
-
-## Run the microgenerator
-
-After the generator publishes to npm, use the following command to execute:
-
-```bash
-npx @modern-js/codesmith-cli <generatorName>
-```
-
-Where generatorName is the generator package name.
-
-:::info
-`@modern-js/create` also supports running micro-generators, you can use `npx @modern-js/create --generator <generatorName>` to run customized micro-generators.
-:::

package/en/docusaurus-plugin-content-docs/current/guides/topic-detail/generator/codesmith/introduce.md

@@ -1,46 +0,0 @@
----
-sidebar_position: 1
----
-
-# What is a microgenerator
-
-Modern.js provides the `@modern-js/create` tool and the `new` command for initialization to create projects and the ability to enable some plugin functions, respectively, these tools are based on microgenerators, also known as codesmith implementations.
-
-Codesmith is committed to providing a set of micro-generator operating mechanism, and maintain the context information in the execution process of the micro-generator, so as to implement various operations based on files, commands, etc., to complete sophisticated operations.
-
-Codesmith also encapsulates the commonly used methods, and can directly use the API functions it provides, which can more easily implement its own micro-generator.
-
-## Core concept
-
-### GeneratorCore
-
-GeneratorCore is the core of codesmith running generator, maintaining the context and running methods during the execution of the generator.
-
-```typescript
-class GeneratorCore {
-  logger: ILogger;
-  materialsManager: MaterialsManager;
-  outputPath: string;
-  output:
-    fs: (file: string | number, data: any, options?: fs.WriteFileOptions | string) => Promise<void>;
-  };
-  _context: GeneratorContext;
-  addMaterial(key: string, material: FsMaterial): void;
-  runGenerator(generator: string, config?: Record<string, unknown>): Promise<void>;
-  runSubGenerator(subGenerator: string, relativePwdPath?: string, config?: Record<string, any>): Promise<void>;
-}
-```
-
-### Materials
-
-The micro-generator resource information currently only includes file resources (fsMaterials). Through this field, the template resources in the generator execution process can be obtained and operated through the API.
-
-```typescript
-class MaterialsManager {
-  materialMap: { // 资源映射关系
-    [materialUri: string]: FsMaterial;
-  };
-  loadLocalGenerator(generator: string): Promise<FsMaterial>;
-  loadRemoteGenerator(generator: string): Promise<FsMaterial>;
-}
-```