@fast-china/eslint-config 2.0.3 → 2.0.5

package/CHANGELOG.md

@@ -6,6 +6,29 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
 
 ## Unreleased
 
+## 2.0.5 - 2026-08-02
+
+### Changed
+
+- Upgraded public API documentation to complete TSDoc, including standard defaults, parameters, return values, thrown errors, remarks, examples, and package-level documentation.
+- Separated runtime, type-contract, rule-governance, and package-contract tests, and replaced the hard-coded release version assertion with SemVer and changelog consistency checks.
+
+## 2.0.4 - 2026-08-02
+
+### Added
+
+- Added dedicated `@fast-china/eslint-config/configs` and `@fast-china/eslint-config/constants` subpaths for advanced Flat Config composition.
+
+### Changed
+
+- Changed the `configs` and `rules` barrels to forward every module export, including configuration option types, while keeping configuration types out of the root entry.
+- Changed this repository's own ESLint configuration to compose focused config fragments and constants instead of calling the root `fastConfig()` factory.
+- Moved the `fastConfig()` implementation from `src/core/index.ts` directly into `src/index.ts` so the source root matches the package root entry.
+- Narrowed the default preset to conventional Vue 3 browser administration projects by making Markdown linting opt-in alongside React, Angular, and manifest sorting.
+- Removed Lodash policy selection from `fastConfig()` and the temporary `./lodash` subpath; optional Lodash restrictions now compose exclusively through `createLodashConfigs()` from `./configs`.
+- Changed `createGlobalIgnores()` to return a config array like the other fragment factories, so direct composition consistently uses spread syntax.
+- Updated `@eslint-react/eslint-plugin`, `@eslint/config-inspector`, and `globals` within their existing compatible version ranges.
+
 ## 2.0.3 - 2026-07-29
 
 ### Changed

package/README.md

@@ -21,9 +21,9 @@ A practical, typed ESLint Flat Config for Vue 3, React, Angular, Vite, TypeScrip
 
 ## Requirements
 
-- Node.js `^22.18.0` or `>=24.11.0`
+- Node.js `^22.18.0` or `^24.18.0`
 - ESLint `^10.0.0`
-- TypeScript `>=6.0.0 <6.1.0`
+- TypeScript `^6.0.0`
 
 These versions follow the runtime requirements of ESLint 10 and the included language plugins.
 
@@ -45,13 +45,15 @@ import fastChina from "@fast-china/eslint-config";
 export default fastChina();
 ```
 
-The default enables Vue 3, TypeScript, JavaScript, JSON dialects, Markdown, import ordering, RegExp checks, `.gitignore`, browser globals, and Node globals for common config, script, test, and CLI files.
+The default targets a conventional Vue 3 browser-based administration project. It enables Vue 3, TypeScript, JavaScript, JSON dialects, import ordering, RegExp checks, `.gitignore`, browser globals, and Node globals for common config, script, test, and CLI files. Markdown, React, Angular, and manifest sorting remain opt-in. Lodash policies are composed separately from the `configs` subpath.
 
 ## Other project types
 
-Use the default `fastConfig()` factory to keep only what a project needs.
+Other projects can either configure the root factory or compose focused fragments directly.
 
-### React + Vite
+### Use `fastConfig()`
+
+#### React + Vite
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -64,7 +66,7 @@ export default fastChina({
 
 React support applies the modern `@eslint-react` JavaScript/TypeScript preset, the official React Hooks Flat Config, and additional DOM safety checks. JSX and TSX are parsed by the existing JavaScript and TypeScript integrations. For a React-compatible JSX runtime such as Preact, set `react: { importSource: "preact" }`.
 
-### Angular
+#### Angular
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -89,7 +91,7 @@ export default fastChina({
 
 Angular requires the TypeScript integration; `angular: true` together with `typescript: false` fails early with a clear configuration error.
 
-### Node.js + TypeScript
+#### Node.js + TypeScript
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -100,7 +102,7 @@ export default fastChina({
 });
 ```
 
