@power-plant/core 0.0.2 → 0.0.4

package/dist/schema-xFkmOyE6.d.cts

@@ -0,0 +1,205 @@
+import { InferExtractOptions, SchemaEnvelopeOf, SchemaSourceInput } from "@power-plant/schema";
+
+//#region ../../../node_modules/.pnpm/@stryke+types@0.12.21/node_modules/@stryke/types/dist/base.d.mts
+/**
+ * Matches a value that is either of type `T` or a promise that resolves to `T`.
+ *
+ * @example
+ * ```ts
+ * type Result = MaybePromise<string>;
+ * // string | Promise<string>
+ * ```
+ */
+type MaybePromise<T> = T | Promise<T>;
+/**
+ * Matches a reducer function that takes the current state and an action, returning the next state.
+ *
+ * @remarks
+ * This is the function signature used in state management libraries like Redux.
+ *
+ * @example
+ * ```ts
+ * type CounterReducer = ReducerFunction<number, { type: 'increment' | 'decrement' }>;
+ * const reducer: CounterReducer = (state, action) => {
+ *   return action.type === 'increment' ? state + 1 : state - 1;
+ * };
+ * ```
+ */
+//#endregion
+//#region src/types/meta.d.ts
+type MetaValue<TSpec, TOptions extends object, TValue = any> = TValue | ((spec: TSpec, options: TOptions) => MaybePromise<TValue>);
+type MetaDeprecated = true | string | {
+  message?: string;
+  since?: string;
+  alternative?: string;
+};
+type MetaLink = string | {
+  href: string;
+  description?: string;
+};
+interface MetaInput<TSpec, TOptions extends object> {
+  /**
+   * A name for the schema, which can be used to identify or reference the schema in documentation, tooling, or other contexts. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `name` property is a string that can be used to give the schema a human-readable identifier. It can be used in documentation, error messages, or other contexts where it is helpful to have a name associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  name?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A version string that indicates the version of the schema. This property can be used to track changes or updates to the schema over time, allowing consumers of the schema to determine which version they are working with. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `version` property is a string that can follow any versioning scheme, such as semantic versioning (e.g., "1.0.0", "2.1.3"), date-based versioning (e.g., "2023-06-15"), or any other format that conveys the version of the schema. It is recommended to use a consistent versioning scheme across all schemas to facilitate easier tracking and management of schema versions.
+   *
+   * @defaultValue "1.0"
+   */
+  version?: MetaValue<TSpec, TOptions, string | Date | number>;
+  /**
+   * A string that describes the schema in some way.
+   */
+  description?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A string that provides a human-readable name for the schema, which can be used in documentation, tooling, or other contexts to identify or reference the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `title` property is a string that can be used to give the schema a more user-friendly or descriptive name. It can be used in documentation, error messages, or other contexts where it is helpful to have a display name associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  title?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A string that describes when the schema is used.
+   */
+  usage?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * Indicates whether the schema is deprecated, and optionally provides additional information about the deprecation, such as a message, the version since which it is deprecated, and an alternative schema to use instead.
+   *
+   * @remarks
+   * The `deprecated` property can be a boolean value, where `true` indicates that the schema is deprecated and `false` indicates that it is not. It can also be a string that provides a message explaining the deprecation, or an object that includes additional details such as a message, the version since which it is deprecated, and an alternative schema to use instead. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  deprecated?: MetaValue<TSpec, TOptions, MetaDeprecated>;
+  /**
+   * An array of tags associated with the schema. Tags can be used to categorize or label schemas for organizational purposes, making it easier to search, filter, or group related schemas together. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * Each tag in the array should be a string that represents a meaningful label or category for the schema. It is recommended to use consistent and descriptive tags across schemas to facilitate easier management and discovery of related schemas.
+   */
+  tags?: MetaValue<TSpec, TOptions, string[]>;
+  /**
+   * An array of links associated with the schema. Each link can be a string representing a URL or an object containing a `href` property and an optional `description` property.
+   */
+  links?: MetaValue<TSpec, TOptions, MetaLink[]>;
+}
+interface Meta<TSpec, TOptions extends object> {
+  /**
+   * A unique identifier for the schema, which can be used to reference or identify the schema in documentation, tooling, or other contexts. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `id` property is a string that can be used to give the schema a unique identifier. It can be used in documentation, error messages, or other contexts where it is helpful to have an identifier associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  id: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A name for the schema, which can be used to identify or reference the schema in documentation, tooling, or other contexts. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `name` property is a string that can be used to give the schema a human-readable identifier. It can be used in documentation, error messages, or other contexts where it is helpful to have a name associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  name: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A version string that indicates the version of the schema. This property can be used to track changes or updates to the schema over time, allowing consumers of the schema to determine which version they are working with. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `version` property is a string that can follow any versioning scheme, such as semantic versioning (e.g., "1.0.0", "2.1.3"), date-based versioning (e.g., "2023-06-15"), or any other format that conveys the version of the schema. It is recommended to use a consistent versioning scheme across all schemas to facilitate easier tracking and management of schema versions.
+   *
+   * @defaultValue "1.0"
+   */
+  version: MetaValue<TSpec, TOptions, string | Date | number>;
+  /**
+   * A string that describes the schema in some way.
+   */
+  description: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A string that provides a human-readable name for the schema, which can be used in documentation, tooling, or other contexts to identify or reference the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `title` property is a string that can be used to give the schema a more user-friendly or descriptive name. It can be used in documentation, error messages, or other contexts where it is helpful to have a display name associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  title: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A string that describes when the schema is used.
+   */
+  usage?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * Indicates whether the schema is deprecated, and optionally provides additional information about the deprecation, such as a message, the version since which it is deprecated, and an alternative schema to use instead.
+   *
+   * @remarks
+   * The `deprecated` property can be a boolean value, where `true` indicates that the schema is deprecated and `false` indicates that it is not. It can also be a string that provides a message explaining the deprecation, or an object that includes additional details such as a message, the version since which it is deprecated, and an alternative schema to use instead. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  deprecated?: MetaValue<TSpec, TOptions, MetaDeprecated>;
+  /**
+   * An array of tags associated with the schema. Tags can be used to categorize or label schemas for organizational purposes, making it easier to search, filter, or group related schemas together. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * Each tag in the array should be a string that represents a meaningful label or category for the schema. It is recommended to use consistent and descriptive tags across schemas to facilitate easier management and discovery of related schemas.
+   */
+  tags?: MetaValue<TSpec, TOptions, string[]>;
+  /**
+   * An array of links associated with the schema. Each link can be a string representing a URL or an object containing a `href` property and an optional `description` property.
+   */
+  links: MetaValue<TSpec, TOptions, MetaLink[]>;
+}
+//#endregion
+//#region src/types/schema.d.ts
+type SchemaMetaExample<TSpec> = TSpec | {
+  name?: string;
+  description?: string;
+  value: TSpec;
+};
+interface SchemaMetaInput<TSpec, TOptions extends object = any> extends MetaInput<TSpec, TOptions> {
+  /**
+   * Examples of valid data for the schema. This can be a single example or an array of examples.
+   */
+  examples?: SchemaMetaExample<TSpec> | MetaValue<TSpec, TOptions, SchemaMetaExample<TSpec>[]>;
+  /**
+   * A description of the specification that is described by this schema.
+   */
+  spec?: MetaValue<TSpec, TOptions, string>;
+}
+interface SchemaMeta<TSpec, TOptions extends object = any> extends Meta<TSpec, TOptions> {
+  /**
+   * Examples of valid data for the schema.
+   */
+  examples: MetaValue<TSpec, TOptions, SchemaMetaExample<TSpec>[]>;
+}
+/**
+ * Schema input wrapper that attaches optional contextual metadata.
+ */
+interface SchemaInputObject<TSpec, TOptions extends object = any> {
+  /**
+   * The schema that defines the structure of the specification input for the generator. This schema is used to validate the input specification and ensure that it conforms to the expected format before being processed by the generator.
+   */
+  schema: SchemaSourceInput<TSpec> | SchemaEnvelopeOf<TSpec>;
+  /**
+   * Optional metadata that provides contextual information for the schema.
+   */
+  meta?: SchemaMetaInput<TSpec, TOptions>;
+}
+type InferCreateSchemaOptions<T extends SchemaSourceInput<any> | SchemaEnvelopeOf<any> | SchemaInputObject<any, any>> = T extends SchemaSourceInput<any> | SchemaEnvelopeOf<any> ? InferExtractOptions<T> : {};
+/**
+ * A schema extracted from a source input, normalized to JSON Schema.
+ */
+interface Schema<TSpec, TOptions extends object = any> extends SchemaEnvelopeOf<TSpec> {
+  /**
+   * Optional contextual metadata associated with the schema.
+   */
+  meta: SchemaMeta<TSpec, TOptions>;
+}
+/**
+ * A normalized JSON Schema extracted from a source input of type `T`. This type represents the result of the schema extraction process, where a raw schema input (which could be in various formats such as Zod, Untyped, Valibot, or as a type definition in TypeScript source code) is transformed into a standardized JSON Schema format. The `SchemaOf<T>` type captures the normalized JSON Schema along with metadata about the source variant and a content hash for caching or identification purposes.
+ *
+ * @template TSpec - The original TypeScript type for which the schema is being extracted. This type parameter is used to derive the appropriate JSON Schema representation based on the structure and constraints of `T`.
+ *
+ * @see {@link Schema}
+ */
+type SchemaOf<TSpec, TOptions extends object = any> = Schema<TSpec, TOptions>;
+//#endregion
+export { SchemaMetaExample as a, Meta as c, MetaLink as d, MetaValue as f, SchemaMeta as i, MetaDeprecated as l, Schema as n, SchemaMetaInput as o, MaybePromise as p, SchemaInputObject as r, SchemaOf as s, InferCreateSchemaOptions as t, MetaInput as u };
+//# sourceMappingURL=schema-xFkmOyE6.d.cts.map

