@hey-api/openapi-ts 0.77.0 → 0.78.0

package/dist/{types.d-CBVwu8Hi.d.cts → types.d-BsTxgeRq.d.cts}

@@ -2639,6 +2639,205 @@ interface EnsureUniqueIdentifierData {
     namespace: Namespace;
 }
 
+type ObjectType<T> = Extract<T, Record<string, any>> extends never ? Record<string, any> : Extract<T, Record<string, any>>;
+type ValueToObject = <T extends undefined | string | boolean | number | Record<string, any>>(args: {
+    defaultValue: ObjectType<T>;
+    mappers: {
+        boolean: T extends boolean ? (value: boolean) => Partial<ObjectType<T>> : never;
+        number: T extends number ? (value: number) => Partial<ObjectType<T>> : never;
+        object?: (value: Partial<ObjectType<T>>) => Partial<ObjectType<T>>;
+        string: T extends string ? (value: string) => Partial<ObjectType<T>> : never;
+    } extends infer U ? {
+        [K in keyof U as U[K] extends never ? never : K]: U[K];
+    } : never;
+    value: T;
+}) => ObjectType<T>;
+
+type Input = {
+  /**
+   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
+   *
+   * Projects are private by default, you will need to be authenticated
+   * to download OpenAPI specifications. We recommend using project API
+   * keys in CI workflows and personal API keys for local development.
+   *
+   * API key isn't required for public projects. You can also omit this
+   * parameter and provide an environment variable `HEY_API_TOKEN`.
+   */
+  api_key?: string;
+  /**
+   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
+   *
+   * You can fetch the last build from branch by providing the branch
+   * name.
+   */
+  branch?: string;
+  /**
+   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
+   *
+   * You can fetch an exact specification by providing a commit sha.
+   * This will always return the same file.
+   */
+  commit_sha?: string;
+  /**
+   * You can pass any valid Fetch API options to the request for fetching your
+   * specification. This is useful if your file is behind auth for example.
+   */
+  fetch?: RequestInit;
+  /**
+   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
+   *
+   * Organization created in Hey API Platform.
+   */
+  organization?: string;
+  /**
+   * Path to the OpenAPI specification. This can be either local or remote path.
+   * Both JSON and YAML file formats are supported. You can also pass the parsed
+   * object directly if you're fetching the file yourself.
+   */
+  path?:
+    | 'https://get.heyapi.dev/<organization>/<project>'
+    | (string & {})
+    | Record<string, unknown>;
+  /**
+   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
+   *
+   * Project created in Hey API Platform.
+   */
+  project?: string;
+  /**
+   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
+   *
+   * If you're tagging your specifications with custom tags, you can use
+   * them to filter the results. When you provide multiple tags, only
+   * the first match will be returned.
+   */
+  tags?: ReadonlyArray<string>;
+  /**
+   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
+   *
+   * Every OpenAPI document contains a required version field. You can
+   * use this value to fetch the last uploaded specification matching
+   * the value.
+   */
+  version?: string;
+  /**
+   * Regenerate the client when the input file changes? You can alternatively
+   * pass a numeric value for the interval in ms.
+   *
+   * @default false
+   */
+  watch?: boolean | number | Watch;
+};
+
+type Watch = {
+  /**
+   * Regenerate the client when the input file changes?
+   *
+   * @default false
+   */
+  enabled?: boolean;
+  /**
+   * How often should we attempt to detect the input file change? (in ms)
+   *
+   * @default 1000
+   */
+  interval?: number;
+  /**
+   * How long will we wait before the request times out?
+   *
+   * @default 60_000
+   */
+  timeout?: number;
+};
+
+type Logs = {
+  /**
+   * Whether or not error logs should be written to a file or not
+   *
+   * @default true
+   * */
+  file?: boolean;
+  /**
+   * The logging level to control the verbosity of log output.
+   * Determines which messages are logged based on their severity.
+   *
+   * Available levels (in increasing order of severity):
+   * - `trace`: Detailed debug information, primarily for development.
+   * - `debug`: Diagnostic information useful during debugging.
+   * - `info`: General operational messages that indicate normal application behavior.
+   * - `warn`: Potentially problematic situations that require attention.
+   * - `error`: Errors that prevent some functionality but do not crash the application.
+   * - `fatal`: Critical errors that cause the application to terminate.
+   * - `silent`: Disables all logging.
+   *
+   * Messages with a severity equal to or higher than the specified level will be logged.
+   *
+   * @default 'info'
+   */
+  level?: 'debug' | 'error' | 'fatal' | 'info' | 'silent' | 'trace' | 'warn';
+  /**
+   * The relative location of the logs folder
+   *
+   * @default process.cwd()
+   */
+  path?: string;
+};
+
+type Formatters = 'biome' | 'prettier';
+
+type Linters = 'biome' | 'eslint' | 'oxlint';
+
+type Output = {
+  /**
+   * Defines casing of the output fields. By default, we preserve `input`
+   * values as data transforms incur a performance penalty at runtime.
+   *
+   * @default undefined
+   */
+  case?: Exclude<StringCase, 'SCREAMING_SNAKE_CASE'>;
+  /**
+   * Clean the `output` folder on every run? If disabled, this folder may
+   * be used to store additional files. The default option is `true` to
+   * reduce the risk of keeping outdated files around when configuration,
+   * input, or package version changes.
+   *
+   * @default true
+   */
+  clean?: boolean;
+  /**
+   * Process output folder with formatter?
+   *
+   * @default false
+   */
+  format?: Formatters | false;
+  /**
+   * Should the exports from plugin files be re-exported in the index
+   * barrel file? By default, this is enabled and only default plugins
+   * are re-exported.
+   *
+   * @default true
+   */
+  indexFile?: boolean;
+  /**
+   * Process output folder with linter?
+   *
+   * @default false
+   */
+  lint?: Linters | false;
+  /**
+   * The relative location of the output folder
+   */
+  path: string;
+  /**
+   * Relative or absolute path to the tsconfig file we should use to
+   * generate the output. If a path to tsconfig file is not provided, we
+   * attempt to find one starting from the location of the
+   * `@hey-api/openapi-ts` configuration file and traversing up.
+   */
+  tsConfigPath?: 'off' | (string & {});
+};
+
 interface JsonSchemaDraft4 extends EnumExtensions {
   /**
    * A schema can reference another schema using the `$ref` keyword. The value of `$ref` is a URI-reference that is resolved against the schema's {@link https://json-schema.org/understanding-json-schema/structuring#base-uri Base URI}. When evaluating a `$ref`, an implementation uses the resolved identifier to retrieve the referenced schema and applies that schema to the {@link https://json-schema.org/learn/glossary#instance instance}.
@@ -4396,6 +4595,7 @@ interface XMLObject$1 {
 
 interface OpenApiV2_0_XTypes {
     InfoObject: InfoObject$1;
+    OperationObject: OperationObject$1;
     SchemaObject: SchemaObject$1;
 }
 
@@ -5682,6 +5882,7 @@ type Format = JsonSchemaFormats | OpenApiSchemaFormats | (string & {});
 
 interface OpenApiV3_0_XTypes {
     InfoObject: InfoObject;
+    OperationObject: OperationObject;
     ParameterObject: ParameterObject;
     ReferenceObject: ReferenceObject;
     RequestBodyObject: RequestBodyObject;
@@ -5691,6 +5892,7 @@ interface OpenApiV3_0_XTypes {
 
 interface OpenApiV3_1_XTypes {
     InfoObject: InfoObject$2;
+    OperationObject: OperationObject$2;
     ParameterObject: ParameterObject$2;
     ReferenceObject: ReferenceObject$2;
     RequestBodyObject: RequestBodyObject$1;
@@ -5714,6 +5916,14 @@ declare namespace OpenApiMetaObject {
   export type V3_1_X = OpenApiV3_1_XTypes['InfoObject'];
 }
 
+declare namespace OpenApiOperationObject {
+  export type V2_0_X = OpenApiV2_0_XTypes['OperationObject'];
+
+  export type V3_0_X = OpenApiV3_0_XTypes['OperationObject'];
+
+  export type V3_1_X = OpenApiV3_1_XTypes['OperationObject'];
+}
+
 declare namespace OpenApiParameterObject {
   export type V3_0_X =
     | OpenApiV3_0_XTypes['ParameterObject']
@@ -5752,48 +5962,14 @@ declare namespace OpenApiSchemaObject {
   export type V3_1_X = OpenApiV3_1_XTypes['SchemaObject'];
 }
 
-interface Input {
-  /**
-   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
-   *
-   * Projects are private by default, you will need to be authenticated
-   * to download OpenAPI specifications. We recommend using project API
-   * keys in CI workflows and personal API keys for local development.
-   *
-   * API key isn't required for public projects. You can also omit this
-   * parameter and provide an environment variable `HEY_API_TOKEN`.
-   */
-  api_key?: string;
-  /**
-   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
-   *
-   * You can fetch the last build from branch by providing the branch
-   * name.
-   */
-  branch?: string;
-  /**
-   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
-   *
-   * You can fetch an exact specification by providing a commit sha.
-   * This will always return the same file.
-   */
-  commit_sha?: string;
-  /**
-   * You pass any valid Fetch API options to the request for fetching your
-   * specification. This is useful if your file is behind auth for example.
-   */
-  fetch?: RequestInit;
+type EnumsMode = 'inline' | 'root';
+
+type Parser = {
   /**
-   * Filters can be used to select a subset of your input before it's processed
-   * by plugins.
+   * Filters can be used to select a subset of your input before it's passed
+   * to plugins.
    */
   filters?: Filters;
-  /**
-   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
-   *
-   * Organization created in Hey API platform.
-   */
-  organization?: string;
   /**
    * Pagination configuration.
    */
@@ -5807,33 +5983,129 @@ interface Input {
     keywords?: ReadonlyArray<string>;
   };
   /**
-   * Custom input transformations to execute before parsing. This allows you
-   * to modify, fix, or enhance input definitions before code generation.
+   * Custom input transformations to execute before parsing. Use this
+   * to modify, fix, or enhance input before it's passed to plugins.
    */
   patch?: Patch;
   /**
-   * Path to the OpenAPI specification. This can be either local or remote path.
-   * Both JSON and YAML file formats are supported. You can also pass the parsed
-   * object directly if you're fetching the file yourself.
-   */
-  path?:
-    | 'https://get.heyapi.dev/<organization>/<project>'
-    | (string & {})
-    | Record<string, unknown>;
-  /**
-   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
-   *
-   * Project created in Hey API platform.
-   */
-  project?: string;
-  /**
-   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
-   *
-   * If you're tagging your specifications with custom tags, you can use
-   * them to filter the results. When you provide multiple tags, only
-   * the first match will be returned.
+   * Built-in transformations that modify or normalize the input before it's
+   * passed to plugins. These options enable predictable, documented behaviors
+   * and are distinct from custom patches. Use this to perform structural
+   * changes to input in a standardized way.
    */
-  tags?: ReadonlyArray<string>;
+  transforms?: {
+    /**
+     * Your input might contain two types of enums:
+     * - enums defined as reusable components (root enums)
+     * - non-reusable enums nested within other schemas (inline enums)
+     *
+     * You may want all enums to be reusable. This is because only root enums
+     * are typically exported by plugins. Inline enums will never be directly
+     * importable since they're nested inside other schemas.
+     *
+     * For example, to export nested enum types with the `@hey-api/typescript`
+     * plugin, set `enums` to `root`. Likewise, if you don't want to export any
+     * enum types, set `enums` to `inline`.
+     *
+     * @default false
+     */
+    enums?:
+      | boolean
+      | EnumsMode
+      | {
+          /**
+           * The casing convention to use for generated names.
+           *
+           * @default 'PascalCase'
+           */
+          case?: StringCase;
+          /**
+           * Whether to transform all enums.
+           *
+           * @default true
+           */
+          enabled?: boolean;
+          /**
+           * Controls whether enums are promoted to reusable root components
+           * ('root') or kept inline within schemas ('inline').
+           *
+           * @default 'root'
+           */
+          mode?: EnumsMode;
+          /**
+           * Customize the generated name of enums.
+           *
+           * @default '{{name}}Enum'
+           */
+          name?: string | ((name: string) => string);
+        };
+    /**
+     * Your schemas might contain read-only or write-only fields. Using such
+     * schemas directly could mean asking the user to provide a read-only
+     * field in requests, or expecting a write-only field in responses.
+     *
+     * We separate schemas for requests and responses if direct usage
+     * would result in such scenarios. You can still disable this
+     * behavior if you prefer.
+     *
+     * @default true
+     */
+    readWrite?:
+      | boolean
+      | {
+          /**
+           * Whether to split read-only and write-only schemas.
+           *
+           * @default true
+           */
+          enabled?: boolean;
+          /**
+           * Configuration for generated request-specific schemas.
+           *
+           * @default '{{name}}Writable'
+           */
+          requests?:
+            | string
+            | {
+                /**
+                 * The casing convention to use for generated names.
+                 *
+                 * @default 'preserve'
+                 */
+                case?: StringCase;
+                /**
+                 * Customize the generated name of schemas used in requests or
+                 * containing write-only fields.
+                 *
+                 * @default '{{name}}Writable'
+                 */
+                name?: string | ((name: string) => string);
+              };
+          /**
+           * Configuration for generated response-specific schemas.
+           *
+           * @default '{{name}}'
+           */
+          responses?:
+            | string
+            | {
+                /**
+                 * The casing convention to use for generated names.
+                 *
+                 * @default 'preserve'
+                 */
+                case?: StringCase;
+                /**
+                 * Customize the generated name of schemas used in responses or
+                 * containing read-only fields. We default to the original name
+                 * to avoid breaking output when a read-only field is added.
+                 *
+                 * @default '{{name}}'
+                 */
+                name?: string | ((name: string) => string);
+              };
+        };
+  };
   /**
    * **This is an experimental feature.**
    *
@@ -5844,24 +6116,146 @@ interface Input {
    * @default false
    */
   validate_EXPERIMENTAL?: boolean | 'strict' | 'warn';
+};
+
+type ResolvedParser = {
   /**
-   * **Requires `path` to start with `https://get.heyapi.dev` or be undefined**
-   *
-   * Every OpenAPI document contains a required version field. You can
-   * use this value to fetch the last uploaded specification matching
-   * the value.
+   * Filters can be used to select a subset of your input before it's passed
+   * to plugins.
    */
-  version?: string;
+  filters?: Filters;
   /**
-   * Regenerate the client when the input file changes? You can alternatively
-   * pass a numeric value for the interval in ms.
+   * Pagination configuration.
+   */
+  pagination: {
+    /**
+     * Array of keywords to be considered as pagination field names.
+     * These will be used to detect pagination fields in schemas and parameters.
+     *
+     * @default ['after', 'before', 'cursor', 'offset', 'page', 'start']
+     */
+    keywords: ReadonlyArray<string>;
+  };
+  /**
+   * Custom input transformations to execute before parsing. Use this
+   * to modify, fix, or enhance input before it's passed to plugins.
+   */
+  patch?: Patch;
+  /**
+   * Built-in transformations that modify or normalize the input before it's
+   * passed to plugins. These options enable predictable, documented behaviors
+   * and are distinct from custom patches. Use this to perform structural
+   * changes to input in a standardized way.
+   */
+  transforms: {
+    /**
+     * Your input might contain two types of enums:
+     * - enums defined as reusable components (root enums)
+     * - non-reusable enums nested within other schemas (inline enums)
+     *
+     * You may want all enums to be reusable. This is because only root enums
+     * are typically exported by plugins. Inline enums will never be directly
+     * importable since they're nested inside other schemas.
+     *
+     * For example, to export nested enum types with the `@hey-api/typescript`
+     * plugin, set `enums` to `root`. Likewise, if you don't want to export any
+     * enum types, set `enums` to `inline`.
+     */
+    enums: {
+      /**
+       * The casing convention to use for generated names.
+       *
+       * @default 'PascalCase'
+       */
+      case: StringCase;
+      /**
+       * Whether to transform all enums.
+       *
+       * @default true
+       */
+      enabled: boolean;
+      /**
+       * Controls whether enums are promoted to reusable root components
+       * ('root') or kept inline within schemas ('inline').
+       *
+       * @default 'root'
+       */
+      mode: EnumsMode;
+      /**
+       * Customize the generated name of enums.
+       *
+       * @default '{{name}}Enum'
+       */
+      name: string | ((name: string) => string);
+    };
+    /**
+     * Your schemas might contain read-only or write-only fields. Using such
+     * schemas directly could mean asking the user to provide a read-only
+     * field in requests, or expecting a write-only field in responses.
+     *
+     * We separate schemas for requests and responses if direct usage
+     * would result in such scenarios. You can still disable this
+     * behavior if you prefer.
+     */
+    readWrite: {
+      /**
+       * Whether to split read-only and write-only schemas.
+       *
+       * @default true
+       */
+      enabled: boolean;
+      /**
+       * Configuration for generated request-specific schemas.
+       */
+      requests: {
+        /**
+         * The casing convention to use for generated names.
+         *
+         * @default 'preserve'
+         */
+        case: StringCase;
+        /**
+         * Customize the generated name of schemas used in requests or
+         * containing write-only fields.
+         *
+         * @default '{{name}}Writable'
+         */
+        name: string | ((name: string) => string);
+      };
+      /**
+       * Configuration for generated response-specific schemas.
+       */
+      responses: {
+        /**
+         * The casing convention to use for generated names.
+         *
+         * @default 'preserve'
+         */
+        case: StringCase;
+        /**
+         * Customize the generated name of schemas used in responses or
+         * containing read-only fields. We default to the original name
+         * to avoid breaking output when a read-only field is added.
+         *
+         * @default '{{name}}'
+         */
+        name: string | ((name: string) => string);
+      };
+    };
+  };
+  /**
+   * **This is an experimental feature.**
+   *
+   * Validate the input before generating output? This is an experimental,
+   * lightweight feature and support will be added on an ad hoc basis. Setting
+   * `validate_EXPERIMENTAL` to `true` is the same as `warn`.
    *
    * @default false
    */
-  watch?: boolean | number | Watch;
-}
+  validate_EXPERIMENTAL: false | 'strict' | 'warn';
+};
 