-### JavaScript only
+#### JavaScript only
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -114,7 +116,7 @@ export default fastChina({
 });
 ```
 
-### Type-aware TypeScript rules
+#### Type-aware TypeScript rules
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -129,6 +131,45 @@ export default fastChina({
 
 Type-aware linting uses the typescript-eslint Project Service. Project files must belong to a `tsconfig.json`. Most projects can omit `tsconfigRootDir`; complex monorepos should pass the directory containing the ESLint config explicitly.
 
+### Compose config fragments directly
+
+Projects that do not want the root factory can assemble only the required fragments. This React browser example is fully independent of `fastConfig()`:
+
+```js
+import { defineConfig } from "eslint/config";
+
+import {
+	createCommonConfigs,
+	createEnvironmentConfigs,
+	createGitignoreConfigs,
+	createGlobalIgnores,
+	createImportConfigs,
+	createJavaScriptConfigs,
+	createPrettierConfigs,
+	createReactConfigs,
+	createRegexpConfigs,
+	createTypeScriptConfigs,
+} from "@fast-china/eslint-config/configs";
+import { GLOBS_JAVASCRIPT, GLOBS_TYPESCRIPT } from "@fast-china/eslint-config/constants";
+
+const codeFiles = [...GLOBS_JAVASCRIPT, ...GLOBS_TYPESCRIPT];
+
+export default defineConfig([
+	...createGlobalIgnores(),
+	...createGitignoreConfigs(),
+	...createEnvironmentConfigs({ environment: "browser", files: codeFiles, nodeFiles: codeFiles }),
+	...createCommonConfigs(codeFiles),
+	...createJavaScriptConfigs(),
+	...createImportConfigs(codeFiles),
+	...createRegexpConfigs(codeFiles),
+	...createTypeScriptConfigs(),
+	...createReactConfigs({}, { javascript: true, typescript: true }),
+	...createPrettierConfigs(),
+]);
+```
+
+Use `createVueConfigs()` for Vue SFCs, `createAngularConfigs()` for Angular, or set `environment: "node"` for Node.js. Fragment order is significant: project overrides should remain last.
+
 ## Options
 
 | Option            | Default     | Purpose                                                                    |
@@ -141,8 +182,7 @@ Type-aware linting uses the typescript-eslint Project Service. Project files mus
 | `imports`         | `true`      | Enable import-x correctness and ordering rules.                            |
 | `javascript`      | `true`      | Process JavaScript and JSX files.                                          |
 | `json`            | `true`      | Enable recommended JSON, JSONC, and JSON5 rules.                           |
-| `lodash`          | `false`     | Select `"lodash"` or `"lodash-unified"` for static imports.                |
-| `markdown`        | `true`      | Enable the official Markdown language rules.                               |
+| `markdown`        | `false`     | Enable the official Markdown language rules.                               |
 | `prettier`        | `true`      | Disable ESLint rules that conflict with Prettier.                          |
 | `react`           | `false`     | Enable React/JSX/Hooks, or pass runtime and React-version settings.        |
 | `regexp`          | `true`      | Enable recommended RegExp rules.                                           |
@@ -160,10 +200,10 @@ Svelte, Astro, and Solid use different template or compiler semantics and are no
 
 ## Lodash import policy
 
-The default, `lodash: false`, leaves the dependency choice to the project. Select one policy when every static import should use the same package:
+Lodash policy is not a `fastConfig()` option. Import `createLodashConfigs()` from `@fast-china/eslint-config/configs` only when every static import should use one package:
 
-- `lodash: "lodash-unified"` rejects static imports and re-exports from `lodash`, `lodash-es`, and their subpaths.
-- `lodash: "lodash"` rejects static imports and re-exports from `lodash-es`, `lodash-unified`, and their subpaths. The `lodash` root and `lodash/*` method imports remain valid.
+- `createLodashConfigs("lodash-unified")` rejects static imports and re-exports from `lodash`, `lodash-es`, and their subpaths.
+- `createLodashConfigs("lodash")` rejects static imports and re-exports from `lodash-es`, `lodash-unified`, and their subpaths. The `lodash` root and `lodash/*` method imports remain valid.
 
 Choose `lodash-unified`:
 
@@ -172,10 +212,13 @@ pnpm add lodash-unified
 ```
 
 ```js
+import { defineConfig } from "eslint/config";
+
 import fastChina from "@fast-china/eslint-config";
+import { createLodashConfigs } from "@fast-china/eslint-config/configs";
 import { cloneDeep, debounce } from "lodash-unified";
 
-export default fastChina({ lodash: "lodash-unified" });
+export default defineConfig([...fastChina(), ...createLodashConfigs("lodash-unified")]);
 ```
 
 Choose standard `lodash`:
@@ -186,13 +229,16 @@ pnpm add -D @types/lodash
 ```
 
 ```js
+import { defineConfig } from "eslint/config";
+
 import fastChina from "@fast-china/eslint-config";
+import { createLodashConfigs } from "@fast-china/eslint-config/configs";
 import debounce from "lodash/debounce";
 
-export default fastChina({ lodash: "lodash" });
+export default defineConfig([...fastChina(), ...createLodashConfigs("lodash")]);
 ```
 
-This feature uses ESLint core `no-restricted-imports`, adds no plugin, and does not install Lodash for the project. It checks static `import`/`export` only, not dynamic `import()` or CommonJS `require()`. Setting `imports: false` disables import-x but leaves an explicitly selected Lodash policy active.
+This fragment uses ESLint core `no-restricted-imports`, adds no plugin, and does not install Lodash for the project. It checks static `import`/`export` only, not dynamic `import()` or CommonJS `require()`. It is independent of the root factory's `imports` option.
 
 If a later `rules` record or file-scoped override sets `no-restricted-imports`, ESLint replaces this complete policy instead of merging its options. Projects that need additional package restrictions can import raw `preferLodashRules` or `preferLodashUnifiedRules` from `@fast-china/eslint-config/rules` and maintain one combined rule.
 
@@ -262,7 +308,20 @@ export default fastChina(
 );
 ```
 
-The root entry exports only `fastConfig`, `defaultConfigOptions`, `defineRules`, and their related types. Advanced consumers can import the fully commented raw rule records from `@fast-china/eslint-config/rules`.
+The root entry exports only `fastConfig`, `defaultConfigOptions`, `defineRules`, `FastConfigOptions`, and `RuleOptions`. Advanced composition uses focused subpaths instead of widening the root API:
+
+- `@fast-china/eslint-config/configs` exports every configuration creator and its option types.
+- `@fast-china/eslint-config/constants` exports all maintained file globs.
+- `@fast-china/eslint-config/rules` exports the fully commented raw rule records and `RuleOptions`.
+
+```js
+import { defineConfig } from "eslint/config";
+
+import { createCommonConfigs, createTypeScriptConfigs } from "@fast-china/eslint-config/configs";
+import { GLOBS_TYPESCRIPT } from "@fast-china/eslint-config/constants";
+
+export default defineConfig([...createCommonConfigs(GLOBS_TYPESCRIPT), ...createTypeScriptConfigs({ typeChecked: true })]);
+```
 
 ## Prettier
 
@@ -284,7 +343,7 @@ pnpm check
 pnpm pack --dry-run
 ```
 
-Run `pnpm typegen` after upgrading ESLint or a plugin and commit `src/typegen.d.ts`; never edit the generated file manually. `pnpm check` verifies that generated types are current, builds the package, type-checks source, lints all supported file types, checks formatting, and runs both runtime and consumer type tests against the built package.
+Run `pnpm typegen` after upgrading ESLint or a plugin and commit `src/typegen.d.ts`; never edit the generated file manually. `pnpm test` rebuilds the package before running consumer type-contract, runtime integration, rule-governance, and package-contract tests. `pnpm check` adds source type-checking, full-repository linting, and formatting verification.
 
 See [CONTRIBUTING.md](./CONTRIBUTING.md) for the contribution workflow, the [default-rule and risk guide](./docs/rules-risk.md) for rule maintenance, and [the engineering audit](./docs/engineering-audit.zh.md) for the current quality baseline.
 

package/README.zh.md

@@ -21,9 +21,9 @@
 
 ## 环境要求
 
-- Node.js `^22.18.0` 或 `>=24.11.0`
+- Node.js `^22.18.0` 或 `^24.18.0`
 - ESLint `^10.0.0`
-- TypeScript `>=6.0.0 <6.1.0`
+- TypeScript `^6.0.0`
 
 这些版本范围与 ESLint 10 及内置语言插件的运行要求保持一致。
 
@@ -45,13 +45,15 @@ import fastChina from "@fast-china/eslint-config";
 export default fastChina();
 ```
 
-默认配置会启用 Vue 3、TypeScript、JavaScript、JSON 各方言、Markdown、导入排序、正则检查、`.gitignore` 与浏览器全局变量；常见配置文件、脚本、测试和 CLI 文件会额外获得 Node.js 全局变量。
+默认配置面向普通 Vue 3 浏览器后台管理项目，启用 Vue 3、TypeScript、JavaScript、JSON 各方言、导入排序、正则检查、`.gitignore` 与浏览器全局变量；常见配置文件、脚本、测试和 CLI 文件会额外获得 Node.js 全局变量。Markdown、React、Angular 和清单排序按需启用；Lodash 策略通过 `configs` 子路径独立组合。
 
 ## 适配其他项目
 
-通过默认导出的 `fastConfig()` 只保留项目真正需要的能力。
+其他项目可以配置根工厂，也可以完全绕过根工厂，直接组合所需片段。
 
-### React + Vite
+### 使用 `fastConfig()`
+
+#### React + Vite
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -64,7 +66,7 @@ export default fastChina({
 
 React 集成会应用现代 `@eslint-react` JavaScript/TypeScript 预置、React 官方 Hooks Flat Config，以及额外的 DOM 安全检查。JSX 与 TSX 分别复用现有 JavaScript、TypeScript 解析能力。Preact 等兼容 React 的 JSX 运行时可设置 `react: { importSource: "preact" }`。
 
-### Angular
+#### Angular
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -89,7 +91,7 @@ export default fastChina({
 
 Angular 依赖 TypeScript 集成；同时设置 `angular: true` 与 `typescript: false` 时会立即抛出清晰的配置错误。
 
-### Node.js + TypeScript
+#### Node.js + TypeScript
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -100,7 +102,7 @@ export default fastChina({
 });
 ```
 
-### 纯 JavaScript
+#### 纯 JavaScript
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -114,7 +116,7 @@ export default fastChina({
 });
 ```
 
-### 启用 TypeScript 类型感知规则
+#### 启用 TypeScript 类型感知规则
 
 ```js
 import fastChina from "@fast-china/eslint-config";
@@ -129,6 +131,45 @@ export default fastChina({
 
 类型感知模式使用 typescript-eslint Project Service，被检查的文件必须属于某个 `tsconfig.json`。普通项目通常可省略 `tsconfigRootDir`；复杂 monorepo 建议显式传入配置文件所在目录。
 
+### 直接组合配置片段
+
+不希望使用根工厂的项目可以只组装需要的片段。以下 React 浏览器项目示例完全不依赖 `fastConfig()`：
+
+```js
+import { defineConfig } from "eslint/config";
+
+import {
+	createCommonConfigs,
+	createEnvironmentConfigs,
+	createGitignoreConfigs,
+	createGlobalIgnores,
+	createImportConfigs,
+	createJavaScriptConfigs,
+	createPrettierConfigs,
+	createReactConfigs,
+	createRegexpConfigs,
+	createTypeScriptConfigs,
+} from "@fast-china/eslint-config/configs";
+import { GLOBS_JAVASCRIPT, GLOBS_TYPESCRIPT } from "@fast-china/eslint-config/constants";
+
+const codeFiles = [...GLOBS_JAVASCRIPT, ...GLOBS_TYPESCRIPT];
+
+export default defineConfig([
+	...createGlobalIgnores(),
+	...createGitignoreConfigs(),
+	...createEnvironmentConfigs({ environment: "browser", files: codeFiles, nodeFiles: codeFiles }),
+	...createCommonConfigs(codeFiles),
+	...createJavaScriptConfigs(),
+	...createImportConfigs(codeFiles),
+	...createRegexpConfigs(codeFiles),
+	...createTypeScriptConfigs(),
+	...createReactConfigs({}, { javascript: true, typescript: true }),
+	...createPrettierConfigs(),
+]);
+```
+
+Vue SFC 可增加 `createVueConfigs()`，Angular 可增加 `createAngularConfigs()`，Node.js 项目则将环境设为 `"node"`。配置片段的顺序具有语义，项目覆写应始终放在最后。
+
 ## 配置选项
 
 | 选项              | 默认值      | 作用                                                           |
@@ -141,8 +182,7 @@ export default fastChina({
 | `imports`         | `true`      | 启用 import-x 正确性与排序规则。                               |
 | `javascript`      | `true`      | 处理 JavaScript 与 JSX。                                       |
 | `json`            | `true`      | 启用 JSON、JSONC 与 JSON5 推荐规则。                           |
-| `lodash`          | `false`     | 可选 `"lodash"` 或 `"lodash-unified"`，统一静态导入来源。      |
-| `markdown`        | `true`      | 启用官方 Markdown 语言规则。                                   |
+| `markdown`        | `false`     | 启用官方 Markdown 语言规则。                                   |
 | `prettier`        | `true`      | 关闭与 Prettier 冲突的 ESLint 规则。                           |
 | `react`           | `false`     | 启用 React、JSX 与 Hooks，或传入运行时和 React 版本设置。      |
 | `regexp`          | `true`      | 启用推荐的正则表达式规则。                                     |
@@ -160,10 +200,10 @@ Svelte、Astro 与 Solid 具有不同的模板或编译器语义，目前不会
 
 ## Lodash 导入策略
 
-默认值 `lodash: false` 不限制项目选择。需要统一依赖入口时，可选择以下任一策略：
+Lodash 策略不是 `fastConfig()` 选项。只有需要统一静态导入来源时，才从 `@fast-china/eslint-config/configs` 导入 `createLodashConfigs()`：
 
-- `lodash: "lodash-unified"`：禁止从 `lodash`、`lodash-es` 及其子路径静态导入或重新导出。
-- `lodash: "lodash"`：禁止从 `lodash-es`、`lodash-unified` 及其子路径静态导入或重新导出；允许 `lodash` 根入口和 `lodash/*` 按方法导入。
+- `createLodashConfigs("lodash-unified")`：禁止从 `lodash`、`lodash-es` 及其子路径静态导入或重新导出。
+- `createLodashConfigs("lodash")`：禁止从 `lodash-es`、`lodash-unified` 及其子路径静态导入或重新导出；允许 `lodash` 根入口和 `lodash/*` 按方法导入。
 
 选择 `lodash-unified`：
 
@@ -172,10 +212,13 @@ pnpm add lodash-unified
 ```
 
 ```js
+import { defineConfig } from "eslint/config";
+
 import fastChina from "@fast-china/eslint-config";
+import { createLodashConfigs } from "@fast-china/eslint-config/configs";
 import { cloneDeep, debounce } from "lodash-unified";
 
-export default fastChina({ lodash: "lodash-unified" });
+export default defineConfig([...fastChina(), ...createLodashConfigs("lodash-unified")]);
 ```
 
 选择标准 `lodash`：
@@ -186,13 +229,16 @@ pnpm add -D @types/lodash
 ```
 
 ```js
+import { defineConfig } from "eslint/config";
+
 import fastChina from "@fast-china/eslint-config";
+import { createLodashConfigs } from "@fast-china/eslint-config/configs";
 import debounce from "lodash/debounce";
 
-export default fastChina({ lodash: "lodash" });
+export default defineConfig([...fastChina(), ...createLodashConfigs("lodash")]);
 ```
 
-该能力使用 ESLint 核心 `no-restricted-imports`，不需要额外插件，也不会替项目安装 Lodash。它只检查静态 `import`/`export`，不检查动态 `import()` 或 CommonJS `require()`。`imports: false` 只关闭 import-x，不会关闭已经显式选择的 Lodash 策略。
+该片段使用 ESLint 核心 `no-restricted-imports`，不需要额外插件，也不会替项目安装 Lodash。它只检查静态 `import`/`export`，不检查动态 `import()` 或 CommonJS `require()`，并且独立于根工厂的 `imports` 选项。
 
 如果后续 `rules` 或文件级覆写再次设置 `no-restricted-imports`，ESLint 会用后面的完整规则替换这套策略，而不是合并选项。需要组合更多包限制时，可从 `@fast-china/eslint-config/rules` 导入原始 `preferLodashRules` 或 `preferLodashUnifiedRules`，统一维护一份完整规则。
 
@@ -262,7 +308,20 @@ export default fastChina(
 );
 ```
 
-根入口只公开 `fastConfig`、`defaultConfigOptions`、`defineRules` 及相关类型。高级使用者可以从 `@fast-china/eslint-config/rules` 导入有完整注释的原始规则记录。
+根入口只公开 `fastConfig`、`defaultConfigOptions`、`defineRules`、`FastConfigOptions` 和 `RuleOptions`。高级组合通过职责明确的子路径完成，避免扩大根入口：
+
+- `@fast-china/eslint-config/configs` 导出全部配置创建函数及其选项类型。
+- `@fast-china/eslint-config/constants` 导出项目维护的全部文件 glob。
+- `@fast-china/eslint-config/rules` 导出带完整注释的原始规则记录和 `RuleOptions`。
+
+```js
+import { defineConfig } from "eslint/config";
+
+import { createCommonConfigs, createTypeScriptConfigs } from "@fast-china/eslint-config/configs";
+import { GLOBS_TYPESCRIPT } from "@fast-china/eslint-config/constants";
+
+export default defineConfig([...createCommonConfigs(GLOBS_TYPESCRIPT), ...createTypeScriptConfigs({ typeChecked: true })]);
+```
 
 ## Prettier
 
@@ -284,7 +343,7 @@ pnpm check
 pnpm pack --dry-run
 ```
 
-升级 ESLint 或插件后运行 `pnpm typegen` 并提交 `src/typegen.d.ts`；不要手工编辑生成文件。`pnpm check` 会验证生成类型没有漂移，然后依次构建、类型检查、检查所有支持的文件类型、验证格式，并针对构建后的真实包运行运行时和消费者类型测试。
+升级 ESLint 或插件后运行 `pnpm typegen` 并提交 `src/typegen.d.ts`；不要手工编辑生成文件。`pnpm test` 会先重新构建发布产物，再分别执行消费者类型契约、运行时集成、规则治理和发布包契约测试。`pnpm check` 在此基础上增加源码类型检查、全仓 ESLint 和格式验证。
 
 贡献流程见 [CONTRIBUTING.md](./CONTRIBUTING.md)，规则维护约定见 [默认规则与风险指南](./docs/rules-risk.zh.md)，本次工程审查和质量基线见 [工程质量审查报告](./docs/engineering-audit.zh.md)。
 

package/dist/configs/angular.d.mts

@@ -0,0 +1,46 @@
+//#region src/configs/angular.d.ts
+/**
+ * Angular TypeScript 源码与 HTML 模板检查的细分选项。
+ *
+ * @remarks
+ * 该对象通过 `fastConfig({ angular: { ... } })` 传入。只要传入对象，Angular 支持就会
+ * 被启用；未指定的字段继续使用各自默认值。Angular 配置始终包含框架 TypeScript 规则
+ * 和外部 `.html` 模板基础规则，本接口只控制成本或迁移影响较高的可选部分。
+ *
+ * Angular 支持依赖顶层 `typescript` 能力，不能与 `typescript: false` 同时使用。
+ * 这些选项不会修改 Angular 编译器、CLI 或模板类型检查配置。
+ */
+interface AngularConfigOptions {
+  /**
+   * 是否使用 Angular 官方 processor，从 TypeScript 文件的
+   * `@Component({ template: ... })` 元数据中提取内联 HTML 并复用模板规则进行检查。
+   *
+   * 关闭后仍会检查 Angular TypeScript 源码和外部 `.html` 模板，只是不再处理组件中的
+   * 内联模板。大型项目若主要使用外部模板，或 processor 与其他工具发生冲突，可暂时关闭。
+   * @defaultValue `true`
+   */
+  inlineTemplates?: boolean;
+  /**
+   * 是否在模板基础正确性规则之外启用 Angular 模板无障碍规则组。
+   *
+   * 该规则组检查替代文本、键盘交互、焦点、表单标签和 ARIA 等可访问性问题，适用于
+   * 外部模板与已提取的内联模板。关闭后仍保留模板语法、严格比较和现代控制流等基础规则。
+   * 对旧项目而言可能一次产生较多报告，建议在确认迁移计划后再决定是否临时关闭。
+   * @defaultValue `true`
+   */
+  templateAccessibility?: boolean;
+}
+/**
+ * 创建 Angular TypeScript、外部 HTML 模板与内联模板配置。
+ *
+ * @remarks
+ * Angular 支持依赖工厂的 TypeScript 配置先注册 typescript-eslint 解析器；模板由
+ * Angular 专用 parser 解析，内联模板通过官方 processor 复用同一套 HTML 规则。
+ *
+ * @param options - 控制内联模板处理与模板无障碍规则的 Angular 选项。
+ * @returns 按 TypeScript 源码、外部模板顺序排列的 ESLint Flat Config 数组。
+ */
+declare const createAngularConfigs: ({ inlineTemplates, templateAccessibility }?: AngularConfigOptions) => import("eslint/config").ConfigObject[];
+//#endregion
+export { AngularConfigOptions, createAngularConfigs };
+//# sourceMappingURL=angular.d.mts.map