package/dist/schema-xFkmOyE6.d.cts.map

@@ -0,0 +1 @@
+{"version":3,"file":"schema-xFkmOyE6.d.cts","names":["SerializablePrimitive","Primitive","Date","RegExp","Function","Promise","value","Record","TypeTester","Value","X","A","ReadonlyArray","P","List","R","args","FunctionLike","T","Nullish","Map","WeakMap","WeakKey","emptyObjectSymbol","PlainObject","AnyArray","AnyMap","AnyWeakMap","IndexType","TypedIndexable","F1","F2","Uppercase","Lowercase","AnyCase","F","EMPTY_STRING","_args","prototype","clone","TState","TAction","state","action","IArguments","Set","K","Omit","Required","Pick","Narrowable","NarrowRaw","Try","A1","A2","Catch","N","Result","ComputeRange","TValue","TName","name","File","D","BrowserNativeObject","NestedValue","DeepPartial","Depth","DeepRequired","DeepNonNullable","NonNullable","DeepReadonly","Array","U","DeepReadonlyNonNullable","DeepReadonlyNullable","initialValue","currentValue","BaseType","Exclude","Key","B","G","KeyType","ExcludeType","IsEqual","requireExactProps","ObjectType","KeysType","Options","ExceptOptions","Filter","Partial","Keys","$NestedValue","current","id","version","sequence","__type","Typed","isTypeOf","BuiltIns","arguments_","IsNull","IsUndefined","AnyFunction","globalThis","Arguments","AbstractConstructor","L","Fill","BuildTuple","ArrayBuffer","DataView","Error","TypedArray","Blob","StructuredCloneable","key","ReadonlyMap","ReadonlySet","StructuredCloneablePrimitive","StructuredCloneableData","StructuredCloneableCollection"],"sources":["../../../../node_modules/.pnpm/@stryke+types@0.12.21/node_modules/@stryke/types/dist/base.d.mts","../src/types/meta.ts","../src/types/schema.ts"],"x_google_ignoreList":[0],"mappings":";;;;AE2BuD;AAEvD;;;;;;;KFsMK,YAAA,MAAkB,CAAA,GAAI,OAAA,CAAQ,CAAA;;;;;;;;;;;;;;;;;KC/MvB,SAAA,iDACR,MAAA,KACE,IAAA,EAAM,KAAA,EAAO,OAAA,EAAS,QAAA,KAAa,YAAA,CAAa,MAAA;AAAA,KAE1C,cAAA;EAGN,OAAA;EAAkB,KAAA;EAAgB,WAAA;AAAA;AAAA,KAE5B,QAAA;EAAsB,IAAA;EAAc,WAAW;AAAA;AAAA,UAE1C,SAAA;EDoMMkB;;;;AAAa;;EC7LlC,IAAA,GAAO,SAAA,CAAU,KAAA,EAAO,QAAA;;AAlB1B;;;;;;;EA4BE,OAAA,GAAU,SAAA,CAAU,KAAA,EAAO,QAAA,WAAmB,IAAA;EA1BK;;;EA+BnD,WAAA,GAAc,SAAA,CAAU,KAAA,EAAO,QAAA;EAjCqB;;;;;;EAyCpD,KAAA,GAAQ,SAAA,CAAU,KAAA,EAAO,QAAA;EAvC2B;;AAAM;EA4C1D,KAAA,GAAQ,SAAA,CAAU,KAAA,EAAO,QAAA;EA1CD;;;;;;EAkDxB,UAAA,GAAa,SAAA,CAAU,KAAA,EAAO,QAAA,EAAU,cAAA;EA/CS;AAEnD;;;;AAA2D;EAqDzD,IAAA,GAAO,SAAA,CAAU,KAAA,EAAO,QAAA;EAnDA;;;EAwDxB,KAAA,GAAQ,SAAA,CAAU,KAAA,EAAO,QAAA,EAAU,QAAA;AAAA;AAAA,UAGpB,IAAA;EA1CY;;;;;;EAiD3B,EAAA,EAAI,SAAA,CAAU,KAAA,EAAO,QAAA;EApCI;;;;;;EA4CzB,IAAA,EAAM,SAAA,CAAU,KAAA,EAAO,QAAA;EA/BiB;;;;;;;;EAyCxC,OAAA,EAAS,SAAA,CAAU,KAAA,EAAO,QAAA,WAAmB,IAAA;EA5B5B;;;EAiCjB,WAAA,EAAa,SAAA,CAAU,KAAA,EAAO,QAAA;EAlF9B;;;;;;EA0FA,KAAA,EAAO,SAAA,CAAU,KAAA,EAAO,QAAA;EAhFG;;;EAqF3B,KAAA,GAAQ,SAAA,CAAU,KAAA,EAAO,QAAA;EAhFD;;;;;;EAwFxB,UAAA,GAAa,SAAA,CAAU,KAAA,EAAO,QAAA,EAAU,cAAA;EA3EhC;;;;;;EAmFR,IAAA,GAAO,SAAA,CAAU,KAAA,EAAO,QAAA;EA3EgB;;;EAgFxC,KAAA,EAAO,SAAA,CAAU,KAAA,EAAO,QAAA,EAAU,QAAA;AAAA;;;KCjIxB,iBAAA,UACR,KAAA;EACE,IAAA;EAAe,WAAA;EAAsB,KAAA,EAAO,KAAK;AAAA;AAAA,UAEtC,eAAA,+CAGP,SAAA,CAAU,KAAA,EAAO,QAAA;EFmMA;;;EE/LzB,QAAA,GACI,iBAAA,CAAkB,KAAA,IAClB,SAAA,CAAU,KAAA,EAAO,QAAA,EAAU,iBAAA,CAAkB,KAAA;EF6L5BA;;;EExLrB,IAAA,GAAO,SAAA,CAAU,KAAA,EAAO,QAAA;AAAA;AAAA,UAGT,UAAA,+CAAyD,IAAA,CACxE,KAAA,EACA,QAAA;;;AD5BF;ECiCE,QAAA,EAAU,SAAA,CAAU,KAAA,EAAO,QAAA,EAAU,iBAAA,CAAkB,KAAA;AAAA;;;;UAMxC,iBAAA;EDrCwB;;;ECyCvC,MAAA,EAAQ,iBAAA,CAAkB,KAAA,IAAS,gBAAA,CAAiB,KAAA;ED3CzB;;;ECgD3B,IAAA,GAAO,eAAA,CAAgB,KAAA,EAAO,QAAA;AAAA;AAAA,KAGpB,wBAAA,WAEN,iBAAA,QACA,gBAAA,QACA,iBAAA,cACF,CAAA,SAAU,iBAAA,QAAyB,gBAAA,QACnC,mBAAA,CAAoB,CAAA;;;;UAOP,MAAA,+CAGP,gBAAA,CAAiB,KAAA;EDjEiC;AAE5D;;ECmEE,IAAA,EAAM,UAAA,CAAW,KAAA,EAAO,QAAA;AAAA;;;;;ADhEyB;AAEnD;;KCwEY,QAAA,yCAAiD,MAAA,CAC3D,KAAA,EACA,QAAA"}