-interface Filters {
+type Filters = {
   /**
    * Include deprecated resources in the output?
    *
@@ -5990,9 +6384,9 @@ interface Filters {
      */
     include?: ReadonlyArray<string>;
   };
-}
+};
 
-interface Patch {
+type Patch = {
   /**
    * Patch the OpenAPI meta object in place. Useful for modifying general metadata such as title, description, version, or custom fields before further processing.
    *
@@ -6004,6 +6398,25 @@ interface Patch {
       | OpenApiMetaObject.V3_0_X
       | OpenApiMetaObject.V3_1_X,
   ) => void;
+  /**
+   * Patch OpenAPI operations in place. The key is the operation method and operation path, and the function receives the operation object to modify directly.
+   *
+   * @example
+   * operations: {
+   *   'GET /foo': (operation) => {
+   *     operation.responses['200'].description = 'foo';
+   *   }
+   * }
+   */
+  operations?: Record<
+    string,
+    (
+      operation:
+        | OpenApiOperationObject.V2_0_X
+        | OpenApiOperationObject.V3_0_X
+        | OpenApiOperationObject.V3_1_X,
+    ) => void
+  >;
   /**
    * Patch OpenAPI parameters in place. The key is the parameter name, and the function receives the parameter object to modify directly.
    *
@@ -6101,33 +6514,8 @@ interface Patch {
    * @example
    * version: (version) => version.replace(/^v/, '')
    */
-  version?: (version: string) => string;
-}
-
-interface Watch {
-  /**
-   * Regenerate the client when the input file changes?
-   *
-   * @default false
-   */
-  enabled?: boolean;
-  /**
-   * How often should we attempt to detect the input file change? (in ms)
-   *
-   * @default 1000
-   */
-  interval?: number;
-  /**
-   * How long will we wait before the request times out?
-   *
-   * @default 60_000
-   */
-  timeout?: number;
-}
-
-type Formatters = 'biome' | 'prettier';
-
-type Linters = 'biome' | 'eslint' | 'oxlint';
+  version?: string | ((version: string) => string);
+};
 
 interface UserConfig {
   /**
@@ -6154,106 +6542,20 @@ interface UserConfig {
     | (Record<string, unknown> & { path?: never })
     | Input;
   /**
-   * The relative location of the logs folder
+   * The relative location of the logs folder.
    *
    * @default process.cwd()
    */
-  logs?:
-    | string
-    | {
-        /**
-         * Whether or not error logs should be written to a file or not
-         *
-         * @default true
-         * */
-        file?: boolean;
-        /**
-         * The logging level to control the verbosity of log output.
-         * Determines which messages are logged based on their severity.
-         *
-         * Available levels (in increasing order of severity):
-         * - `trace`: Detailed debug information, primarily for development.
-         * - `debug`: Diagnostic information useful during debugging.
-         * - `info`: General operational messages that indicate normal application behavior.
-         * - `warn`: Potentially problematic situations that require attention.
-         * - `error`: Errors that prevent some functionality but do not crash the application.
-         * - `fatal`: Critical errors that cause the application to terminate.
-         * - `silent`: Disables all logging.
-         *
-         * Messages with a severity equal to or higher than the specified level will be logged.
-         *
-         * @default 'info'
-         */
-        level?:
-          | 'debug'
-          | 'error'
-          | 'fatal'
-          | 'info'
-          | 'silent'
-          | 'trace'
-          | 'warn';
-
-        /**
-         * The relative location of the logs folder
-         *
-         * @default process.cwd()
-         */
-        path?: string;
-      };
+  logs?: string | Logs;
   /**
-   * The relative location of the output folder
+   * The relative location of the output folder.
    */
-  output:
-    | string
-    | {
-        /**
-         * Defines casing of the output fields. By default, we preserve `input`
-         * values as data transforms incur a performance penalty at runtime.
-         *
-         * @default undefined
-         */
-        case?: Exclude<StringCase, 'SCREAMING_SNAKE_CASE'>;
-        /**
-         * Clean the `output` folder on every run? If disabled, this folder may
-         * be used to store additional files. The default option is `true` to
-         * reduce the risk of keeping outdated files around when configuration,
-         * input, or package version changes.
-         *
-         * @default true
-         */
-        clean?: boolean;
-        /**
-         * Process output folder with formatter?
-         *
-         * @default false
-         */
-        format?: Formatters | false;
-        /**
-         * Should the exports from plugin files be re-exported in the index
-         * barrel file? By default, this is enabled and only default plugins
-         * are re-exported.
-         *
-         * @default true
-         */
-        indexFile?: boolean;
-        /**
-         * Process output folder with linter?
-         *
-         * @default false
-         */
-        lint?: Linters | false;
-        /**
-         * The relative location of the output folder
-         */
-        path: string;
-        /**
-         * Relative or absolute path to the tsconfig file we should use to
-         * generate the output. If a path to tsconfig file is not provided, we
-         * attempt to find one starting from the location of the
-         * `@hey-api/openapi-ts` configuration file and traversing up.
-         */
-        tsConfigPath?: 'off' | (string & {});
-      };
+  output: string | Output;
+  /**
+   * Customize how the input is parsed and transformed before it's passed to
+   * plugins.
+   */
+  parser?: Parser;
   /**
    * Plugins generate artifacts from `input`. By default, we generate SDK
    * functions and TypeScript interfaces. If you manually define `plugins`,
@@ -6331,17 +6633,23 @@ type Config$l = Omit<
   | 'logs'
   | 'name'
   | 'output'
+  | 'parser'
   | 'plugins'
   | 'request'
   | 'watch'
 > &
   Pick<UserConfig, 'base' | 'name' | 'request'> & {
-    input: Omit<Input, 'path' | 'validate_EXPERIMENTAL' | 'watch'> &
-      Pick<Required<Input>, 'path' | 'validate_EXPERIMENTAL'> & {
+    input: Omit<Input, 'path' | 'watch'> &
+      Pick<Required<Input>, 'path'> & {
         watch: Extract<Required<Required<Input>['watch']>, object>;
       };
     logs: Extract<Required<UserConfig['logs']>, object>;
     output: Extract<UserConfig['output'], object>;
+    /**
+     * Customize how the input is parsed and transformed before it's passed to
+     * plugins.
+     */
+    parser: ResolvedParser;
     pluginOrder: ReadonlyArray<keyof PluginConfigMap>;
     plugins: {
       [K in PluginNames]?: Plugin.ConfigWithName<PluginConfigMap[K]>;
@@ -7281,11 +7589,6 @@ type AnyPluginName = PluginNames | (string & {});
 
 type PluginTag = 'client' | 'transformer' | 'validator';
 
-type ObjectType<T> =
-  Extract<T, Record<string, any>> extends never
-    ? Record<string, any>
-    : Extract<T, Record<string, any>>;
-
 interface PluginContext {
   pluginByTag: <T extends AnyPluginName | boolean = AnyPluginName>(
     tag: PluginTag,
@@ -7294,25 +7597,7 @@ interface PluginContext {
       errorMessage?: string;
     },
   ) => Exclude<T, boolean> | undefined;
-  valueToObject: <
-    T extends undefined | string | boolean | number | Record<string, any>,
-  >(args: {
-    defaultValue: ObjectType<T>;
-    mappers: {
-      boolean: T extends boolean
-        ? (value: boolean) => Partial<ObjectType<T>>
-        : never;
-      number: T extends number
-        ? (value: number) => Partial<ObjectType<T>>
-        : never;
-      string: T extends string
-        ? (value: string) => Partial<ObjectType<T>>
-        : never;
-    } extends infer U
-      ? { [K in keyof U as U[K] extends never ? never : K]: U[K] }
-      : never;
-    value: T;
-  }) => ObjectType<T>;
+  valueToObject: ValueToObject;
 }
 
 type BaseApi = Record<string, unknown>;
@@ -7775,7 +8060,7 @@ type Config$a = Plugin.Name<'@hey-api/sdk'> & {
   response?: 'body' | 'response';
 };
 
-type ResolvedConfig$7 = Plugin.Name<'@hey-api/sdk'> & {
+type ResolvedConfig$8 = Plugin.Name<'@hey-api/sdk'> & {
   /**
    * Group operation methods into classes? When enabled, you can select which
    * classes to export with `sdk.include` and/or transform their names with
@@ -7927,7 +8212,7 @@ type ResolvedConfig$7 = Plugin.Name<'@hey-api/sdk'> & {
   response: 'body' | 'response';
 };
 
-type HeyApiSdkPlugin = DefinePlugin<Config$a, ResolvedConfig$7>;
+type HeyApiSdkPlugin = DefinePlugin<Config$a, ResolvedConfig$8>;
 
 type Config$9 = Plugin.Name<'@hey-api/transformers'> & {
   /**
@@ -7959,31 +8244,62 @@ type Config$9 = Plugin.Name<'@hey-api/transformers'> & {
 
 type HeyApiTransformersPlugin = DefinePlugin<Config$9>;
 
+type EnumsType = 'javascript' | 'typescript' | 'typescript+namespace';
+
 type Config$8 = Plugin.Name<'@hey-api/typescript'> & {
   /**
-   * By default, enums are generated as TypeScript types. In addition to that,
-   * you can choose to generate them as JavaScript objects, TypeScript enums,
-   * or TypeScript enums contained within namespaces.
+   * The casing convention to use for generated names.
    *
-   * @default false
+   * @default 'PascalCase'
    */
-  enums?: 'javascript' | 'typescript' | 'typescript+namespace' | false;
+  case?: Exclude<StringCase, 'SCREAMING_SNAKE_CASE'>;
   /**
-   * Defines casing of the enum keys. By default, we use `SCREAMING_SNAKE_CASE`.
-   * This option has effect only when `enums` is defined.
+   * By default, enums are emitted as types to preserve runtime-free output.
    *
-   * @default 'SCREAMING_SNAKE_CASE'
-   */
-  enumsCase?: StringCase;
-  /**
-   * When generating enums as JavaScript objects, they'll contain a null value
-   * if they're nullable. This might be undesirable if you want to do
-   * `Object.values(Foo)` and have all values be of the same type. This setting
-   * is disabled by default to preserve the source schemas.
+   * However, you may want to generate enums as JavaScript objects or
+   * TypeScript enums for runtime usage, interoperability, or integration with
+   * other tools.
    *
    * @default false
    */
-  enumsConstantsIgnoreNull?: boolean;
+  enums?:
+    | boolean
+    | EnumsType
+    | {
+        /**
+         * The casing convention to use for generated names.
+         *
+         * @default 'SCREAMING_SNAKE_CASE'
+         */
+        case?: StringCase;
+        /**
+         * When generating enums as JavaScript objects, they'll contain a null
+         * value if they're nullable. This might be undesirable if you want to do
+         * `Object.values(Foo)` and have all values be of the same type.
+         *
+         * This setting is disabled by default to preserve the source schemas.
+         *
+         * @default false
+         */
+        constantsIgnoreNull?: boolean;
+        /**
+         * Whether to generate runtime enums.
+         *
+         * @default true
+         */
+        enabled?: boolean;
+        /**
+         * Specifies the output mode for generated enums.
+         *
+         * Can be:
+         * - `javascript`: Generates JavaScript objects
+         * - `typescript`: Generates TypeScript enums
+         * - `typescript+namespace`: Generates TypeScript enums within a namespace
+         *
+         * @default 'javascript'
+         */
+        mode?: EnumsType;
+      };
   /**
    * Should the exports from the generated files be re-exported in the index
    * barrel file?
@@ -7992,48 +8308,106 @@ type Config$8 = Plugin.Name<'@hey-api/typescript'> & {
    */
   exportFromIndex?: boolean;
   /**
-   * By default, inline enums (enums not defined as reusable components in
-   * the input file) are generated as inlined union types. You can set
-   * `exportInlineEnums` to `true` to treat inline enums as reusable components.
-   * When `true`, the exported enums will follow the style defined in `enums`.
+   * Name of the generated file.
    *
-   * @default false
+   * @default 'types'
    */
-  exportInlineEnums?: boolean;
+  output?: string;
+
+  // DEPRECATED OPTIONS BELOW
+
   /**
-   * Defines casing of the identifiers. By default, we use `PascalCase`.
+   * **This feature works only with the legacy parser**
    *
-   * @default 'PascalCase'
+   * Include only types matching regular expression.
+   *
+   * @deprecated
    */
-  identifierCase?: Exclude<StringCase, 'SCREAMING_SNAKE_CASE'>;
+  // eslint-disable-next-line typescript-sort-keys/interface
+  include?: string;
   /**
-   * Name of the generated file.
+   * **This feature works only with the legacy parser**
    *
-   * @default 'types'
+   * Use your preferred naming pattern
+   *
+   * @deprecated
+   * @default 'preserve'
    */
-  output?: string;
+  style?: 'PascalCase' | 'preserve';
   /**
-   * Choose how to handle types containing read-only or write-only fields?
-   * This option exists for backward compatibility with outputs created before
-   * this feature existed.
+   * **This feature works only with the legacy parser**
    *
-   * @default 'split'
+   * Generate a tree of types containing all operations? It will be named
+   * $OpenApiTs.
+   *
+   * @deprecated
+   * @default false
    */
-  readOnlyWriteOnlyBehavior?: 'off' | 'split';
+  tree?: boolean;
+};
+
+type ResolvedConfig$7 = Plugin.Name<'@hey-api/typescript'> & {
+  /**
+   * The casing convention to use for generated names.
+   *
+   * @default 'PascalCase'
+   */
+  case: Exclude<StringCase, 'SCREAMING_SNAKE_CASE'>;
   /**
-   * Customize the name of types used in responses or containing read-only
-   * fields.
+   * By default, enums are emitted as types to preserve runtime-free output.
+   *
+   * However, you may want to generate enums as JavaScript objects or
+   * TypeScript enums for runtime usage, interoperability, or integration with
+   * other tools.
+   */
+  enums: {
+    /**
+     * The casing convention to use for generated names.
+     *
+     * @default 'SCREAMING_SNAKE_CASE'
+     */
+    case: StringCase;
+    /**
+     * When generating enums as JavaScript objects, they'll contain a null
+     * value if they're nullable. This might be undesirable if you want to do
+     * `Object.values(Foo)` and have all values be of the same type.
+     *
+     * This setting is disabled by default to preserve the source schemas.
+     *
+     * @default false
+     */
+    constantsIgnoreNull: boolean;
+    /**
+     * Whether to generate runtime enums.
+     *
+     * @default false
+     */
+    enabled: boolean;
+    /**
+     * Specifies the output mode for generated enums.
+     *
+     * Can be:
+     * - `javascript`: Generates JavaScript objects
+     * - `typescript`: Generates TypeScript enums
+     * - `typescript+namespace`: Generates TypeScript enums within a namespace
+     *
+     * @default 'javascript'
+     */
+    mode: EnumsType;
+  };
+  /**
+   * Should the exports from the generated files be re-exported in the index
+   * barrel file?
    *
-   * @default '{{name}}Readable'
+   * @default true
    */
-  readableNameBuilder?: string;
+  exportFromIndex: boolean;
   /**
-   * Customize the name of types used in payloads or containing write-only
-   * fields.
+   * Name of the generated file.
    *
-   * @default '{{name}}Writable'
+   * @default 'types'
    */
-  writableNameBuilder?: string;
+  output: string;
 
   // DEPRECATED OPTIONS BELOW
 
@@ -8054,7 +8428,7 @@ type Config$8 = Plugin.Name<'@hey-api/typescript'> & {
    * @deprecated
    * @default 'preserve'
    */
-  style?: 'PascalCase' | 'preserve';
+  style: 'PascalCase' | 'preserve';
   /**
    * **This feature works only with the legacy parser**
    *
@@ -8064,10 +8438,10 @@ type Config$8 = Plugin.Name<'@hey-api/typescript'> & {
    * @deprecated
    * @default false
    */
-  tree?: boolean;
+  tree: boolean;
 };
 
-type HeyApiTypeScriptPlugin = DefinePlugin<Config$8>;
+type HeyApiTypeScriptPlugin = DefinePlugin<Config$8, ResolvedConfig$7>;
 
 type Config$7 = Plugin.Name<'@tanstack/angular-query-experimental'> & {
   /**
@@ -9152,9 +9526,10 @@ type Config$1 = Plugin.Name<'valibot'> & {
    */
   comments?: boolean;
   /**
-   * Configuration for reusable schema definitions. Controls generation of
-   * shared Valibot schemas that can be referenced across requests and
-   * responses.
+   * Configuration for reusable schema definitions.
+   *
+   * Controls generation of shared Valibot schemas that can be referenced
+   * across requests and responses.
    *
    * Can be:
    * - `boolean`: Shorthand for `{ enabled: boolean }`
@@ -9178,8 +9553,8 @@ type Config$1 = Plugin.Name<'valibot'> & {
          */
         enabled?: boolean;
         /**
-         * Custom naming pattern for generated schema names. The name variable is
-         * obtained from the schema name.
+         * Custom naming pattern for generated schema names. The name variable
+         * is obtained from the schema name.
          *
          * @default 'v{{name}}'
          */
@@ -9208,6 +9583,7 @@ type Config$1 = Plugin.Name<'valibot'> & {
   output?: string;
   /**
    * Configuration for request-specific Valibot schemas.
+   *
    * Controls generation of Valibot schemas for request bodies, query
    * parameters, path parameters, and headers.
    *
@@ -9233,8 +9609,8 @@ type Config$1 = Plugin.Name<'valibot'> & {
          */
         enabled?: boolean;
         /**
-         * Custom naming pattern for generated schema names. The name variable is
-         * obtained from the operation name.
+         * Custom naming pattern for generated schema names. The name variable
+         * is obtained from the operation name.
          *
          * @default 'v{{name}}Data'
          */
@@ -9242,6 +9618,7 @@ type Config$1 = Plugin.Name<'valibot'> & {
       };
   /**
    * Configuration for response-specific Valibot schemas.
+   *
    * Controls generation of Valibot schemas for response bodies, error
    * responses, and status codes.
    *
@@ -9267,8 +9644,8 @@ type Config$1 = Plugin.Name<'valibot'> & {
          */
         enabled?: boolean;
         /**
-         * Custom naming pattern for generated schema names. The name variable is
-         * obtained from the operation name.
+         * Custom naming pattern for generated schema names. The name variable
+         * is obtained from the operation name.
          *
          * @default 'v{{name}}Response'
          */
@@ -9290,9 +9667,10 @@ type ResolvedConfig$1 = Plugin.Name<'valibot'> & {
    */
   comments: boolean;
   /**
-   * Configuration for reusable schema definitions. Controls generation of
-   * shared Valibot schemas that can be referenced across requests and
-   * responses.
+   * Configuration for reusable schema definitions.
+   *
+   * Controls generation of shared Valibot schemas that can be referenced
+   * across requests and responses.
    */
   definitions: {
     /**
@@ -9338,6 +9716,7 @@ type ResolvedConfig$1 = Plugin.Name<'valibot'> & {
   output: string;
   /**
    * Configuration for request-specific Valibot schemas.
+   *
    * Controls generation of Valibot schemas for request bodies, query
    * parameters, path parameters, and headers.
    */
@@ -9364,6 +9743,7 @@ type ResolvedConfig$1 = Plugin.Name<'valibot'> & {
   };
   /**
    * Configuration for response-specific Valibot schemas.
+   *
    * Controls generation of Valibot schemas for response bodies, error
    * responses, and status codes.
    */
@@ -9419,8 +9799,10 @@ type Config = Plugin.Name<'zod'> & {
    */
   comments?: boolean;
   /**
-   * Configuration for reusable schema definitions. Controls generation of
-   * shared Zod schemas that can be referenced across requests and responses.
+   * Configuration for reusable schema definitions.
+   *
+   * Controls generation of shared Zod schemas that can be referenced across
+   * requests and responses.
    *
    * Can be:
    * - `boolean`: Shorthand for `{ enabled: boolean }`
@@ -9474,7 +9856,9 @@ type Config = Plugin.Name<'zod'> & {
   output?: string;
   /**
    * Configuration for request-specific Zod schemas.
-   * Controls generation of Zod schemas for request bodies, query parameters, path parameters, and headers.
+   *
+   * Controls generation of Zod schemas for request bodies, query parameters, path
+   * parameters, and headers.
    *
    * Can be:
    * - `boolean`: Shorthand for `{ enabled: boolean }`
@@ -9507,7 +9891,9 @@ type Config = Plugin.Name<'zod'> & {
       };
   /**
    * Configuration for response-specific Zod schemas.
-   * Controls generation of Zod schemas for response bodies, error responses, and status codes.
+   *
+   * Controls generation of Zod schemas for response bodies, error responses,
+   * and status codes.
    *
    * Can be:
    * - `boolean`: Shorthand for `{ enabled: boolean }`
@@ -9554,8 +9940,10 @@ type ResolvedConfig = Plugin.Name<'zod'> & {
    */
   comments: boolean;
   /**
-   * Configuration for reusable schema definitions. Controls generation of
-   * shared Zod schemas that can be referenced across requests and responses.
+   * Configuration for reusable schema definitions.
+   *
+   * Controls generation of shared Zod schemas that can be referenced across
+   * requests and responses.
    */
   definitions: {
     /**
@@ -9601,7 +9989,9 @@ type ResolvedConfig = Plugin.Name<'zod'> & {
   output: string;
   /**
    * Configuration for request-specific Zod schemas.
-   * Controls generation of Zod schemas for request bodies, query parameters, path parameters, and headers.
+   *
+   * Controls generation of Zod schemas for request bodies, query parameters, path
+   * parameters, and headers.
    */
   requests: {
     /**
@@ -9626,7 +10016,9 @@ type ResolvedConfig = Plugin.Name<'zod'> & {
   };
   /**
    * Configuration for response-specific Zod schemas.
-   * Controls generation of Zod schemas for response bodies, error responses, and status codes.
+   *
+   * Controls generation of Zod schemas for response bodies, error responses,
+   * and status codes.
    */
   responses: {
     /**
@@ -10004,18 +10396,6 @@ declare namespace IR {
   export type ServerObject = IRServerObject;
 }
 
-/**
- * Default plugins used to generate artifacts if plugins aren't specified.
- */
-declare const defaultPlugins: readonly ["@hey-api/typescript", "@hey-api/sdk"];
-/**
- * @internal
- */
-declare const initConfigs: (userConfig: UserConfig | undefined) => Promise<ReadonlyArray<{
-    config: Config$l;
-    errors: ReadonlyArray<Error>;
-}>>;
-
 declare namespace LegacyIR {
   export type LegacyOperation = Operation;
 }
@@ -10038,4 +10418,4 @@ interface WatchValues {
   lastValue?: string;
 }
 
-export { type Client$1 as C, type DefinePlugin as D, IR as I, LegacyIR as L, OpenApi$3 as O, type PluginHandler as P, type StringCase as S, type UserConfig as U, type WatchValues as W, Plugin as a, OpenApiSchemaObject as b, Client as c, defaultPlugins as d, type Config$l as e, initConfigs as i };
+export { type Client$1 as C, type DefinePlugin as D, IR as I, LegacyIR as L, OpenApi$3 as O, type PluginHandler as P, type StringCase as S, type UserConfig as U, type WatchValues as W, Plugin as a, OpenApiMetaObject as b, OpenApiOperationObject as c, OpenApiParameterObject as d, OpenApiRequestBodyObject as e, OpenApiResponseObject as f, OpenApiSchemaObject as g, Client as h, type Config$l as i };