package/dist/configs/angular.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"angular.d.mts","names":[],"sources":["../../src/configs/angular.ts"],"mappings":";;;;;;;;;;;;UAqBiB;;;;;;;;;EAShB;;;;;;;;;EASA;;;;;;;;;;;;cAaY,yBAAwB,iBAAA,0BAA0D,iDAAyB"}

package/dist/configs/angular.mjs

@@ -0,0 +1,37 @@
+import { GLOB_ANGULAR_TEMPLATE, GLOB_ANGULAR_TYPESCRIPT } from "../constants/index.mjs";
+import { angularRules, angularTemplateAccessibilityRules, angularTemplateRules } from "../rules/angular.mjs";
+import angularPlugin from "@angular-eslint/eslint-plugin";
+import angularTemplatePlugin from "@angular-eslint/eslint-plugin-template";
+import angularTemplateParser from "@angular-eslint/template-parser";
+import { defineConfig } from "eslint/config";
+//#region src/configs/angular.ts
+/**
+* 创建 Angular TypeScript、外部 HTML 模板与内联模板配置。
+*
+* @remarks
+* Angular 支持依赖工厂的 TypeScript 配置先注册 typescript-eslint 解析器；模板由
+* Angular 专用 parser 解析，内联模板通过官方 processor 复用同一套 HTML 规则。
+*
+* @param options - 控制内联模板处理与模板无障碍规则的 Angular 选项。
+* @returns 按 TypeScript 源码、外部模板顺序排列的 ESLint Flat Config 数组。
+*/
+const createAngularConfigs = ({ inlineTemplates = true, templateAccessibility = true } = {}) => defineConfig([{
+	name: inlineTemplates ? "@fast-china/angular/typescript-with-inline-templates" : "@fast-china/angular/typescript",
+	files: [GLOB_ANGULAR_TYPESCRIPT],
+	plugins: { "@angular-eslint": angularPlugin },
+	...inlineTemplates ? { processor: angularTemplatePlugin.processors["extract-inline-html"] } : {},
+	rules: angularRules
+}, {
+	name: templateAccessibility ? "@fast-china/angular/template-accessibility" : "@fast-china/angular/template",
+	files: [GLOB_ANGULAR_TEMPLATE],
+	languageOptions: { parser: angularTemplateParser },
+	plugins: { "@angular-eslint/template": angularTemplatePlugin },
+	rules: {
+		...angularTemplateRules,
+		...templateAccessibility ? angularTemplateAccessibilityRules : {}
+	}
+}]);
+//#endregion
+export { createAngularConfigs };
+
+//# sourceMappingURL=angular.mjs.map