package/dist/schema-xFkmOyE6.d.mts

@@ -0,0 +1,205 @@
+import { InferExtractOptions, SchemaEnvelopeOf, SchemaSourceInput } from "@power-plant/schema";
+
+//#region ../../../node_modules/.pnpm/@stryke+types@0.12.21/node_modules/@stryke/types/dist/base.d.mts
+/**
+ * Matches a value that is either of type `T` or a promise that resolves to `T`.
+ *
+ * @example
+ * ```ts
+ * type Result = MaybePromise<string>;
+ * // string | Promise<string>
+ * ```
+ */
+type MaybePromise<T> = T | Promise<T>;
+/**
+ * Matches a reducer function that takes the current state and an action, returning the next state.
+ *
+ * @remarks
+ * This is the function signature used in state management libraries like Redux.
+ *
+ * @example
+ * ```ts
+ * type CounterReducer = ReducerFunction<number, { type: 'increment' | 'decrement' }>;
+ * const reducer: CounterReducer = (state, action) => {
+ *   return action.type === 'increment' ? state + 1 : state - 1;
+ * };
+ * ```
+ */
+//#endregion
+//#region src/types/meta.d.ts
+type MetaValue<TSpec, TOptions extends object, TValue = any> = TValue | ((spec: TSpec, options: TOptions) => MaybePromise<TValue>);
+type MetaDeprecated = true | string | {
+  message?: string;
+  since?: string;
+  alternative?: string;
+};
+type MetaLink = string | {
+  href: string;
+  description?: string;
+};
+interface MetaInput<TSpec, TOptions extends object> {
+  /**
+   * A name for the schema, which can be used to identify or reference the schema in documentation, tooling, or other contexts. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `name` property is a string that can be used to give the schema a human-readable identifier. It can be used in documentation, error messages, or other contexts where it is helpful to have a name associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  name?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A version string that indicates the version of the schema. This property can be used to track changes or updates to the schema over time, allowing consumers of the schema to determine which version they are working with. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `version` property is a string that can follow any versioning scheme, such as semantic versioning (e.g., "1.0.0", "2.1.3"), date-based versioning (e.g., "2023-06-15"), or any other format that conveys the version of the schema. It is recommended to use a consistent versioning scheme across all schemas to facilitate easier tracking and management of schema versions.
+   *
+   * @defaultValue "1.0"
+   */
+  version?: MetaValue<TSpec, TOptions, string | Date | number>;
+  /**
+   * A string that describes the schema in some way.
+   */
+  description?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A string that provides a human-readable name for the schema, which can be used in documentation, tooling, or other contexts to identify or reference the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `title` property is a string that can be used to give the schema a more user-friendly or descriptive name. It can be used in documentation, error messages, or other contexts where it is helpful to have a display name associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  title?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A string that describes when the schema is used.
+   */
+  usage?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * Indicates whether the schema is deprecated, and optionally provides additional information about the deprecation, such as a message, the version since which it is deprecated, and an alternative schema to use instead.
+   *
+   * @remarks
+   * The `deprecated` property can be a boolean value, where `true` indicates that the schema is deprecated and `false` indicates that it is not. It can also be a string that provides a message explaining the deprecation, or an object that includes additional details such as a message, the version since which it is deprecated, and an alternative schema to use instead. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  deprecated?: MetaValue<TSpec, TOptions, MetaDeprecated>;
+  /**
+   * An array of tags associated with the schema. Tags can be used to categorize or label schemas for organizational purposes, making it easier to search, filter, or group related schemas together. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * Each tag in the array should be a string that represents a meaningful label or category for the schema. It is recommended to use consistent and descriptive tags across schemas to facilitate easier management and discovery of related schemas.
+   */
+  tags?: MetaValue<TSpec, TOptions, string[]>;
+  /**
+   * An array of links associated with the schema. Each link can be a string representing a URL or an object containing a `href` property and an optional `description` property.
+   */
+  links?: MetaValue<TSpec, TOptions, MetaLink[]>;
+}
+interface Meta<TSpec, TOptions extends object> {
+  /**
+   * A unique identifier for the schema, which can be used to reference or identify the schema in documentation, tooling, or other contexts. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `id` property is a string that can be used to give the schema a unique identifier. It can be used in documentation, error messages, or other contexts where it is helpful to have an identifier associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  id: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A name for the schema, which can be used to identify or reference the schema in documentation, tooling, or other contexts. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `name` property is a string that can be used to give the schema a human-readable identifier. It can be used in documentation, error messages, or other contexts where it is helpful to have a name associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  name: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A version string that indicates the version of the schema. This property can be used to track changes or updates to the schema over time, allowing consumers of the schema to determine which version they are working with. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `version` property is a string that can follow any versioning scheme, such as semantic versioning (e.g., "1.0.0", "2.1.3"), date-based versioning (e.g., "2023-06-15"), or any other format that conveys the version of the schema. It is recommended to use a consistent versioning scheme across all schemas to facilitate easier tracking and management of schema versions.
+   *
+   * @defaultValue "1.0"
+   */
+  version: MetaValue<TSpec, TOptions, string | Date | number>;
+  /**
+   * A string that describes the schema in some way.
+   */
+  description: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A string that provides a human-readable name for the schema, which can be used in documentation, tooling, or other contexts to identify or reference the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * The `title` property is a string that can be used to give the schema a more user-friendly or descriptive name. It can be used in documentation, error messages, or other contexts where it is helpful to have a display name associated with the schema. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  title: MetaValue<TSpec, TOptions, string>;
+  /**
+   * A string that describes when the schema is used.
+   */
+  usage?: MetaValue<TSpec, TOptions, string>;
+  /**
+   * Indicates whether the schema is deprecated, and optionally provides additional information about the deprecation, such as a message, the version since which it is deprecated, and an alternative schema to use instead.
+   *
+   * @remarks
+   * The `deprecated` property can be a boolean value, where `true` indicates that the schema is deprecated and `false` indicates that it is not. It can also be a string that provides a message explaining the deprecation, or an object that includes additional details such as a message, the version since which it is deprecated, and an alternative schema to use instead. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   */
+  deprecated?: MetaValue<TSpec, TOptions, MetaDeprecated>;
+  /**
+   * An array of tags associated with the schema. Tags can be used to categorize or label schemas for organizational purposes, making it easier to search, filter, or group related schemas together. The presence of this property does not affect the validation behavior of the schema itself, but it can provide additional context or information about the expected data when used in conjunction with compatible tools.
+   *
+   * @remarks
+   * Each tag in the array should be a string that represents a meaningful label or category for the schema. It is recommended to use consistent and descriptive tags across schemas to facilitate easier management and discovery of related schemas.
+   */
+  tags?: MetaValue<TSpec, TOptions, string[]>;
+  /**
+   * An array of links associated with the schema. Each link can be a string representing a URL or an object containing a `href` property and an optional `description` property.
+   */
+  links: MetaValue<TSpec, TOptions, MetaLink[]>;
+}
+//#endregion
+//#region src/types/schema.d.ts
+type SchemaMetaExample<TSpec> = TSpec | {
+  name?: string;
+  description?: string;
+  value: TSpec;
+};
+interface SchemaMetaInput<TSpec, TOptions extends object = any> extends MetaInput<TSpec, TOptions> {
+  /**
+   * Examples of valid data for the schema. This can be a single example or an array of examples.
+   */
+  examples?: SchemaMetaExample<TSpec> | MetaValue<TSpec, TOptions, SchemaMetaExample<TSpec>[]>;
+  /**
+   * A description of the specification that is described by this schema.
+   */
+  spec?: MetaValue<TSpec, TOptions, string>;
+}
+interface SchemaMeta<TSpec, TOptions extends object = any> extends Meta<TSpec, TOptions> {
+  /**
+   * Examples of valid data for the schema.
+   */
+  examples: MetaValue<TSpec, TOptions, SchemaMetaExample<TSpec>[]>;
+}
+/**
+ * Schema input wrapper that attaches optional contextual metadata.
+ */
+interface SchemaInputObject<TSpec, TOptions extends object = any> {
+  /**
+   * The schema that defines the structure of the specification input for the generator. This schema is used to validate the input specification and ensure that it conforms to the expected format before being processed by the generator.
+   */
+  schema: SchemaSourceInput<TSpec> | SchemaEnvelopeOf<TSpec>;
+  /**
+   * Optional metadata that provides contextual information for the schema.
+   */
+  meta?: SchemaMetaInput<TSpec, TOptions>;
+}
+type InferCreateSchemaOptions<T extends SchemaSourceInput<any> | SchemaEnvelopeOf<any> | SchemaInputObject<any, any>> = T extends SchemaSourceInput<any> | SchemaEnvelopeOf<any> ? InferExtractOptions<T> : {};
+/**
+ * A schema extracted from a source input, normalized to JSON Schema.
+ */
+interface Schema<TSpec, TOptions extends object = any> extends SchemaEnvelopeOf<TSpec> {
+  /**
+   * Optional contextual metadata associated with the schema.
+   */
+  meta: SchemaMeta<TSpec, TOptions>;
+}
+/**
+ * A normalized JSON Schema extracted from a source input of type `T`. This type represents the result of the schema extraction process, where a raw schema input (which could be in various formats such as Zod, Untyped, Valibot, or as a type definition in TypeScript source code) is transformed into a standardized JSON Schema format. The `SchemaOf<T>` type captures the normalized JSON Schema along with metadata about the source variant and a content hash for caching or identification purposes.
+ *
+ * @template TSpec - The original TypeScript type for which the schema is being extracted. This type parameter is used to derive the appropriate JSON Schema representation based on the structure and constraints of `T`.
+ *
+ * @see {@link Schema}
+ */
+type SchemaOf<TSpec, TOptions extends object = any> = Schema<TSpec, TOptions>;
+//#endregion
+export { SchemaMetaExample as a, Meta as c, MetaLink as d, MetaValue as f, SchemaMeta as i, MetaDeprecated as l, Schema as n, SchemaMetaInput as o, MaybePromise as p, SchemaInputObject as r, SchemaOf as s, InferCreateSchemaOptions as t, MetaInput as u };
+//# sourceMappingURL=schema-xFkmOyE6.d.mts.map

