@ts-type/package-dts 1.0.59 → 2.0.2

package/types/eslintrc.json.d.ts

@@ -5,257 +5,77 @@
  * and run json-schema-to-typescript to regenerate this file.
  */
 
+/**
+ * ESLint supports the use of third-party plugins. Before using the plugin, you have to install it using npm.
+ */
+export type Plugins = string[];
+/**
+ * ESLint comes with a large number of rules. You can modify which rules your project uses either using configuration comments or configuration files.
+ */
+export type Rules = PossibleErrors &
+  BestPractices &
+  StrictMode &
+  Variables &
+  NodeAndCommonJs &
+  StylisticIssues &
+  EcmaScript6 &
+  Legacy;
 /**
  * This interface was referenced by `JSONSchemaForESLintConfigurationFiles`'s JSON-Schema
  * via the `definition` "rule".
  */
 export type Rule = number | ("off" | "warn" | "error") | unknown[];
-
-export interface JSONSchemaForESLintConfigurationFiles {
+/**
+ * Allows to override configuration for files and folders, specified by glob patterns
+ */
+export type Overrides = {
   /**
-   * By default, ESLint supports only ECMAScript 5 syntax. You can override that setting to enable support for ECMAScript 6 as well as JSX by using configuration settings.
-   */
-  ecmaFeatures?: {
-    arrowFunctions?: boolean;
-    binaryLiterals?: boolean;
-    blockBindings?: boolean;
-    classes?: boolean;
-    defaultParams?: boolean;
-    destructuring?: boolean;
-    /**
-     * Enables support for the experimental object rest/spread properties (IMPORTANT: This is an experimental feature that may change significantly in the future. It’s recommended that you do not write rules relying on this functionality unless you are willing to incur maintenance cost when it changes.)
-     */
-    experimentalObjectRestSpread?: boolean;
-    forOf?: boolean;
-    generators?: boolean;
-    /**
-     * allow return statements in the global scope
-     */
-    globalReturn?: boolean;
-    /**
-     * enable global strict mode (if ecmaVersion is 5 or greater)
-     */
-    impliedStrict?: boolean;
-    /**
-     * enable JSX
-     */
-    jsx?: boolean;
-    modules?: boolean;
-    objectLiteralComputedProperties?: boolean;
-    objectLiteralDuplicateProperties?: boolean;
-    objectLiteralShorthandMethods?: boolean;
-    objectLiteralShorthandProperties?: boolean;
-    octalLiterals?: boolean;
-    regexUFlag?: boolean;
-    regexYFlag?: boolean;
-    restParams?: boolean;
-    spread?: boolean;
-    superInFunctions?: boolean;
-    templateStrings?: boolean;
-    unicodeCodePointEscapes?: boolean;
-    [k: string]: unknown;
-  };
-  /**
-   * An environment defines global variables that are predefined.
-   */
-  env?: {
-    /**
-     * defines require() and define() as global variables as per the amd spec
-     */
-    amd?: boolean;
-    /**
-     * AppleScript global variables
-     */
-    applescript?: boolean;
-    /**
-     * Atom test helper globals
-     */
-    atomtest?: boolean;
-    /**
-     * browser global variables
-     */
-    browser?: boolean;
-    /**
-     * CommonJS global variables and CommonJS scoping (use this for browser-only code that uses Browserify/WebPack)
-     */
-    commonjs?: boolean;
-    /**
-     * Globals common to both Node and Browser
-     */
-    "shared-node-browser"?: boolean;
-    /**
-     * Ember test helper globals
-     */
-    embertest?: boolean;
-    /**
-     * enable all ECMAScript 6 features except for modules
-     */
-    es6?: boolean;
-    /**
-     * GreaseMonkey globals
-     */
-    greasemonkey?: boolean;
-    /**
-     * adds all of the Jasmine testing global variables for version 1.3 and 2.0
-     */
-    jasmine?: boolean;
-    /**
-     * Jest global variables
-     */
-    jest?: boolean;
-    /**
-     * jQuery global variables
-     */
-    jquery?: boolean;
-    /**
-     * Meteor global variables
-     */
-    meteor?: boolean;
-    /**
-     * adds all of the Mocha test global variables
-     */
-    mocha?: boolean;
-    /**
-     * MongoDB global variables
-     */
-    mongo?: boolean;
-    /**
-     * Java 8 Nashorn global variables
-     */
-    nashorn?: boolean;
-    /**
-     * Node.js global variables and Node.js scoping
-     */
-    node?: boolean;
-    /**
-     * PhantomJS global variables
-     */
-    phantomjs?: boolean;
-    /**
-     * Prototype.js global variables
-     */
-    prototypejs?: boolean;
-    /**
-     * Protractor global variables
-     */
-    protractor?: boolean;
-    /**
-     * QUnit global variables
-     */
-    qunit?: boolean;
-    /**
-     * Service Worker global variables
-     */
-    serviceworker?: boolean;
-    /**
-     * ShellJS global variables
-     */
-    shelljs?: boolean;
-    /**
-     * WebExtensions globals
-     */
-    webextensions?: boolean;
-    /**
-     * web workers global variables
-     */
-    worker?: boolean;
-    [k: string]: unknown;
-  };
+   * Glob pattern for files to apply 'overrides' configuration, relative to the directory of the config file
+   */
+  files: string | [string, ...string[]];
   /**
    * If you want to extend a specific configuration file, you can use the extends property and specify the path to the file. The path can be either relative or absolute.
    */
   extends?: string | string[];
   /**
-   * Set each global variable name equal to true to allow the variable to be overwritten or false to disallow overwriting.
+   * If a file matches any of the 'excludedFiles' glob patterns, the 'overrides' configuration won’t apply
    */
-  globals?: {
-    [k: string]: ("readonly" | "writable" | "off") | boolean;
-  };
+  excludedFiles?: string | string[];
+  ecmaFeatures?: EcmaFeatures;
+  env?: Env;
+  globals?: Globals;
+  parser?: string;
+  parserOptions?: ParserOptions;
+  plugins?: Plugins;
+  /**
+   * To specify a processor, specify the plugin name and processor name joined by a forward slash
+   */
+  processor?: string;
+  rules?: Rules;
+  settings?: Settings;
+  overrides?: Overrides;
+}[];
+/**
+ * This interface was referenced by `JSONSchemaForESLintConfigurationFiles`'s JSON-Schema
+ * via the `definition` "stringOrStringArray".
+ */
+export type StringOrStringArray = string | string[];
+
+export interface JSONSchemaForESLintConfigurationFiles {
+  ecmaFeatures?: EcmaFeatures;
+  env?: Env;
+  /**
+   * If you want to extend a specific configuration file, you can use the extends property and specify the path to the file. The path can be either relative or absolute.
+   */
+  extends?: string | string[];
+  globals?: Globals;
   /**
    * Prevent comments from changing config or rules
    */
   noInlineConfig?: boolean;
   parser?: string;
-  /**
-   * The JavaScript language options to be supported
-   */
-  parserOptions?: {
-    /**
-     * By default, ESLint supports only ECMAScript 5 syntax. You can override that setting to enable support for ECMAScript 6 as well as JSX by using configuration settings.
-     */
-    ecmaFeatures?: {
-      arrowFunctions?: boolean;
-      binaryLiterals?: boolean;
-      blockBindings?: boolean;
-      classes?: boolean;
-      defaultParams?: boolean;
-      destructuring?: boolean;
-      /**
-       * Enables support for the experimental object rest/spread properties (IMPORTANT: This is an experimental feature that may change significantly in the future. It’s recommended that you do not write rules relying on this functionality unless you are willing to incur maintenance cost when it changes.)
-       */
-      experimentalObjectRestSpread?: boolean;
-      forOf?: boolean;
-      generators?: boolean;
-      /**
-       * allow return statements in the global scope
-       */
-      globalReturn?: boolean;
-      /**
-       * enable global strict mode (if ecmaVersion is 5 or greater)
-       */
-      impliedStrict?: boolean;
-      /**
-       * enable JSX
-       */
-      jsx?: boolean;
-      modules?: boolean;
-      objectLiteralComputedProperties?: boolean;
-      objectLiteralDuplicateProperties?: boolean;
-      objectLiteralShorthandMethods?: boolean;
-      objectLiteralShorthandProperties?: boolean;
-      octalLiterals?: boolean;
-      regexUFlag?: boolean;
-      regexYFlag?: boolean;
-      restParams?: boolean;
-      spread?: boolean;
-      superInFunctions?: boolean;
-      templateStrings?: boolean;
-      unicodeCodePointEscapes?: boolean;
-      [k: string]: unknown;
-    };
-    /**
-     * Set to 3, 5, 6, 7, 8, 9, 10, 11 (default), 12, 13 or "latest" to specify the version of ECMAScript syntax you want to use. You can also set to 2015 (same as 6), 2016 (same as 7), 2017 (same as 8), 2018 (same as 9), 2019 (same as 10), 2020 (same as 11) or 2021 (same as 12) or 2022 (same as 13) to use the year-based naming. "latest" always enables the latest supported ECMAScript version.
-     */
-    ecmaVersion?:
-      | 3
-      | 5
-      | 6
-      | 2015
-      | 7
-      | 2016
-      | 8
-      | 2017
-      | 9
-      | 2018
-      | 10
-      | 2019
-      | 11
-      | 2020
-      | 12
-      | 2021
-      | 13
-      | 2022
-      | "latest";
-    /**
-     * set to "script" (default) or "module" if your code is in ECMAScript modules
-     */
-    sourceType?: "script" | "module";
-    [k: string]: unknown;
-  };
-  /**
-   * ESLint supports the use of third-party plugins. Before using the plugin, you have to install it using npm.
-   */
-  plugins?: string[];
+  parserOptions?: ParserOptions;
+  plugins?: Plugins;
   /**
    * By default, ESLint will look for configuration files in all parent folders up to the root directory. This can be useful if you want all of your projects to follow a certain convention, but can sometimes lead to unexpected results. To limit ESLint to a specific project, set this to `true` in a configuration in the root of your project.
    */
@@ -264,297 +84,198 @@ export interface JSONSchemaForESLintConfigurationFiles {
    * Tell ESLint to ignore specific files and directories. Each value uses the same pattern as the `.eslintignore` file.
    */
   ignorePatterns?: string | string[];
+  rules?: Rules;
+  settings?: Settings;
+  overrides?: Overrides;
+  [k: string]: unknown;
+}
+/**
+ * By default, ESLint supports only ECMAScript 5 syntax. You can override that setting to enable support for ECMAScript 6 as well as JSX by using configuration settings.
+ */
+export interface EcmaFeatures {
+  arrowFunctions?: boolean;
+  binaryLiterals?: boolean;
+  blockBindings?: boolean;
+  classes?: boolean;
+  defaultParams?: boolean;
+  destructuring?: boolean;
+  /**
+   * Enables support for the experimental object rest/spread properties (IMPORTANT: This is an experimental feature that may change significantly in the future. It’s recommended that you do not write rules relying on this functionality unless you are willing to incur maintenance cost when it changes.)
+   */
+  experimentalObjectRestSpread?: boolean;
+  forOf?: boolean;
+  generators?: boolean;
+  /**
+   * allow return statements in the global scope
+   */
+  globalReturn?: boolean;
+  /**
+   * enable global strict mode (if ecmaVersion is 5 or greater)
+   */
+  impliedStrict?: boolean;
+  /**
+   * enable JSX
+   */
+  jsx?: boolean;
+  modules?: boolean;
+  objectLiteralComputedProperties?: boolean;
+  objectLiteralDuplicateProperties?: boolean;
+  objectLiteralShorthandMethods?: boolean;
+  objectLiteralShorthandProperties?: boolean;
+  octalLiterals?: boolean;
+  regexUFlag?: boolean;
+  regexYFlag?: boolean;
+  restParams?: boolean;
+  spread?: boolean;
+  superInFunctions?: boolean;
+  templateStrings?: boolean;
+  unicodeCodePointEscapes?: boolean;
+  [k: string]: unknown;
+}
+/**
+ * An environment defines global variables that are predefined.
+ */
+export interface Env {
+  /**
+   * defines require() and define() as global variables as per the amd spec
+   */
+  amd?: boolean;
+  /**
+   * AppleScript global variables
+   */
+  applescript?: boolean;
+  /**
+   * Atom test helper globals
+   */
+  atomtest?: boolean;
+  /**
+   * browser global variables
+   */
+  browser?: boolean;
+  /**
+   * CommonJS global variables and CommonJS scoping (use this for browser-only code that uses Browserify/WebPack)
+   */
+  commonjs?: boolean;
+  /**
+   * Globals common to both Node and Browser
+   */
+  "shared-node-browser"?: boolean;
+  /**
+   * Ember test helper globals
+   */
+  embertest?: boolean;
+  /**
+   * enable all ECMAScript 6 features except for modules
+   */
+  es6?: boolean;
+  /**
+   * GreaseMonkey globals
+   */
+  greasemonkey?: boolean;
+  /**
+   * adds all of the Jasmine testing global variables for version 1.3 and 2.0
+   */
+  jasmine?: boolean;
+  /**
+   * Jest global variables
+   */
+  jest?: boolean;
+  /**
+   * jQuery global variables
+   */
+  jquery?: boolean;
+  /**
+   * Meteor global variables
+   */
+  meteor?: boolean;
+  /**
+   * adds all of the Mocha test global variables
+   */
+  mocha?: boolean;
+  /**
+   * MongoDB global variables
+   */
+  mongo?: boolean;
+  /**
+   * Java 8 Nashorn global variables
+   */
+  nashorn?: boolean;
+  /**
+   * Node.js global variables and Node.js scoping
+   */
+  node?: boolean;
+  /**
+   * PhantomJS global variables
+   */
+  phantomjs?: boolean;
+  /**
+   * Prototype.js global variables
+   */
+  prototypejs?: boolean;
   /**
-   * ESLint comes with a large number of rules. You can modify which rules your project uses either using configuration comments or configuration files.
-   */
-  rules?: PossibleErrors &
-    BestPractices &
-    StrictMode &
-    Variables &
-    NodeAndCommonJs &
-    StylisticIssues &
-    EcmaScript6 &
-    Legacy;
-  /**
-   * ESLint supports adding shared settings into configuration file. You can add settings object to ESLint configuration file and it will be supplied to every rule that will be executed. This may be useful if you are adding custom rules and want them to have access to the same information and be easily configurable.
-   */
-  settings?: {
-    [k: string]: unknown;
-  };
-  /**
-   * Allows to override configuration for files and folders, specified by glob patterns
-   */
-  overrides?: {
-    /**
-     * Glob pattern for files to apply 'overrides' configuration, relative to the directory of the config file
-     */
-    files: string | [string, ...string[]];
-    /**
-     * If you want to extend a specific configuration file, you can use the extends property and specify the path to the file. The path can be either relative or absolute.
-     */
-    extends?: string | string[];
-    /**
-     * If a file matches any of the 'excludedFiles' glob patterns, the 'overrides' configuration won’t apply
-     */
-    excludedFiles?: string | string[];
-    /**
-     * By default, ESLint supports only ECMAScript 5 syntax. You can override that setting to enable support for ECMAScript 6 as well as JSX by using configuration settings.
-     */
-    ecmaFeatures?: {
-      arrowFunctions?: boolean;
-      binaryLiterals?: boolean;
-      blockBindings?: boolean;
-      classes?: boolean;
-      defaultParams?: boolean;
-      destructuring?: boolean;
-      /**
-       * Enables support for the experimental object rest/spread properties (IMPORTANT: This is an experimental feature that may change significantly in the future. It’s recommended that you do not write rules relying on this functionality unless you are willing to incur maintenance cost when it changes.)
-       */
-      experimentalObjectRestSpread?: boolean;
-      forOf?: boolean;
-      generators?: boolean;
-      /**
-       * allow return statements in the global scope
-       */
-      globalReturn?: boolean;
-      /**
-       * enable global strict mode (if ecmaVersion is 5 or greater)
-       */
-      impliedStrict?: boolean;
-      /**
-       * enable JSX
-       */
-      jsx?: boolean;
-      modules?: boolean;
-      objectLiteralComputedProperties?: boolean;
-      objectLiteralDuplicateProperties?: boolean;
-      objectLiteralShorthandMethods?: boolean;
-      objectLiteralShorthandProperties?: boolean;
-      octalLiterals?: boolean;
-      regexUFlag?: boolean;
-      regexYFlag?: boolean;
-      restParams?: boolean;
-      spread?: boolean;
-      superInFunctions?: boolean;
-      templateStrings?: boolean;
-      unicodeCodePointEscapes?: boolean;
-      [k: string]: unknown;
-    };
-    /**
-     * An environment defines global variables that are predefined.
-     */
-    env?: {
-      /**
-       * defines require() and define() as global variables as per the amd spec
-       */
-      amd?: boolean;
-      /**
-       * AppleScript global variables
-       */
-      applescript?: boolean;
-      /**
-       * Atom test helper globals
-       */
-      atomtest?: boolean;
-      /**
-       * browser global variables
-       */
-      browser?: boolean;
-      /**
-       * CommonJS global variables and CommonJS scoping (use this for browser-only code that uses Browserify/WebPack)
-       */
-      commonjs?: boolean;
-      /**
-       * Globals common to both Node and Browser
-       */
-      "shared-node-browser"?: boolean;
-      /**
-       * Ember test helper globals
-       */
-      embertest?: boolean;
-      /**
-       * enable all ECMAScript 6 features except for modules
-       */
-      es6?: boolean;
-      /**
-       * GreaseMonkey globals
-       */
-      greasemonkey?: boolean;
-      /**
-       * adds all of the Jasmine testing global variables for version 1.3 and 2.0
-       */
-      jasmine?: boolean;
-      /**
-       * Jest global variables
-       */
-      jest?: boolean;
-      /**
-       * jQuery global variables
-       */
-      jquery?: boolean;
-      /**
-       * Meteor global variables
-       */
-      meteor?: boolean;
-      /**
-       * adds all of the Mocha test global variables
-       */
-      mocha?: boolean;
-      /**
-       * MongoDB global variables
-       */
-      mongo?: boolean;
-      /**
-       * Java 8 Nashorn global variables
-       */
-      nashorn?: boolean;
-      /**
-       * Node.js global variables and Node.js scoping
-       */
-      node?: boolean;
-      /**
-       * PhantomJS global variables
-       */
-      phantomjs?: boolean;
-      /**
-       * Prototype.js global variables
-       */
-      prototypejs?: boolean;
-      /**
-       * Protractor global variables
-       */
-      protractor?: boolean;
-      /**
-       * QUnit global variables
-       */
-      qunit?: boolean;
-      /**
-       * Service Worker global variables
-       */
-      serviceworker?: boolean;
-      /**
-       * ShellJS global variables
-       */
-      shelljs?: boolean;
-      /**
-       * WebExtensions globals
-       */
-      webextensions?: boolean;
-      /**
-       * web workers global variables
-       */
-      worker?: boolean;
-      [k: string]: unknown;
-    };
-    /**
-     * Set each global variable name equal to true to allow the variable to be overwritten or false to disallow overwriting.
-     */
-    globals?: {
-      [k: string]: ("readonly" | "writable" | "off") | boolean;
-    };
-    parser?: string;
-    /**
-     * The JavaScript language options to be supported
-     */
-    parserOptions?: {
-      /**
-       * By default, ESLint supports only ECMAScript 5 syntax. You can override that setting to enable support for ECMAScript 6 as well as JSX by using configuration settings.
-       */
-      ecmaFeatures?: {
-        arrowFunctions?: boolean;
-        binaryLiterals?: boolean;
-        blockBindings?: boolean;
-        classes?: boolean;
-        defaultParams?: boolean;
-        destructuring?: boolean;
-        /**
-         * Enables support for the experimental object rest/spread properties (IMPORTANT: This is an experimental feature that may change significantly in the future. It’s recommended that you do not write rules relying on this functionality unless you are willing to incur maintenance cost when it changes.)
-         */
-        experimentalObjectRestSpread?: boolean;
-        forOf?: boolean;
-        generators?: boolean;
-        /**
-         * allow return statements in the global scope
-         */
-        globalReturn?: boolean;
-        /**
-         * enable global strict mode (if ecmaVersion is 5 or greater)
-         */
-        impliedStrict?: boolean;
-        /**
-         * enable JSX
-         */
-        jsx?: boolean;
-        modules?: boolean;
-        objectLiteralComputedProperties?: boolean;
-        objectLiteralDuplicateProperties?: boolean;
-        objectLiteralShorthandMethods?: boolean;
-        objectLiteralShorthandProperties?: boolean;
-        octalLiterals?: boolean;
-        regexUFlag?: boolean;
-        regexYFlag?: boolean;
-        restParams?: boolean;
-        spread?: boolean;
-        superInFunctions?: boolean;
-        templateStrings?: boolean;
-        unicodeCodePointEscapes?: boolean;
-        [k: string]: unknown;
-      };
-      /**
-       * Set to 3, 5, 6, 7, 8, 9, 10, 11 (default), 12, 13 or "latest" to specify the version of ECMAScript syntax you want to use. You can also set to 2015 (same as 6), 2016 (same as 7), 2017 (same as 8), 2018 (same as 9), 2019 (same as 10), 2020 (same as 11) or 2021 (same as 12) or 2022 (same as 13) to use the year-based naming. "latest" always enables the latest supported ECMAScript version.
-       */
-      ecmaVersion?:
-        | 3
-        | 5
-        | 6
-        | 2015
-        | 7
-        | 2016
-        | 8
-        | 2017
-        | 9
-        | 2018
-        | 10
-        | 2019
-        | 11
-        | 2020
-        | 12
-        | 2021
-        | 13
-        | 2022
-        | "latest";
-      /**
-       * set to "script" (default) or "module" if your code is in ECMAScript modules
-       */
-      sourceType?: "script" | "module";
-      [k: string]: unknown;
-    };
-    /**
-     * ESLint supports the use of third-party plugins. Before using the plugin, you have to install it using npm.
-     */
-    plugins?: string[];
-    /**
-     * To specify a processor, specify the plugin name and processor name joined by a forward slash
-     */
-    processor?: string;
-    /**
-     * ESLint comes with a large number of rules. You can modify which rules your project uses either using configuration comments or configuration files.
-     */
-    rules?: PossibleErrors &
-      BestPractices &
-      StrictMode &
-      Variables &
-      NodeAndCommonJs &
-      StylisticIssues &
-      EcmaScript6 &
-      Legacy;
-    /**
-     * ESLint supports adding shared settings into configuration file. You can add settings object to ESLint configuration file and it will be supplied to every rule that will be executed. This may be useful if you are adding custom rules and want them to have access to the same information and be easily configurable.
-     */
-    settings?: {
-      [k: string]: unknown;
-    };
-  }[];
+   * Protractor global variables
+   */
+  protractor?: boolean;
+  /**
+   * QUnit global variables
+   */
+  qunit?: boolean;
+  /**
+   * Service Worker global variables
+   */
+  serviceworker?: boolean;
+  /**
+   * ShellJS global variables
+   */
+  shelljs?: boolean;
+  /**
+   * WebExtensions globals
+   */
+  webextensions?: boolean;
+  /**
+   * web workers global variables
+   */
+  worker?: boolean;
+  [k: string]: unknown;
+}
+/**
+ * Set each global variable name equal to true to allow the variable to be overwritten or false to disallow overwriting.
+ */
+export interface Globals {
+  [k: string]: ("readonly" | "writable" | "off") | boolean;
+}
+/**
+ * The JavaScript language options to be supported
+ */
+export interface ParserOptions {
+  ecmaFeatures?: EcmaFeatures;
+  /**
+   * Set to 3, 5, 6, 7, 8, 9, 10, 11 (default), 12, 13 or "latest" to specify the version of ECMAScript syntax you want to use. You can also set to 2015 (same as 6), 2016 (same as 7), 2017 (same as 8), 2018 (same as 9), 2019 (same as 10), 2020 (same as 11) or 2021 (same as 12) or 2022 (same as 13) to use the year-based naming. "latest" always enables the latest supported ECMAScript version.
+   */
+  ecmaVersion?:
+    | 3
+    | 5
+    | 6
+    | 2015
+    | 7
+    | 2016
+    | 8
+    | 2017
+    | 9
+    | 2018
+    | 10
+    | 2019
+    | 11
+    | 2020
+    | 12
+    | 2021
+    | 13
+    | 2022
+    | "latest";
+  /**
+   * set to "script" (default) or "module" if your code is in ECMAScript modules
+   */
+  sourceType?: "script" | "module";
   [k: string]: unknown;
 }
 /**
@@ -1650,3 +1371,9 @@ export interface Legacy {
   "no-plusplus"?: Rule;
   [k: string]: unknown;
 }
+/**
+ * ESLint supports adding shared settings into configuration file. You can add settings object to ESLint configuration file and it will be supplied to every rule that will be executed. This may be useful if you are adding custom rules and want them to have access to the same information and be easily configurable.
+ */
+export interface Settings {
+  [k: string]: unknown;
+}