package/dist/configs/angular.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"angular.mjs","names":[],"sources":["../../src/configs/angular.ts"],"sourcesContent":["import angularPlugin from \"@angular-eslint/eslint-plugin\";\nimport angularTemplatePlugin from \"@angular-eslint/eslint-plugin-template\";\nimport angularTemplateParser from \"@angular-eslint/template-parser\";\nimport { defineConfig } from \"eslint/config\";\n\nimport { GLOB_ANGULAR_TEMPLATE, GLOB_ANGULAR_TYPESCRIPT } from \"../constants\";\nimport { angularRules, angularTemplateAccessibilityRules, angularTemplateRules } from \"../rules\";\n\nimport type { ESLint, Linter } from \"eslint\";\n\n/**\n * Angular TypeScript 源码与 HTML 模板检查的细分选项。\n *\n * @remarks\n * 该对象通过 `fastConfig({ angular: { ... } })` 传入。只要传入对象，Angular 支持就会\n * 被启用；未指定的字段继续使用各自默认值。Angular 配置始终包含框架 TypeScript 规则\n * 和外部 `.html` 模板基础规则，本接口只控制成本或迁移影响较高的可选部分。\n *\n * Angular 支持依赖顶层 `typescript` 能力，不能与 `typescript: false` 同时使用。\n * 这些选项不会修改 Angular 编译器、CLI 或模板类型检查配置。\n */\nexport interface AngularConfigOptions {\n\t/**\n\t * 是否使用 Angular 官方 processor，从 TypeScript 文件的\n\t * `@Component({ template: ... })` 元数据中提取内联 HTML 并复用模板规则进行检查。\n\t *\n\t * 关闭后仍会检查 Angular TypeScript 源码和外部 `.html` 模板，只是不再处理组件中的\n\t * 内联模板。大型项目若主要使用外部模板，或 processor 与其他工具发生冲突，可暂时关闭。\n\t * @defaultValue `true`\n\t */\n\tinlineTemplates?: boolean;\n\t/**\n\t * 是否在模板基础正确性规则之外启用 Angular 模板无障碍规则组。\n\t *\n\t * 该规则组检查替代文本、键盘交互、焦点、表单标签和 ARIA 等可访问性问题，适用于\n\t * 外部模板与已提取的内联模板。关闭后仍保留模板语法、严格比较和现代控制流等基础规则。\n\t * 对旧项目而言可能一次产生较多报告，建议在确认迁移计划后再决定是否临时关闭。\n\t * @defaultValue `true`\n\t */\n\ttemplateAccessibility?: boolean;\n}\n\n/**\n * 创建 Angular TypeScript、外部 HTML 模板与内联模板配置。\n *\n * @remarks\n * Angular 支持依赖工厂的 TypeScript 配置先注册 typescript-eslint 解析器；模板由\n * Angular 专用 parser 解析，内联模板通过官方 processor 复用同一套 HTML 规则。\n *\n * @param options - 控制内联模板处理与模板无障碍规则的 Angular 选项。\n * @returns 按 TypeScript 源码、外部模板顺序排列的 ESLint Flat Config 数组。\n */\nexport const createAngularConfigs = ({ inlineTemplates = true, templateAccessibility = true }: AngularConfigOptions = {}) =>\n\tdefineConfig([\n\t\t{\n\t\t\tname: inlineTemplates ? \"@fast-china/angular/typescript-with-inline-templates\" : \"@fast-china/angular/typescript\",\n\t\t\tfiles: [GLOB_ANGULAR_TYPESCRIPT],\n\t\t\tplugins: {\n\t\t\t\t\"@angular-eslint\": angularPlugin as unknown as ESLint.Plugin,\n\t\t\t},\n\t\t\t...(inlineTemplates\n\t\t\t\t? {\n\t\t\t\t\t\tprocessor: angularTemplatePlugin.processors[\"extract-inline-html\"] as Linter.Processor,\n\t\t\t\t\t}\n\t\t\t\t: {}),\n\t\t\trules: angularRules,\n\t\t},\n\t\t{\n\t\t\tname: templateAccessibility ? \"@fast-china/angular/template-accessibility\" : \"@fast-china/angular/template\",\n\t\t\tfiles: [GLOB_ANGULAR_TEMPLATE],\n\t\t\tlanguageOptions: {\n\t\t\t\tparser: angularTemplateParser as unknown as Linter.Parser,\n\t\t\t},\n\t\t\tplugins: {\n\t\t\t\t\"@angular-eslint/template\": angularTemplatePlugin as unknown as ESLint.Plugin,\n\t\t\t},\n\t\t\trules: {\n\t\t\t\t...angularTemplateRules,\n\t\t\t\t...(templateAccessibility ? angularTemplateAccessibilityRules : {}),\n\t\t\t},\n\t\t},\n\t]);\n"],"mappings":";;;;;;;;;;;;;;;;;AAoDA,MAAa,wBAAwB,EAAE,kBAAkB,MAAM,wBAAwB,SAA+B,CAAC,MACtH,aAAa,CACZ;CACC,MAAM,kBAAkB,yDAAyD;CACjF,OAAO,CAAC,uBAAuB;CAC/B,SAAS,EACR,mBAAmB,cACpB;CACA,GAAI,kBACD,EACA,WAAW,sBAAsB,WAAW,uBAC7C,IACC,CAAC;CACJ,OAAO;AACR,GACA;CACC,MAAM,wBAAwB,+CAA+C;CAC7E,OAAO,CAAC,qBAAqB;CAC7B,iBAAiB,EAChB,QAAQ,sBACT;CACA,SAAS,EACR,4BAA4B,sBAC7B;CACA,OAAO;EACN,GAAG;EACH,GAAI,wBAAwB,oCAAoC,CAAC;CAClE;AACD,CACD,CAAC"}