package/dist/schema-xFkmOyE6.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"schema-xFkmOyE6.d.mts","names":["SerializablePrimitive","Primitive","Date","RegExp","Function","Promise","value","Record","TypeTester","Value","X","A","ReadonlyArray","P","List","R","args","FunctionLike","T","Nullish","Map","WeakMap","WeakKey","emptyObjectSymbol","PlainObject","AnyArray","AnyMap","AnyWeakMap","IndexType","TypedIndexable","F1","F2","Uppercase","Lowercase","AnyCase","F","EMPTY_STRING","_args","prototype","clone","TState","TAction","state","action","IArguments","Set","K","Omit","Required","Pick","Narrowable","NarrowRaw","Try","A1","A2","Catch","N","Result","ComputeRange","TValue","TName","name","File","D","BrowserNativeObject","NestedValue","DeepPartial","Depth","DeepRequired","DeepNonNullable","NonNullable","DeepReadonly","Array","U","DeepReadonlyNonNullable","DeepReadonlyNullable","initialValue","currentValue","BaseType","Exclude","Key","B","G","KeyType","ExcludeType","IsEqual","requireExactProps","ObjectType","KeysType","Options","ExceptOptions","Filter","Partial","Keys","$NestedValue","current","id","version","sequence","__type","Typed","isTypeOf","BuiltIns","arguments_","IsNull","IsUndefined","AnyFunction","globalThis","Arguments","AbstractConstructor","L","Fill","BuildTuple","ArrayBuffer","DataView","Error","TypedArray","Blob","StructuredCloneable","key","ReadonlyMap","ReadonlySet","StructuredCloneablePrimitive","StructuredCloneableData","StructuredCloneableCollection"],"sources":["../../../../node_modules/.pnpm/@stryke+types@0.12.21/node_modules/@stryke/types/dist/base.d.mts","../src/types/meta.ts","../src/types/schema.ts"],"x_google_ignoreList":[0],"mappings":""}