package/dist/configs/common.d.mts

@@ -0,0 +1,15 @@
+//#region src/configs/common.d.ts
+/**
+ * 创建跨 JavaScript、TypeScript 与 Vue 脚本生效的通用配置。
+ *
+ * @remarks
+ * 除公共规则外，这里还把无效的 `eslint-disable` 指令提升为错误，避免规则被移除后
+ * 留下长期失效的抑制注释。
+ *
+ * @param files - 应用公共规则的 ESLint glob 列表。
+ * @returns 包含公共规则与无效禁用指令检查的 Flat Config 数组。
+ */
+declare const createCommonConfigs: (files?: readonly string[]) => import("eslint/config").ConfigObject[];
+//#endregion
+export { createCommonConfigs };
+//# sourceMappingURL=common.d.mts.map

package/dist/configs/common.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"common.d.mts","names":[],"sources":["../../src/configs/common.ts"],"mappings":";;;;;;;;;;;cAea,sBAAuB,sDAAqC"}

package/dist/configs/common.mjs

@@ -0,0 +1,24 @@
+import { GLOBS_CODE } from "../constants/index.mjs";
+import { commonRules } from "../rules/common.mjs";
+import { defineConfig } from "eslint/config";
+//#region src/configs/common.ts
+/**
+* 创建跨 JavaScript、TypeScript 与 Vue 脚本生效的通用配置。
+*
+* @remarks
+* 除公共规则外，这里还把无效的 `eslint-disable` 指令提升为错误，避免规则被移除后
+* 留下长期失效的抑制注释。
+*
+* @param files - 应用公共规则的 ESLint glob 列表。
+* @returns 包含公共规则与无效禁用指令检查的 Flat Config 数组。
+*/
+const createCommonConfigs = (files = GLOBS_CODE) => defineConfig([{
+	name: "@fast-china/common",
+	files: [...files],
+	linterOptions: { reportUnusedDisableDirectives: "error" },
+	rules: commonRules
+}]);
+//#endregion
+export { createCommonConfigs };
+
+//# sourceMappingURL=common.mjs.map