package/dist/sink/create.cjs

@@ -0,0 +1 @@
+Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("../create-23iLtMb_.cjs"),t=require("./helpers.cjs");let n=require("@stryke/resolve/load"),r=require("@stryke/type-checks/is-function"),i=require("@power-plant/schema/helpers"),a=require("@stryke/resolve/type-checks");function o(t,n){let i=t?.schema??{},a=e.r(t,n);return a.description=e.i((0,r.isFunction)(a.title)?async(e,t)=>`Accepts a ${await Promise.resolve(a.title(e,t))??``} specification and processes it with a {title} sink.`:`Accepts a ${a.title??``} specification and processes it with a {title} sink.`,i,a,n?.description),a}async function s(r,c,l={}){let{sink:u,meta:d,schema:f}=t.isSinkInputObject(c)?c:{sink:c,meta:{}},p=r;f&&(p=await e.t(f,l),p.schema=(0,i.mergeMetadata)(p.schema,r.schema));let m;if((0,a.isLoadInput)(u))try{let e=await(0,n.load)(u,l);m=t.isSinkInputObject(e)?await s(p,e.sink,l).then(e=>e.sink):e}catch{}return m||=u,{schema:p,sink:m,meta:o(p,d)}}exports.createSink=s,exports.extractSinkMeta=o;

package/dist/sink/create.d.cts

@@ -0,0 +1,2 @@
+import { n as extractSinkMeta, t as createSink } from "../create-DAGPeYVI.cjs";
+export { createSink, extractSinkMeta };

package/dist/sink/create.d.mts

@@ -0,0 +1,2 @@
+import { n as extractSinkMeta, t as createSink } from "../create-DEe398aQ.mjs";
+export { createSink, extractSinkMeta };

package/dist/sink/create.mjs

@@ -0,0 +1,2 @@
+import{i as e,r as t,t as n}from"../create-BR4IeVl4.mjs";import{isSinkInputObject as r}from"./helpers.mjs";import{load as i}from"@stryke/resolve/load";import{isFunction as a}from"@stryke/type-checks/is-function";import{mergeMetadata as o}from"@power-plant/schema/helpers";import{isLoadInput as s}from"@stryke/resolve/type-checks";function c(n,r){let i=n?.schema??{},o=t(n,r);return o.description=e(a(o.title)?async(e,t)=>`Accepts a ${await Promise.resolve(o.title(e,t))??``} specification and processes it with a {title} sink.`:`Accepts a ${o.title??``} specification and processes it with a {title} sink.`,i,o,r?.description),o}async function l(e,t,a={}){let{sink:u,meta:d,schema:f}=r(t)?t:{sink:t,meta:{}},p=e;f&&(p=await n(f,a),p.schema=o(p.schema,e.schema));let m;if(s(u))try{let e=await i(u,a);m=r(e)?await l(p,e.sink,a).then(e=>e.sink):e}catch{}return m||=u,{schema:p,sink:m,meta:c(p,d)}}export{l as createSink,c as extractSinkMeta};
+//# sourceMappingURL=create.mjs.map