package/dist/configs/common.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"common.mjs","names":[],"sources":["../../src/configs/common.ts"],"sourcesContent":["import { defineConfig } from \"eslint/config\";\n\nimport { GLOBS_CODE } from \"../constants\";\nimport { commonRules } from \"../rules\";\n\n/**\n * 创建跨 JavaScript、TypeScript 与 Vue 脚本生效的通用配置。\n *\n * @remarks\n * 除公共规则外，这里还把无效的 `eslint-disable` 指令提升为错误，避免规则被移除后\n * 留下长期失效的抑制注释。\n *\n * @param files - 应用公共规则的 ESLint glob 列表。\n * @returns 包含公共规则与无效禁用指令检查的 Flat Config 数组。\n */\nexport const createCommonConfigs = (files: readonly string[] = GLOBS_CODE) =>\n\tdefineConfig([\n\t\t{\n\t\t\tname: \"@fast-china/common\",\n\t\t\tfiles: [...files],\n\t\t\tlinterOptions: {\n\t\t\t\treportUnusedDisableDirectives: \"error\",\n\t\t\t},\n\t\t\trules: commonRules,\n\t\t},\n\t]);\n"],"mappings":";;;;;;;;;;;;;;AAeA,MAAa,uBAAuB,QAA2B,eAC9D,aAAa,CACZ;CACC,MAAM;CACN,OAAO,CAAC,GAAG,KAAK;CAChB,eAAe,EACd,+BAA+B,QAChC;CACA,OAAO;AACR,CACD,CAAC"}