package/dist/sink/create.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"create.mjs","names":[],"sources":[],"mappings":""}

package/dist/sink/define.cjs

@@ -0,0 +1 @@
+Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("./helpers.cjs");function t(t){return e.isSinkInputObject(t)?t:{sink:t}}exports.defineSink=t;

package/dist/sink/define.d.cts

@@ -0,0 +1,37 @@
+import { a as SinkInputObject, i as SinkInput } from "../sink-DHpx94GM.cjs";
+//#region src/sink/define.d.ts
+/**
+ * Defines a sink input object. If the provided sink is already a sink input object, it will be returned as-is. Otherwise, it will be wrapped in an object with a `sink` property.
+ *
+ * @example
+ * ```ts
+ * import { defineSink } from "@power-plant/core";
+ *
+ * // Define a sink from a sink function
+ * export default defineSink((spec, options) => {
+ *   // Your sink logic here
+ * });
+ *
+ * // Define a sink from an existing sink input object
+ * export default defineSink({
+ *  meta: {
+ *     name: "My Sink",
+ *     version: "1.0.0",
+ *     description: "A sink that does something.",
+ *   },
+ *   schema: z.object({
+ *     // Your schema definition here
+ *   }),
+ *   sink: (spec, options) => {
+ *     // Your sink logic here
+ *   },
+ * });
+ * ```
+ *
+ * @param sink - The sink input to define. This can be either a sink input object or a sink function.
+ * @returns A sink input object that contains the provided sink. If the input was already a sink input object, it will be returned unchanged.
+ */
+declare function defineSink<TSpec, TOptions extends object, TReturns = void>(sink: SinkInput<TSpec, TOptions, TReturns>): SinkInputObject<TSpec, TOptions, TReturns>;
+//#endregion
+export { defineSink };
+//# sourceMappingURL=define.d.cts.map

package/dist/sink/define.d.cts.map

@@ -0,0 +1 @@
+{"version":3,"file":"define.d.cts","names":[],"sources":["../../src/sink/define.ts"],"mappings":";;;;;AAoDA;;;;;;;;;;;;;;;;;;;;;;;;;;AAE4C;;iBAF5B,UAAA,kDACd,IAAA,EAAM,SAAA,CAAU,KAAA,EAAO,QAAA,EAAU,QAAA,IAChC,eAAA,CAAgB,KAAA,EAAO,QAAA,EAAU,QAAA"}

package/dist/sink/define.d.mts

@@ -0,0 +1,37 @@
+import { a as SinkInputObject, i as SinkInput } from "../sink-CHQncb8H.mjs";
+//#region src/sink/define.d.ts
+/**
+ * Defines a sink input object. If the provided sink is already a sink input object, it will be returned as-is. Otherwise, it will be wrapped in an object with a `sink` property.
+ *
+ * @example
+ * ```ts
+ * import { defineSink } from "@power-plant/core";
+ *
+ * // Define a sink from a sink function
+ * export default defineSink((spec, options) => {
+ *   // Your sink logic here
+ * });
+ *
+ * // Define a sink from an existing sink input object
+ * export default defineSink({
+ *  meta: {
+ *     name: "My Sink",
+ *     version: "1.0.0",
+ *     description: "A sink that does something.",
+ *   },
+ *   schema: z.object({
+ *     // Your schema definition here
+ *   }),
+ *   sink: (spec, options) => {
+ *     // Your sink logic here
+ *   },
+ * });
+ * ```
+ *
+ * @param sink - The sink input to define. This can be either a sink input object or a sink function.
+ * @returns A sink input object that contains the provided sink. If the input was already a sink input object, it will be returned unchanged.
+ */
+declare function defineSink<TSpec, TOptions extends object, TReturns = void>(sink: SinkInput<TSpec, TOptions, TReturns>): SinkInputObject<TSpec, TOptions, TReturns>;
+//#endregion
+export { defineSink };
+//# sourceMappingURL=define.d.mts.map

package/dist/sink/define.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"define.d.mts","names":[],"sources":["../../src/sink/define.ts"],"mappings":""}

package/dist/sink/define.mjs

@@ -0,0 +1,2 @@
+import{isSinkInputObject as e}from"./helpers.mjs";function t(t){return e(t)?t:{sink:t}}export{t as defineSink};
+//# sourceMappingURL=define.mjs.map

package/dist/sink/define.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"define.mjs","names":[],"sources":[],"mappings":""}

package/dist/sink/helpers.cjs

@@ -0,0 +1 @@
+Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});let e=require("@stryke/type-checks/is-set-object");function t(t){return(0,e.isSetObject)(t)&&`sink`in t&&t.sink!==void 0}exports.isSinkInputObject=t;

package/dist/sink/helpers.d.cts

@@ -0,0 +1,13 @@
+import { a as SinkInputObject } from "../sink-DHpx94GM.cjs";
+
+//#region src/sink/helpers.d.ts
+/**
+ * Checks if the provided input is a {@link SinkInputObject}.
+ *
+ * @param input - The input to check.
+ * @returns True if the input is a {@link SinkInputObject}, false otherwise.
+ */
+declare function isSinkInputObject<TSpec, TOptions extends object, TReturns = void>(input: unknown): input is SinkInputObject<TSpec, TOptions, TReturns>;
+//#endregion
+export { isSinkInputObject };
+//# sourceMappingURL=helpers.d.cts.map

package/dist/sink/helpers.d.cts.map

@@ -0,0 +1 @@
+{"version":3,"file":"helpers.d.cts","names":[],"sources":["../../src/sink/helpers.ts"],"mappings":";;;;;AA2BA;;;;iBAAgB,iBAAA,kDAId,KAAA,YAAiB,KAAA,IAAS,eAAA,CAAgB,KAAA,EAAO,QAAA,EAAU,QAAA"}

package/dist/sink/helpers.d.mts

@@ -0,0 +1,13 @@
+import { a as SinkInputObject } from "../sink-CHQncb8H.mjs";
+
+//#region src/sink/helpers.d.ts
+/**
+ * Checks if the provided input is a {@link SinkInputObject}.
+ *
+ * @param input - The input to check.
+ * @returns True if the input is a {@link SinkInputObject}, false otherwise.
+ */
+declare function isSinkInputObject<TSpec, TOptions extends object, TReturns = void>(input: unknown): input is SinkInputObject<TSpec, TOptions, TReturns>;
+//#endregion
+export { isSinkInputObject };
+//# sourceMappingURL=helpers.d.mts.map

package/dist/sink/helpers.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"helpers.d.mts","names":[],"sources":["../../src/sink/helpers.ts"],"mappings":""}

package/dist/sink/helpers.mjs

@@ -0,0 +1,2 @@
+import{isSetObject as e}from"@stryke/type-checks/is-set-object";function t(t){return e(t)&&`sink`in t&&t.sink!==void 0}export{t as isSinkInputObject};
+//# sourceMappingURL=helpers.mjs.map

package/dist/sink/helpers.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"helpers.mjs","names":[],"sources":[],"mappings":""}

package/dist/sink/index.cjs

@@ -1 +1 @@
-Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("../extract-DUwG1ZUO.cjs");exports.VALID_SINK_FILE_EXTENSIONS=e.n,exports.extractSink=e.t;
+Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("./create.cjs");exports.createSink=e.createSink,exports.extractSinkMeta=e.extractSinkMeta;

package/dist/sink/index.d.cts

@@ -1,15 +1,2 @@
-import { a as SinkMeta, i as SinkInputWithMeta, n as SinkFunction, r as SinkInput, t as Sink } from "../types-B2MtSxCp.cjs";
-import { SchemaOf } from "@power-plant/schema/types";
-import { ResolveOptions } from "@power-plant/schema/resolve";
-
-//#region src/sink/constants.d.ts
-declare const VALID_SINK_FILE_EXTENSIONS: string[];
-//#endregion
-//#region src/sink/extract.d.ts
-/**
- * Normalizes any accepted sink input into a concrete sink descriptor.
- */
-declare function extractSink<TSpec, TOptions = never>(schema: SchemaOf<TSpec>, input: SinkInput<TSpec, TOptions>, options?: ResolveOptions): Promise<Sink<TSpec, TOptions>>;
-//#endregion
-export { type Sink, type SinkFunction, type SinkInput, type SinkInputWithMeta, type SinkMeta, VALID_SINK_FILE_EXTENSIONS, extractSink };
-//# sourceMappingURL=index.d.cts.map
+import { n as extractSinkMeta, t as createSink } from "../create-DAGPeYVI.cjs";
+export { createSink, extractSinkMeta };