package/dist/configs/environment.d.mts

@@ -0,0 +1,73 @@
+import { Linter } from "eslint";
+//#region src/configs/environment.d.ts
+/**
+ * 应用源码可声明的运行时环境。
+ *
+ * - `"browser"` 仅提供浏览器全局变量。
+ * - `"node"` 仅提供 Node.js 全局变量。
+ * - `"universal"` 同时提供浏览器与 Node.js 全局变量。
+ */
+type RuntimeEnvironment = "browser" | "node" | "universal";
+/**
+ * 运行时全局变量配置片段的选项。
+ *
+ * @remarks
+ * `fastConfig()` 会根据已启用的语言和框架计算 `files`、`nodeFiles`，再调用
+ * `createEnvironmentConfigs()`。该接口仍保持独立，以便环境片段的输入、默认值和文件
+ * 范围在源码中具有明确契约；直接组合配置片段时可从 `./configs` 子路径使用。
+ *
+ * 应用代码与 Node.js 工程文件使用两个独立 Flat Config 片段，避免浏览器源码无条件获得
+ * `process`、`Buffer` 等 Node.js 全局变量，也避免配置文件误报这些合法全局变量未定义。
+ */
+interface EnvironmentConfigOptions {
+  /**
+   * 应用代码实际运行的环境，决定 `files` 范围内注入哪组标准全局变量。
+   *
+   * `"browser"` 只注入浏览器全局变量，`"node"` 只注入 Node.js 全局变量，
+   * `"universal"` 同时注入两组。该值不会影响 `nodeFiles` 对应的工程文件；后者始终
+   * 使用 Node.js 全局变量。
+   * @defaultValue `"browser"`
+   */
+  environment?: RuntimeEnvironment;
+  /**
+   * 需要获得所选运行时全局变量的应用代码 glob 列表。
+   *
+   * 工厂会把当前启用的 JavaScript、TypeScript 和 Vue 文件范围传入这里。数组会复制到
+   * 生成配置中，不会在函数内部修改调用方传入的值。
+   * @defaultValue {@link GLOBS_CODE}
+   */
+  files?: readonly string[];
+  /**
+   * 当前启用且允许作为 Node.js 工程文件执行的脚本扩展名 glob 列表。
+   *
+   * 每一项都会与内置的配置文件、脚本目录、测试文件和 CLI 文件模式组合为 ESLint
+   * Flat Config 的 AND 文件条件。例如顶层关闭 TypeScript 后，Node.js 工程片段也不会
+   * 因自身模式较宽而意外接管 `.ts` 文件。
+   * @defaultValue {@link GLOBS_JAVASCRIPT}
+   */
+  nodeFiles?: readonly string[];
+  /**
+   * 追加到应用代码环境中的项目级全局变量及其读写权限。
+   *
+   * 该记录在标准环境全局变量之后合并，所以同名条目可以覆盖预置权限。它应用于完整
+   * `files` 范围；其中属于 Node.js 工程文件的子集还会由后续片段追加标准 Node.js 全局
+   * 变量。值格式遵循 ESLint `Linter.Globals`。
+   * @defaultValue `{}`
+   */
+  globals?: Linter.Globals;
+}
+/**
+ * 创建运行时环境相关的 ESLint 配置。
+ *
+ * @remarks
+ * 返回两个相互独立的 Flat Config 片段：第一个为应用源码配置所选环境和项目级全局
+ * 变量；第二个仅命中配置、脚本、测试与 CLI 等工程文件，为它们配置 Node.js 全局变量
+ * 并允许使用 `console`。分离范围可以减少跨运行时的假阴性。
+ *
+ * @param options - 运行时环境、目标文件范围与项目级全局变量。
+ * @returns 依次包含应用运行时环境和 Node.js 工程文件环境的 Flat Config 数组。
+ */
+declare const createEnvironmentConfigs: ({ environment, files, nodeFiles, globals: projectGlobals }?: EnvironmentConfigOptions) => import("eslint/config").ConfigObject[];
+//#endregion
+export { EnvironmentConfigOptions, RuntimeEnvironment, createEnvironmentConfigs };
+//# sourceMappingURL=environment.d.mts.map