notform 2.0.0-alpha.3 → 2.0.0-alpha.5

package/dist/index.d.ts

@@ -1,2731 +1,15 @@
 import * as _$vue from "vue";
-import { ComputedRef, MaybeRefOrGetter, Ref } from "vue";
+import { ComputedRef, MaybeRefOrGetter, Raw, Ref, useAttrs } from "vue";
 import { StandardSchemaV1 } from "@standard-schema/spec";
+import { Get, PartialDeep, Paths as Paths$1 } from "type-fest";
 
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/primitive.d.ts
-/**
-Matches any [primitive value](https://developer.mozilla.org/en-US/docs/Glossary/Primitive).
-
-@category Type
-*/
-type Primitive = null | undefined | string | number | boolean | symbol | bigint;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/characters.d.ts
-/**
-Matches any digit as a string ('0'-'9').
-
-@example
-```
-import type {DigitCharacter} from 'type-fest';
-
-const a: DigitCharacter = '0'; // Valid
-// @ts-expect-error
-const b: DigitCharacter = 0; // Invalid
-```
-
-@category Type
-*/
-type DigitCharacter = '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9';
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/is-any.d.ts
-/**
-Returns a boolean for whether the given type is `any`.
-
-@link https://stackoverflow.com/a/49928360/1490091
-
-Useful in type utilities, such as disallowing `any`s to be passed to a function.
-
-@example
-```
-import type {IsAny} from 'type-fest';
-
-const typedObject = {a: 1, b: 2} as const;
-const anyObject: any = {a: 1, b: 2};
-
-function get<O extends (IsAny<O> extends true ? {} : Record<string, number>), K extends keyof O = keyof O>(object: O, key: K) {
-	return object[key];
-}
-
-const typedA = get(typedObject, 'a');
-//=> 1
-
-const anyA = get(anyObject, 'a');
-//=> any
-```
-
-@category Type Guard
-@category Utilities
-*/
-type IsAny<T> = 0 extends 1 & NoInfer<T> ? true : false;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/is-optional-key-of.d.ts
-/**
-Returns a boolean for whether the given key is an optional key of type.
-
-This is useful when writing utility types or schema validators that need to differentiate `optional` keys.
-
-@example
-```
-import type {IsOptionalKeyOf} from 'type-fest';
-
-type User = {
-	name: string;
-	surname: string;
-
-	luckyNumber?: number;
-};
-
-type Admin = {
-	name: string;
-	surname?: string;
-};
-
-type T1 = IsOptionalKeyOf<User, 'luckyNumber'>;
-//=> true
-
-type T2 = IsOptionalKeyOf<User, 'name'>;
-//=> false
-
-type T3 = IsOptionalKeyOf<User, 'name' | 'luckyNumber'>;
-//=> boolean
-
-type T4 = IsOptionalKeyOf<User | Admin, 'name'>;
-//=> false
-
-type T5 = IsOptionalKeyOf<User | Admin, 'surname'>;
-//=> boolean
-```
-
-@category Type Guard
-@category Utilities
-*/
-type IsOptionalKeyOf<Type extends object, Key extends keyof Type> = IsAny<Type | Key> extends true ? never : Key extends keyof Type ? Type extends Record<Key, Type[Key]> ? false : true : false;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/optional-keys-of.d.ts
-/**
-Extract all optional keys from the given type.
-
-This is useful when you want to create a new type that contains different type values for the optional keys only.
-
-@example
-```
-import type {OptionalKeysOf, Except} from 'type-fest';
-
-type User = {
-	name: string;
-	surname: string;
-
-	luckyNumber?: number;
-};
-
-const REMOVE_FIELD = Symbol('remove field symbol');
-type UpdateOperation<Entity extends object> = Except<Partial<Entity>, OptionalKeysOf<Entity>> & {
-	[Key in OptionalKeysOf<Entity>]?: Entity[Key] | typeof REMOVE_FIELD;
-};
-
-const update1: UpdateOperation<User> = {
-	name: 'Alice',
-};
-
-const update2: UpdateOperation<User> = {
-	name: 'Bob',
-	luckyNumber: REMOVE_FIELD,
-};
-```
-
-@category Utilities
-*/
-type OptionalKeysOf<Type extends object> = Type extends unknown // For distributing `Type`
-? (keyof { [Key in keyof Type as IsOptionalKeyOf<Type, Key> extends false ? never : Key]: never }) & keyof Type // Intersect with `keyof Type` to ensure result of `OptionalKeysOf<Type>` is always assignable to `keyof Type`
-: never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/required-keys-of.d.ts
-/**
-Extract all required keys from the given type.
-
-This is useful when you want to create a new type that contains different type values for the required keys only or use the list of keys for validation purposes, etc...
-
-@example
-```
-import type {RequiredKeysOf} from 'type-fest';
-
-declare function createValidation<
-	Entity extends object,
-	Key extends RequiredKeysOf<Entity> = RequiredKeysOf<Entity>,
->(field: Key, validator: (value: Entity[Key]) => boolean): (entity: Entity) => boolean;
-
-type User = {
-	name: string;
-	surname: string;
-	luckyNumber?: number;
-};
-
-const validator1 = createValidation<User>('name', value => value.length < 25);
-const validator2 = createValidation<User>('surname', value => value.length < 25);
-
-// @ts-expect-error
-const validator3 = createValidation<User>('luckyNumber', value => value > 0);
-// Error: Argument of type '"luckyNumber"' is not assignable to parameter of type '"name" | "surname"'.
-```
-
-@category Utilities
-*/
-type RequiredKeysOf<Type extends object> = Type extends unknown // For distributing `Type`
-? Exclude<keyof Type, OptionalKeysOf<Type>> : never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/is-never.d.ts
-/**
-Returns a boolean for whether the given type is `never`.
-
-@link https://github.com/microsoft/TypeScript/issues/31751#issuecomment-498526919
-@link https://stackoverflow.com/a/53984913/10292952
-@link https://www.zhenghao.io/posts/ts-never
-
-Useful in type utilities, such as checking if something does not occur.
-
-@example
-```
-import type {IsNever, And} from 'type-fest';
-
-type A = IsNever<never>;
-//=> true
-
-type B = IsNever<any>;
-//=> false
-
-type C = IsNever<unknown>;
-//=> false
-
-type D = IsNever<never[]>;
-//=> false
-
-type E = IsNever<object>;
-//=> false
-
-type F = IsNever<string>;
-//=> false
-```
-
-@example
-```
-import type {IsNever} from 'type-fest';
-
-type IsTrue<T> = T extends true ? true : false;
-
-// When a distributive conditional is instantiated with `never`, the entire conditional results in `never`.
-type A = IsTrue<never>;
-//=> never
-
-// If you don't want that behaviour, you can explicitly add an `IsNever` check before the distributive conditional.
-type IsTrueFixed<T> =
-	IsNever<T> extends true ? false : T extends true ? true : false;
-
-type B = IsTrueFixed<never>;
-//=> false
-```
-
-@category Type Guard
-@category Utilities
-*/
-type IsNever<T> = [T] extends [never] ? true : false;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/if.d.ts
-/**
-An if-else-like type that resolves depending on whether the given `boolean` type is `true` or `false`.
-
-Use-cases:
-- You can use this in combination with `Is*` types to create an if-else-like experience. For example, `If<IsAny<any>, 'is any', 'not any'>`.
-
-Note:
-- Returns a union of if branch and else branch if the given type is `boolean` or `any`. For example, `If<boolean, 'Y', 'N'>` will return `'Y' | 'N'`.
-- Returns the else branch if the given type is `never`. For example, `If<never, 'Y', 'N'>` will return `'N'`.
-
-@example
-```
-import type {If} from 'type-fest';
-
-type A = If<true, 'yes', 'no'>;
-//=> 'yes'
-
-type B = If<false, 'yes', 'no'>;
-//=> 'no'
-
-type C = If<boolean, 'yes', 'no'>;
-//=> 'yes' | 'no'
-
-type D = If<any, 'yes', 'no'>;
-//=> 'yes' | 'no'
-
-type E = If<never, 'yes', 'no'>;
-//=> 'no'
-```
-
-@example
-```
-import type {If, IsAny, IsNever} from 'type-fest';
-
-type A = If<IsAny<unknown>, 'is any', 'not any'>;
-//=> 'not any'
-
-type B = If<IsNever<never>, 'is never', 'not never'>;
-//=> 'is never'
-```
-
-@example
-```
-import type {If, IsEqual} from 'type-fest';
-
-type IfEqual<T, U, IfBranch, ElseBranch> = If<IsEqual<T, U>, IfBranch, ElseBranch>;
-
-type A = IfEqual<string, string, 'equal', 'not equal'>;
-//=> 'equal'
-
-type B = IfEqual<string, number, 'equal', 'not equal'>;
-//=> 'not equal'
-```
-
-Note: Sometimes using the `If` type can make an implementation non–tail-recursive, which can impact performance. In such cases, it’s better to use a conditional directly. Refer to the following example:
-
-@example
-```
-import type {If, IsEqual, StringRepeat} from 'type-fest';
-
-type HundredZeroes = StringRepeat<'0', 100>;
-
-// The following implementation is not tail recursive
-type Includes<S extends string, Char extends string> =
-	S extends `${infer First}${infer Rest}`
-		? If<IsEqual<First, Char>,
-			'found',
-			Includes<Rest, Char>>
-		: 'not found';
-
-// Hence, instantiations with long strings will fail
-// @ts-expect-error
-type Fails = Includes<HundredZeroes, '1'>;
-//           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-// Error: Type instantiation is excessively deep and possibly infinite.
-
-// However, if we use a simple conditional instead of `If`, the implementation becomes tail-recursive
-type IncludesWithoutIf<S extends string, Char extends string> =
-	S extends `${infer First}${infer Rest}`
-		? IsEqual<First, Char> extends true
-			? 'found'
-			: IncludesWithoutIf<Rest, Char>
-		: 'not found';
-
-// Now, instantiations with long strings will work
-type Works = IncludesWithoutIf<HundredZeroes, '1'>;
-//=> 'not found'
-```
-
-@category Type Guard
-@category Utilities
-*/
-type If<Type extends boolean, IfBranch, ElseBranch> = IsNever<Type> extends true ? ElseBranch : Type extends true ? IfBranch : ElseBranch;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/unknown-array.d.ts
-/**
-Represents an array with `unknown` value.
-
-Use case: You want a type that all arrays can be assigned to, but you don't care about the value.
-
-@example
-```
-import type {UnknownArray} from 'type-fest';
-
-type IsArray<T> = T extends UnknownArray ? true : false;
-
-type A = IsArray<['foo']>;
-//=> true
-
-type B = IsArray<readonly number[]>;
-//=> true
-
-type C = IsArray<string>;
-//=> false
-```
-
-@category Type
-@category Array
-*/
-type UnknownArray = readonly unknown[];
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/internal/type.d.ts
-/**
-Matches any primitive, `void`, `Date`, or `RegExp` value.
-*/
-type BuiltIns = Primitive | void | Date | RegExp;
-/**
-Matches non-recursive types.
-*/
-type NonRecursiveType = BuiltIns | Function | (new (...arguments_: any[]) => unknown) | Promise<unknown>;
-/**
-Matches maps, sets, or arrays.
-*/
-type MapsSetsOrArrays = ReadonlyMap<unknown, unknown> | WeakMap<WeakKey, unknown> | ReadonlySet<unknown> | WeakSet<WeakKey> | UnknownArray;
-/**
-Test if the given function has multiple call signatures.
-
-Needed to handle the case of a single call signature with properties.
-
-Multiple call signatures cannot currently be supported due to a TypeScript limitation.
-@see https://github.com/microsoft/TypeScript/issues/29732
-*/
-type HasMultipleCallSignatures<T extends (...arguments_: any[]) => unknown> = T extends {
-  (...arguments_: infer A): unknown;
-  (...arguments_: infer B): unknown;
-} ? B extends A ? A extends B ? false : true : true : false;
-/**
-Returns a boolean for whether A is false.
-
-@example
-```
-type A = Not<true>;
-//=> false
-
-type B = Not<false>;
-//=> true
-```
-*/
-type Not<A extends boolean> = A extends true ? false : A extends false ? true : never;
-/**
-An if-else-like type that resolves depending on whether the given type is `any` or `never`.
-
-@example
-```
-// When `T` is a NOT `any` or `never` (like `string`) => Returns `IfNotAnyOrNever` branch
-type A = IfNotAnyOrNever<string, 'VALID', 'IS_ANY', 'IS_NEVER'>;
-//=> 'VALID'
-
-// When `T` is `any` => Returns `IfAny` branch
-type B = IfNotAnyOrNever<any, 'VALID', 'IS_ANY', 'IS_NEVER'>;
-//=> 'IS_ANY'
-
-// When `T` is `never` => Returns `IfNever` branch
-type C = IfNotAnyOrNever<never, 'VALID', 'IS_ANY', 'IS_NEVER'>;
-//=> 'IS_NEVER'
-```
-
-Note: Wrapping a tail-recursive type with `IfNotAnyOrNever` makes the implementation non-tail-recursive. To fix this, move the recursion into a helper type. Refer to the following example:
-
-@example
-```ts
-import type {StringRepeat} from 'type-fest';
-
-type NineHundredNinetyNineSpaces = StringRepeat<' ', 999>;
-
-// The following implementation is not tail recursive
-type TrimLeft<S extends string> = IfNotAnyOrNever<S, S extends ` ${infer R}` ? TrimLeft<R> : S>;
-
-// Hence, instantiations with long strings will fail
-// @ts-expect-error
-type T1 = TrimLeft<NineHundredNinetyNineSpaces>;
-//        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-// Error: Type instantiation is excessively deep and possibly infinite.
-
-// To fix this, move the recursion into a helper type
-type TrimLeftOptimised<S extends string> = IfNotAnyOrNever<S, _TrimLeftOptimised<S>>;
-
-type _TrimLeftOptimised<S extends string> = S extends ` ${infer R}` ? _TrimLeftOptimised<R> : S;
-
-type T2 = TrimLeftOptimised<NineHundredNinetyNineSpaces>;
-//=> ''
-```
-*/
-type IfNotAnyOrNever<T, IfNotAnyOrNever, IfAny = any, IfNever = never> = If<IsAny<T>, IfAny, If<IsNever<T>, IfNever, IfNotAnyOrNever>>;
-/**
-Indicates the value of `exactOptionalPropertyTypes` compiler option.
-*/
-type IsExactOptionalPropertyTypesEnabled = [(string | undefined)?] extends [string?] ? false : true;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/internal/array.d.ts
-/**
-Transforms a tuple type by replacing it's rest element with a single element that has the same type as the rest element, while keeping all the non-rest elements intact.
-
-@example
-```
-type A = CollapseRestElement<[string, string, ...number[]]>;
-//=> [string, string, number]
-
-type B = CollapseRestElement<[...string[], number, number]>;
-//=> [string, number, number]
-
-type C = CollapseRestElement<[string, string, ...Array<number | bigint>]>;
-//=> [string, string, number | bigint]
-
-type D = CollapseRestElement<[string, number]>;
-//=> [string, number]
-```
-
-Note: Optional modifiers (`?`) are removed from elements unless the `exactOptionalPropertyTypes` compiler option is disabled. When disabled, there's an additional `| undefined` for optional elements.
-
-@example
-```
-// `exactOptionalPropertyTypes` enabled
-type A = CollapseRestElement<[string?, string?, ...number[]]>;
-//=> [string, string, number]
-
-// `exactOptionalPropertyTypes` disabled
-type B = CollapseRestElement<[string?, string?, ...number[]]>;
-//=> [string | undefined, string | undefined, number]
-```
-*/
-type CollapseRestElement<TArray extends UnknownArray> = IfNotAnyOrNever<TArray, _CollapseRestElement<TArray>>;
-type _CollapseRestElement<TArray extends UnknownArray, ForwardAccumulator extends UnknownArray = [], BackwardAccumulator extends UnknownArray = []> = TArray extends UnknownArray // For distributing `TArray`
-? keyof TArray & `${number}` extends never // Enters this branch, if `TArray` is empty (e.g., []),
-// or `TArray` contains no non-rest elements preceding the rest element (e.g., `[...string[]]` or `[...string[], string]`).
-? TArray extends readonly [...infer Rest, infer Last] ? _CollapseRestElement<Rest, ForwardAccumulator, [Last, ...BackwardAccumulator]> // Accumulate elements that are present after the rest element.
-: TArray extends readonly [] ? [...ForwardAccumulator, ...BackwardAccumulator] : [...ForwardAccumulator, TArray[number], ...BackwardAccumulator] // Add the rest element between the accumulated elements.
-: TArray extends readonly [(infer First)?, ...infer Rest] ? _CollapseRestElement<Rest, [...ForwardAccumulator, '0' extends OptionalKeysOf<TArray> ? If<IsExactOptionalPropertyTypesEnabled, First, First | undefined> // Add `| undefined` for optional elements, if `exactOptionalPropertyTypes` is disabled.
-: First], BackwardAccumulator> : never // Should never happen, since `[(infer First)?, ...infer Rest]` is a top-type for arrays.
-: never; // Should never happen
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/numeric.d.ts
-type _Numeric = number | bigint;
-type Zero = 0 | 0n;
-/**
-Matches the hidden `Infinity` type.
-
-Please upvote [this issue](https://github.com/microsoft/TypeScript/issues/32277) if you want to have this type as a built-in in TypeScript.
-
-@see {@link NegativeInfinity}
-
-@category Numeric
-*/
-// See https://github.com/microsoft/TypeScript/issues/31752
-// eslint-disable-next-line no-loss-of-precision
-type PositiveInfinity = 1e999;
-/**
-Matches the hidden `-Infinity` type.
-
-Please upvote [this issue](https://github.com/microsoft/TypeScript/issues/32277) if you want to have this type as a built-in in TypeScript.
-
-@see {@link PositiveInfinity}
-
-@category Numeric
-*/
-// See https://github.com/microsoft/TypeScript/issues/31752
-// eslint-disable-next-line no-loss-of-precision
-type NegativeInfinity = -1e999;
-/**
-A negative `number`/`bigint` (`-∞ < x < 0`)
-
-Use-case: Validating and documenting parameters.
-
-@see {@link NegativeInteger}
-@see {@link NonNegative}
-
-@category Numeric
-*/
-type Negative<T extends _Numeric> = T extends Zero ? never : `${T}` extends `-${string}` ? T : never;
-/**
-Returns a boolean for whether the given number is a negative number.
-
-@see {@link Negative}
-
-@example
-```
-import type {IsNegative} from 'type-fest';
-
-type ShouldBeFalse = IsNegative<1>;
-type ShouldBeTrue = IsNegative<-1>;
-```
-
-@category Numeric
-*/
-type IsNegative<T extends _Numeric> = T extends Negative<T> ? true : false;
-//#endregion
-//#region ../../node_modules/.pnpm/tagged-tag@1.0.0/node_modules/tagged-tag/index.d.ts
-declare const tag: unique symbol;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/tagged.d.ts
-// eslint-disable-next-line type-fest/require-exported-types
-type TagContainer<Token> = {
-  readonly [tag]: Token;
-};
-type Tag<Token extends PropertyKey, TagMetadata> = TagContainer<{ [K in Token]: TagMetadata }>;
-/**
-Attach a "tag" to an arbitrary type. This allows you to create distinct types, that aren't assignable to one another, for distinct concepts in your program that should not be interchangeable, even if their runtime values have the same type. (See examples.)
-
-A type returned by `Tagged` can be passed to `Tagged` again, to create a type with multiple tags.
-
-[Read more about tagged types.](https://medium.com/@KevinBGreene/surviving-the-typescript-ecosystem-branding-and-type-tagging-6cf6e516523d)
-
-A tag's name is usually a string (and must be a string, number, or symbol), but each application of a tag can also contain an arbitrary type as its "metadata". See {@link GetTagMetadata} for examples and explanation.
-
-A type `A` returned by `Tagged` is assignable to another type `B` returned by `Tagged` if and only if:
-  - the underlying (untagged) type of `A` is assignable to the underlying type of `B`;
-	- `A` contains at least all the tags `B` has;
-	- and the metadata type for each of `A`'s tags is assignable to the metadata type of `B`'s corresponding tag.
-
-There have been several discussions about adding similar features to TypeScript. Unfortunately, nothing has (yet) moved forward:
-	- [Microsoft/TypeScript#202](https://github.com/microsoft/TypeScript/issues/202)
-	- [Microsoft/TypeScript#4895](https://github.com/microsoft/TypeScript/issues/4895)
-	- [Microsoft/TypeScript#33290](https://github.com/microsoft/TypeScript/pull/33290)
-
-@example
-```
-import type {Tagged} from 'type-fest';
-
-type AccountNumber = Tagged<number, 'AccountNumber'>;
-type AccountBalance = Tagged<number, 'AccountBalance'>;
-
-function createAccountNumber(): AccountNumber {
-	// As you can see, casting from a `number` (the underlying type being tagged) is allowed.
-	return 2 as AccountNumber;
-}
-
-declare function getMoneyForAccount(accountNumber: AccountNumber): AccountBalance;
-
-// This will compile successfully.
-getMoneyForAccount(createAccountNumber());
-
-// But this won't, because it has to be explicitly passed as an `AccountNumber` type!
-// Critically, you could not accidentally use an `AccountBalance` as an `AccountNumber`.
-// @ts-expect-error
-getMoneyForAccount(2);
-
-// You can also use tagged values like their underlying, untagged type.
-// I.e., this will compile successfully because an `AccountNumber` can be used as a regular `number`.
-// In this sense, the underlying base type is not hidden, which differentiates tagged types from opaque types in other languages.
-const accountNumber = createAccountNumber() + 2;
-```
-
-@example
-```
-import type {Tagged} from 'type-fest';
-
-// You can apply multiple tags to a type by using `Tagged` repeatedly.
-type Url = Tagged<string, 'URL'>;
-type SpecialCacheKey = Tagged<Url, 'SpecialCacheKey'>;
-
-// You can also pass a union of tag names, so this is equivalent to the above, although it doesn't give you the ability to assign distinct metadata to each tag.
-type SpecialCacheKey2 = Tagged<string, 'URL' | 'SpecialCacheKey'>;
-```
-
-@category Type
-*/
-type Tagged<Type, TagName extends PropertyKey, TagMetadata = never> = Type & Tag<TagName, TagMetadata>;
-/**
-Revert a tagged type back to its original type by removing all tags.
-
-Why is this necessary?
-
-1. Use a `Tagged` type as object keys
-2. Prevent TS4058 error: "Return type of exported function has or is using name X from external module Y but cannot be named"
-
-@example
-```
-import type {Tagged, UnwrapTagged} from 'type-fest';
-
-type AccountType = Tagged<'SAVINGS' | 'CHECKING', 'AccountType'>;
-
-const moneyByAccountType: Record<UnwrapTagged<AccountType>, number> = {
-	SAVINGS: 99,
-	CHECKING: 0.1,
-};
-
-// Without UnwrapTagged, the following expression would throw a type error.
-const money = moneyByAccountType.SAVINGS; // TS error: Property 'SAVINGS' does not exist
-
-// Attempting to pass a non-Tagged type to UnwrapTagged will raise a type error.
-// @ts-expect-error
-type WontWork = UnwrapTagged<string>;
-```
-
-@category Type
-*/
-type UnwrapTagged<TaggedType extends Tag<PropertyKey, any>> = RemoveAllTags<TaggedType>;
-type RemoveAllTags<T> = T extends Tag<PropertyKey, any> ? { [ThisTag in keyof T[typeof tag]]: T extends Tagged<infer Type, ThisTag, T[typeof tag][ThisTag]> ? RemoveAllTags<Type> : never }[keyof T[typeof tag]] : T;
-/**
-Note: The `Opaque` type is deprecated in favor of `Tagged`.
-
-Attach a "tag" to an arbitrary type. This allows you to create distinct types, that aren't assignable to one another, for runtime values that would otherwise have the same type. (See examples.)
-
-The generic type parameters can be anything.
-
-Note that `Opaque` is somewhat of a misnomer here, in that, unlike [some alternative implementations](https://github.com/microsoft/TypeScript/issues/4895#issuecomment-425132582), the original, untagged type is not actually hidden. (E.g., functions that accept the untagged type can still be called with the "opaque" version -- but not vice-versa.)
-
-Also note that this implementation is limited to a single tag. If you want to allow multiple tags, use `Tagged` instead.
-
-[Read more about tagged types.](https://medium.com/@KevinBGreene/surviving-the-typescript-ecosystem-branding-and-type-tagging-6cf6e516523d)
-
-There have been several discussions about adding similar features to TypeScript. Unfortunately, nothing has (yet) moved forward:
-	- [Microsoft/TypeScript#202](https://github.com/microsoft/TypeScript/issues/202)
-	- [Microsoft/TypeScript#15408](https://github.com/Microsoft/TypeScript/issues/15408)
-	- [Microsoft/TypeScript#15807](https://github.com/Microsoft/TypeScript/issues/15807)
-
-@example
-```
-import type {Opaque} from 'type-fest';
-
-type AccountNumber = Opaque<number, 'AccountNumber'>;
-type AccountBalance = Opaque<number, 'AccountBalance'>;
-
-// The `Token` parameter allows the compiler to differentiate between types, whereas "unknown" will not. For example, consider the following structures:
-type ThingOne = Opaque<string>;
-type ThingTwo = Opaque<string>;
-
-// To the compiler, these types are allowed to be cast to each other as they have the same underlying type. They are both `string & { __opaque__: unknown }`.
-// To avoid this behaviour, you would instead pass the "Token" parameter, like so.
-type NewThingOne = Opaque<string, 'ThingOne'>;
-type NewThingTwo = Opaque<string, 'ThingTwo'>;
-
-// Now they're completely separate types, so the following will fail to compile.
-function createNewThingOne(): NewThingOne {
-	// As you can see, casting from a string is still allowed. However, you may not cast NewThingOne to NewThingTwo, and vice versa.
-	return 'new thing one' as NewThingOne;
-}
-
-// This will fail to compile, as they are fundamentally different types.
-// @ts-expect-error
-const thingTwo = createNewThingOne() as NewThingTwo;
-
-// Here's another example of opaque typing.
-function createAccountNumber(): AccountNumber {
-	return 2 as AccountNumber;
-}
-
-declare function getMoneyForAccount(accountNumber: AccountNumber): AccountBalance;
-
-// This will compile successfully.
-getMoneyForAccount(createAccountNumber());
-
-// But this won't, because it has to be explicitly passed as an `AccountNumber` type.
-// @ts-expect-error
-getMoneyForAccount(2);
-
-// You can use opaque values like they aren't opaque too.
-const accountNumber = createAccountNumber();
-
-// This will compile successfully.
-const newAccountNumber = accountNumber + 2;
-
-// As a side note, you can (and should) use recursive types for your opaque types to make them stronger and hopefully easier to type.
-type Person = {
-	id: Opaque<number, Person>;
-	name: string;
-};
-```
-
-@category Type
-@deprecated Use {@link Tagged} instead
-*/
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/is-literal.d.ts
-/**
-Returns a boolean for whether the given type is a `string` [literal type](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#literal-types).
-
-Useful for:
-	- providing strongly-typed string manipulation functions
-	- constraining strings to be a string literal
-	- type utilities, such as when constructing parsers and ASTs
-
-The implementation of this type is inspired by the trick mentioned in this [StackOverflow answer](https://stackoverflow.com/a/68261113/420747).
-
-@example
-```
-import type {IsStringLiteral} from 'type-fest';
-
-type CapitalizedString<T extends string> = IsStringLiteral<T> extends true ? Capitalize<T> : string;
-
-// https://github.com/yankeeinlondon/native-dash/blob/master/src/capitalize.ts
-function capitalize<T extends Readonly<string>>(input: T): CapitalizedString<T> {
-	return (input.slice(0, 1).toUpperCase() + input.slice(1)) as CapitalizedString<T>;
-}
-
-const output = capitalize('hello, world!');
-//=> 'Hello, world!'
-```
-
-@example
-```
-// String types with infinite set of possible values return `false`.
-
-import type {IsStringLiteral} from 'type-fest';
-
-type AllUppercaseStrings = IsStringLiteral<Uppercase<string>>;
-//=> false
-
-type StringsStartingWithOn = IsStringLiteral<`on${string}`>;
-//=> false
-
-// This behaviour is particularly useful in string manipulation utilities, as infinite string types often require separate handling.
-
-type Length<S extends string, Counter extends never[] = []> =
-	IsStringLiteral<S> extends false
-		? number // return `number` for infinite string types
-		: S extends `${string}${infer Tail}`
-			? Length<Tail, [...Counter, never]>
-			: Counter['length'];
-
-type L1 = Length<Lowercase<string>>;
-//=> number
-
-type L2 = Length<`${number}`>;
-//=> number
-```
-
-@category Type Guard
-@category Utilities
-*/
-type IsStringLiteral<S> = IfNotAnyOrNever<S, _IsStringLiteral<CollapseLiterals<S extends TagContainer<any> ? UnwrapTagged<S> : S>>, false, false>;
-type _IsStringLiteral<S> = // If `T` is an infinite string type (e.g., `on${string}`), `Record<T, never>` produces an index signature,
-// and since `{}` extends index signatures, the result becomes `false`.
-S extends string ? {} extends Record<S, never> ? false : true : false;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/tuple-of.d.ts
-/**
-Create a tuple type of the specified length with elements of the specified type.
-
-@example
-```
-import type {TupleOf} from 'type-fest';
-
-type RGB = TupleOf<3, number>;
-//=> [number, number, number]
-
-type Line = TupleOf<2, {x: number; y: number}>;
-//=> [{x: number; y: number}, {x: number; y: number}]
-
-type TicTacToeBoard = TupleOf<3, TupleOf<3, 'X' | 'O' | null>>;
-//=> [['X' | 'O' | null, 'X' | 'O' | null, 'X' | 'O' | null], ['X' | 'O' | null, 'X' | 'O' | null, 'X' | 'O' | null], ['X' | 'O' | null, 'X' | 'O' | null, 'X' | 'O' | null]]
-```
-
-@example
-```
-import type {TupleOf} from 'type-fest';
-
-type Range<Start extends number, End extends number> = Exclude<keyof TupleOf<End>, keyof TupleOf<Start>>;
-
-type ZeroToFour = Range<0, 5>;
-//=> '0' | '1' | '2' | '3' | '4'
-
-type ThreeToEight = Range<3, 9>;
-//=> '5' | '3' | '4' | '6' | '7' | '8'
-```
-
-Note: If the specified length is the non-literal `number` type, the result will not be a tuple but a regular array.
-
-@example
-```
-import type {TupleOf} from 'type-fest';
-
-type StringArray = TupleOf<number, string>;
-//=> string[]
-```
-
-Note: If the type for elements is not specified, it will default to `unknown`.
-
-@example
-```
-import type {TupleOf} from 'type-fest';
-
-type UnknownTriplet = TupleOf<3>;
-//=> [unknown, unknown, unknown]
-```
-
-Note: If the specified length is negative, the result will be an empty tuple.
-
-@example
-```
-import type {TupleOf} from 'type-fest';
-
-type EmptyTuple = TupleOf<-3, string>;
-//=> []
-```
-
-Note: If you need a readonly tuple, simply wrap this type with `Readonly`, for example, to create `readonly [number, number, number]` use `Readonly<TupleOf<3, number>>`.
-
-@category Array
-*/
-type TupleOf<Length extends number, Fill = unknown> = IfNotAnyOrNever<Length, _TupleOf<If<IsNegative<Length>, 0, Length>, Fill, []>, Fill[], []>;
-type _TupleOf<L extends number, Fill, Accumulator extends UnknownArray> = number extends L ? Fill[] : L extends Accumulator['length'] ? Accumulator : _TupleOf<L, Fill, [...Accumulator, Fill]>;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/internal/string.d.ts
-/**
-Return a string representation of the given string or number.
-
-Note: This type is not the return type of the `.toString()` function.
-*/
-type ToString<T> = T extends string | number ? `${T}` : never;
-/**
-Converts a numeric string to a number.
-
-@example
-```
-type PositiveInt = StringToNumber<'1234'>;
-//=> 1234
-
-type NegativeInt = StringToNumber<'-1234'>;
-//=> -1234
-
-type PositiveFloat = StringToNumber<'1234.56'>;
-//=> 1234.56
-
-type NegativeFloat = StringToNumber<'-1234.56'>;
-//=> -1234.56
-
-type PositiveInfinity = StringToNumber<'Infinity'>;
-//=> Infinity
-
-type NegativeInfinity = StringToNumber<'-Infinity'>;
-//=> -Infinity
-```
-
-@category String
-@category Numeric
-@category Template literal
-*/
-type StringToNumber<S extends string> = S extends `${infer N extends number}` ? N : S extends 'Infinity' ? PositiveInfinity : S extends '-Infinity' ? NegativeInfinity : never;
-/**
-Returns an array of the characters of the string.
-
-@example
-```
-type A = StringToArray<'abcde'>;
-//=> ['a', 'b', 'c', 'd', 'e']
-
-type B = StringToArray<string>;
-//=> never
-```
-
-@category String
-*/
-type StringToArray<S extends string, Result extends string[] = []> = string extends S ? never : S extends `${infer F}${infer R}` ? StringToArray<R, [...Result, F]> : Result;
-/**
-Returns the length of the given string.
-
-@example
-```
-type A = StringLength<'abcde'>;
-//=> 5
-
-type B = StringLength<string>;
-//=> never
-```
-
-@category String
-@category Template literal
-*/
-type StringLength<S extends string> = string extends S ? never : StringToArray<S>['length'];
-/**
-Returns a boolean for whether `A` represents a number greater than `B`, where `A` and `B` are both numeric strings and have the same length.
-
-@example
-```
-type A = SameLengthPositiveNumericStringGt<'50', '10'>;
-//=> true
-
-type B = SameLengthPositiveNumericStringGt<'10', '10'>;
-//=> false
-```
-*/
-type SameLengthPositiveNumericStringGt<A extends string, B extends string> = A extends `${infer FirstA}${infer RestA}` ? B extends `${infer FirstB}${infer RestB}` ? FirstA extends FirstB ? SameLengthPositiveNumericStringGt<RestA, RestB> : PositiveNumericCharacterGt<FirstA, FirstB> : never : false;
-type NumericString = '0123456789';
-/**
-Returns a boolean for whether `A` is greater than `B`, where `A` and `B` are both positive numeric strings.
-
-@example
-```
-type A = PositiveNumericStringGt<'500', '1'>;
-//=> true
-
-type B = PositiveNumericStringGt<'1', '1'>;
-//=> false
-
-type C = PositiveNumericStringGt<'1', '500'>;
-//=> false
-```
-*/
-type PositiveNumericStringGt<A extends string, B extends string> = A extends B ? false : [TupleOf<StringLength<A>, 0>, TupleOf<StringLength<B>, 0>] extends infer R extends [readonly unknown[], readonly unknown[]] ? R[0] extends [...R[1], ...infer Remain extends readonly unknown[]] ? 0 extends Remain['length'] ? SameLengthPositiveNumericStringGt<A, B> : true : false : never;
-/**
-Returns a boolean for whether `A` represents a number greater than `B`, where `A` and `B` are both positive numeric characters.
-
-@example
-```
-type A = PositiveNumericCharacterGt<'5', '1'>;
-//=> true
-
-type B = PositiveNumericCharacterGt<'1', '1'>;
-//=> false
-```
-*/
-type PositiveNumericCharacterGt<A extends string, B extends string> = NumericString extends `${infer HeadA}${A}${infer TailA}` ? NumericString extends `${infer HeadB}${B}${infer TailB}` ? HeadA extends `${HeadB}${infer _}${infer __}` ? true : false : never : never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/internal/numeric.d.ts
-/**
-Returns the absolute value of a given value.
-
-@example
-```
-type A = NumberAbsolute<-1>;
-//=> 1
-
-type B = NumberAbsolute<1>;
-//=> 1
-
-type C = NumberAbsolute<NegativeInfinity>;
-//=> PositiveInfinity
-```
-*/
-type NumberAbsolute<N extends number> = `${N}` extends `-${infer StringPositiveN}` ? StringToNumber<StringPositiveN> : N;
-/**
-Check whether the given type is a number or a number string.
-
-Supports floating-point as a string.
-
-@example
-```
-type A = IsNumberLike<'1'>;
-//=> true
-
-type B = IsNumberLike<'-1.1'>;
-//=> true
-
-type C = IsNumberLike<'5e-20'>;
-//=> true
-
-type D = IsNumberLike<1>;
-//=> true
-
-type E = IsNumberLike<'a'>;
-//=> false
-*/
-type IsNumberLike<N> = IfNotAnyOrNever<N, N extends number | `${number}` ? true : false, boolean, false>;
-/**
-Returns the number with reversed sign.
-
-@example
-```
-type A = ReverseSign<-1>;
-//=> 1
-
-type B = ReverseSign<1>;
-//=> -1
-
-type C = ReverseSign<NegativeInfinity>;
-//=> PositiveInfinity
-
-type D = ReverseSign<PositiveInfinity>;
-//=> NegativeInfinity
-```
-*/
-type ReverseSign<N extends number> = // Handle edge cases
-N extends 0 ? 0 : N extends PositiveInfinity ? NegativeInfinity : N extends NegativeInfinity ? PositiveInfinity : // Handle negative numbers
-`${N}` extends `-${infer P extends number}` ? P // Handle positive numbers
-: `-${N}` extends `${infer R extends number}` ? R : never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/simplify.d.ts
-/**
-Useful to flatten the type output to improve type hints shown in editors. And also to transform an interface into a type to aide with assignability.
-
-@example
-```
-import type {Simplify} from 'type-fest';
-
-type PositionProps = {
-	top: number;
-	left: number;
-};
-
-type SizeProps = {
-	width: number;
-	height: number;
-};
-
-// In your editor, hovering over `Props` will show a flattened object with all the properties.
-type Props = Simplify<PositionProps & SizeProps>;
-```
-
-Sometimes it is desired to pass a value as a function argument that has a different type. At first inspection it may seem assignable, and then you discover it is not because the `value`'s type definition was defined as an interface. In the following example, `fn` requires an argument of type `Record<string, unknown>`. If the value is defined as a literal, then it is assignable. And if the `value` is defined as type using the `Simplify` utility the value is assignable.  But if the `value` is defined as an interface, it is not assignable because the interface is not sealed and elsewhere a non-string property could be added to the interface.
-
-If the type definition must be an interface (perhaps it was defined in a third-party npm package), then the `value` can be defined as `const value: Simplify<SomeInterface> = ...`. Then `value` will be assignable to the `fn` argument.  Or the `value` can be cast as `Simplify<SomeInterface>` if you can't re-declare the `value`.
-
-@example
-```
-import type {Simplify} from 'type-fest';
-
-interface SomeInterface {
-	foo: number;
-	bar?: string;
-	baz: number | undefined;
-}
-
-type SomeType = {
-	foo: number;
-	bar?: string;
-	baz: number | undefined;
-};
-
-const literal = {foo: 123, bar: 'hello', baz: 456};
-const someType: SomeType = literal;
-const someInterface: SomeInterface = literal;
-
-declare function fn(object: Record<string, unknown>): void;
-
-fn(literal); // Good: literal object type is sealed
-fn(someType); // Good: type is sealed
-// @ts-expect-error
-fn(someInterface); // Error: Index signature for type 'string' is missing in type 'someInterface'. Because `interface` can be re-opened
-fn(someInterface as Simplify<SomeInterface>); // Good: transform an `interface` into a `type`
-```
-
-@link https://github.com/microsoft/TypeScript/issues/15300
-@see {@link SimplifyDeep}
-@category Object
-*/
-type Simplify<T> = { [KeyType in keyof T]: T[KeyType] } & {};
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/is-equal.d.ts
-/**
-Returns a boolean for whether the two given types are equal.
-
-@link https://github.com/microsoft/TypeScript/issues/27024#issuecomment-421529650
-@link https://stackoverflow.com/questions/68961864/how-does-the-equals-work-in-typescript/68963796#68963796
-
-Use-cases:
-- If you want to make a conditional branch based on the result of a comparison of two types.
-
-@example
-```
-import type {IsEqual} from 'type-fest';
-
-// This type returns a boolean for whether the given array includes the given item.
-// `IsEqual` is used to compare the given array at position 0 and the given item and then return true if they are equal.
-type Includes<Value extends readonly any[], Item> =
-	Value extends readonly [Value[0], ...infer rest]
-		? IsEqual<Value[0], Item> extends true
-			? true
-			: Includes<rest, Item>
-		: false;
-```
-
-@category Type Guard
-@category Utilities
-*/
-type IsEqual<A, B> = [A] extends [B] ? [B] extends [A] ? _IsEqual<A, B> : false : false;
-// This version fails the `equalWrappedTupleIntersectionToBeNeverAndNeverExpanded` test in `test-d/is-equal.ts`.
-type _IsEqual<A, B> = (<G>() => G extends A & G | G ? 1 : 2) extends (<G>() => G extends B & G | G ? 1 : 2) ? true : false;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/omit-index-signature.d.ts
-/**
-Omit any index signatures from the given object type, leaving only explicitly defined properties.
-
-This is the counterpart of `PickIndexSignature`.
-
-Use-cases:
-- Remove overly permissive signatures from third-party types.
-
-This type was taken from this [StackOverflow answer](https://stackoverflow.com/a/68261113/420747).
-
-It relies on the fact that an empty object (`{}`) is assignable to an object with just an index signature, like `Record<string, unknown>`, but not to an object with explicitly defined keys, like `Record<'foo' | 'bar', unknown>`.
-
-(The actual value type, `unknown`, is irrelevant and could be any type. Only the key type matters.)
-
-```
-const indexed: Record<string, unknown> = {}; // Allowed
-
-// @ts-expect-error
-const keyed: Record<'foo', unknown> = {}; // Error
-// TS2739: Type '{}' is missing the following properties from type 'Record<"foo" | "bar", unknown>': foo, bar
-```
-
-Instead of causing a type error like the above, you can also use a [conditional type](https://www.typescriptlang.org/docs/handbook/2/conditional-types.html) to test whether a type is assignable to another:
-
-```
-type Indexed = {} extends Record<string, unknown>
-	? '✅ `{}` is assignable to `Record<string, unknown>`'
-	: '❌ `{}` is NOT assignable to `Record<string, unknown>`';
-
-type IndexedResult = Indexed;
-//=> '✅ `{}` is assignable to `Record<string, unknown>`'
-
-type Keyed = {} extends Record<'foo' | 'bar', unknown>
-	? '✅ `{}` is assignable to `Record<\'foo\' | \'bar\', unknown>`'
-	: '❌ `{}` is NOT assignable to `Record<\'foo\' | \'bar\', unknown>`';
-
-type KeyedResult = Keyed;
-//=> '❌ `{}` is NOT assignable to `Record<\'foo\' | \'bar\', unknown>`'
-```
-
-Using a [mapped type](https://www.typescriptlang.org/docs/handbook/2/mapped-types.html#further-exploration), you can then check for each `KeyType` of `ObjectType`...
-
-```
-type OmitIndexSignature<ObjectType> = {
-	[KeyType in keyof ObjectType // Map each key of `ObjectType`...
-	]: ObjectType[KeyType]; // ...to its original value, i.e. `OmitIndexSignature<Foo> == Foo`.
-};
-```
-
-...whether an empty object (`{}`) would be assignable to an object with that `KeyType` (`Record<KeyType, unknown>`)...
-
-```
-type OmitIndexSignature<ObjectType> = {
-	[KeyType in keyof ObjectType
-	// Is `{}` assignable to `Record<KeyType, unknown>`?
-	as {} extends Record<KeyType, unknown>
-		? never // ✅ `{}` is assignable to `Record<KeyType, unknown>`
-		: KeyType // ❌ `{}` is NOT assignable to `Record<KeyType, unknown>`
-	]: ObjectType[KeyType];
-};
-```
-
-If `{}` is assignable, it means that `KeyType` is an index signature and we want to remove it. If it is not assignable, `KeyType` is a "real" key and we want to keep it.
-
-@example
-```
-import type {OmitIndexSignature} from 'type-fest';
-
-type Example = {
-	// These index signatures will be removed.
-	[x: string]: any;
-	[x: number]: any;
-	[x: symbol]: any;
-	[x: `head-${string}`]: string;
-	[x: `${string}-tail`]: string;
-	[x: `head-${string}-tail`]: string;
-	[x: `${bigint}`]: string;
-	[x: `embedded-${number}`]: string;
-
-	// These explicitly defined keys will remain.
-	foo: 'bar';
-	qux?: 'baz';
-};
-
-type ExampleWithoutIndexSignatures = OmitIndexSignature<Example>;
-//=> {foo: 'bar'; qux?: 'baz'}
-```
-
-@see {@link PickIndexSignature}
-@category Object
-*/
-type OmitIndexSignature<ObjectType> = { [KeyType in keyof ObjectType as {} extends Record<KeyType, unknown> ? never : KeyType]: ObjectType[KeyType] };
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/pick-index-signature.d.ts
-/**
-Pick only index signatures from the given object type, leaving out all explicitly defined properties.
-
-This is the counterpart of `OmitIndexSignature`.
-
-@example
-```
-import type {PickIndexSignature} from 'type-fest';
-
-declare const symbolKey: unique symbol;
-
-type Example = {
-	// These index signatures will remain.
-	[x: string]: unknown;
-	[x: number]: unknown;
-	[x: symbol]: unknown;
-	[x: `head-${string}`]: string;
-	[x: `${string}-tail`]: string;
-	[x: `head-${string}-tail`]: string;
-	[x: `${bigint}`]: string;
-	[x: `embedded-${number}`]: string;
-
-	// These explicitly defined keys will be removed.
-	['kebab-case-key']: string;
-	[symbolKey]: string;
-	foo: 'bar';
-	qux?: 'baz';
-};
-
-type ExampleIndexSignature = PickIndexSignature<Example>;
-// {
-// 	[x: string]: unknown;
-// 	[x: number]: unknown;
-// 	[x: symbol]: unknown;
-// 	[x: `head-${string}`]: string;
-// 	[x: `${string}-tail`]: string;
-// 	[x: `head-${string}-tail`]: string;
-// 	[x: `${bigint}`]: string;
-// 	[x: `embedded-${number}`]: string;
-// }
-```
-
-@see {@link OmitIndexSignature}
-@category Object
-*/
-type PickIndexSignature<ObjectType> = { [KeyType in keyof ObjectType as {} extends Record<KeyType, unknown> ? KeyType : never]: ObjectType[KeyType] };
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/merge.d.ts
-// Merges two objects without worrying about index signatures.
-type SimpleMerge<Destination, Source> = Simplify<{ [Key in keyof Destination as Key extends keyof Source ? never : Key]: Destination[Key] } & Source>;
-/**
-Merge two types into a new type. Keys of the second type overrides keys of the first type.
-
-This is different from the TypeScript `&` (intersection) operator. With `&`, conflicting property types are intersected, which often results in `never`. For example, `{a: string} & {a: number}` makes `a` become `string & number`, which resolves to `never`. With `Merge`, the second type's keys cleanly override the first, so `Merge<{a: string}, {a: number}>` gives `{a: number}` as expected. `Merge` also produces a flattened type (via `Simplify`), making it more readable in IDE tooltips compared to `A & B`.
-
-@example
-```
-import type {Merge} from 'type-fest';
-
-type Foo = {
-	a: string;
-	b: number;
-};
-
-type Bar = {
-	a: number; // Conflicts with Foo['a']
-	c: boolean;
-};
-
-// With `&`, `a` becomes `string & number` which is `never`. Not what you want.
-type WithIntersection = (Foo & Bar)['a'];
-//=> never
-
-// With `Merge`, `a` is cleanly overridden to `number`.
-type WithMerge = Merge<Foo, Bar>['a'];
-//=> number
-```
-
-@example
-```
-import type {Merge} from 'type-fest';
-
-type Foo = {
-	[x: string]: unknown;
-	[x: number]: unknown;
-	foo: string;
-	bar: symbol;
-};
-
-type Bar = {
-	[x: number]: number;
-	[x: symbol]: unknown;
-	bar: Date;
-	baz: boolean;
-};
-
-export type FooBar = Merge<Foo, Bar>;
-//=> {
-// 	[x: string]: unknown;
-// 	[x: number]: number;
-// 	[x: symbol]: unknown;
-// 	foo: string;
-// 	bar: Date;
-// 	baz: boolean;
-// }
-```
-
-Note: If you want a merge type that more accurately reflects the runtime behavior of object spread or `Object.assign`, refer to the {@link ObjectMerge} type.
-
-@see {@link ObjectMerge}
-@category Object
-*/
-type Merge<Destination, Source> = Destination extends unknown // For distributing `Destination`
-? Source extends unknown // For distributing `Source`
-? If<IsEqual<Destination, Source>, Destination, _Merge<Destination, Source>> : never // Should never happen
-: never;
-// Should never happen
-type _Merge<Destination, Source> = Simplify<SimpleMerge<PickIndexSignature<Destination>, PickIndexSignature<Source>> & SimpleMerge<OmitIndexSignature<Destination>, OmitIndexSignature<Source>>>;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/internal/object.d.ts
-/**
-Merges user specified options with default options.
-
-@example
-```
-type PathsOptions = {maxRecursionDepth?: number; leavesOnly?: boolean};
-type DefaultPathsOptions = {maxRecursionDepth: 10; leavesOnly: false};
-type SpecifiedOptions = {leavesOnly: true};
-
-type Result = ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, SpecifiedOptions>;
-//=> {maxRecursionDepth: 10; leavesOnly: true}
-```
-
-@example
-```
-// Complains if default values are not provided for optional options
-
-type PathsOptions = {maxRecursionDepth?: number; leavesOnly?: boolean};
-type DefaultPathsOptions = {maxRecursionDepth: 10};
-type SpecifiedOptions = {};
-
-type Result = ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, SpecifiedOptions>;
-//                                              ~~~~~~~~~~~~~~~~~~~
-// Property 'leavesOnly' is missing in type 'DefaultPathsOptions' but required in type '{ maxRecursionDepth: number; leavesOnly: boolean; }'.
-```
-
-@example
-```
-// Complains if an option's default type does not conform to the expected type
-
-type PathsOptions = {maxRecursionDepth?: number; leavesOnly?: boolean};
-type DefaultPathsOptions = {maxRecursionDepth: 10; leavesOnly: 'no'};
-type SpecifiedOptions = {};
-
-type Result = ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, SpecifiedOptions>;
-//                                              ~~~~~~~~~~~~~~~~~~~
-// Types of property 'leavesOnly' are incompatible. Type 'string' is not assignable to type 'boolean'.
-```
-
-@example
-```
-// Complains if an option's specified type does not conform to the expected type
-
-type PathsOptions = {maxRecursionDepth?: number; leavesOnly?: boolean};
-type DefaultPathsOptions = {maxRecursionDepth: 10; leavesOnly: false};
-type SpecifiedOptions = {leavesOnly: 'yes'};
-
-type Result = ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, SpecifiedOptions>;
-//                                                                   ~~~~~~~~~~~~~~~~
-// Types of property 'leavesOnly' are incompatible. Type 'string' is not assignable to type 'boolean'.
-```
-*/
-type ApplyDefaultOptions<Options extends object, Defaults extends Simplify<Omit<Required<Options>, RequiredKeysOf<Options>> & Partial<Record<RequiredKeysOf<Options>, never>>>, SpecifiedOptions extends Options> = If<IsAny<SpecifiedOptions>, Defaults, If<IsNever<SpecifiedOptions>, Defaults, Simplify<Merge<Defaults, { [Key in keyof SpecifiedOptions as Key extends OptionalKeysOf<Options> ? undefined extends SpecifiedOptions[Key] ? never : Key : Key]: SpecifiedOptions[Key] }> & Required<Options>>>>;
-// `& Required<Options>` ensures that `ApplyDefaultOptions<SomeOption, ...>` is always assignable to `Required<SomeOption>`
-/**
-Collapses literal types in a union into their corresponding primitive types, when possible. For example, `CollapseLiterals<'foo' | 'bar' | (string & {})>` returns `string`.
-
-Note: This doesn't collapse literals within tagged types. For example, `CollapseLiterals<Tagged<'foo' | (string & {}), 'Tag'>>` returns `("foo" & Tag<"Tag", never>) | (string & Tag<"Tag", never>)` and not `string & Tag<"Tag", never>`.
-
-Use-case: For collapsing unions created using {@link LiteralUnion}.
-
-@example
-```
-import type {LiteralUnion} from 'type-fest';
-
-type A = CollapseLiterals<'foo' | 'bar' | (string & {})>;
-//=> string
-
-type B = CollapseLiterals<LiteralUnion<1 | 2 | 3, number>>;
-//=> number
-
-type C = CollapseLiterals<LiteralUnion<'onClick' | 'onChange', `on${string}`>>;
-//=> `on${string}`
-
-type D = CollapseLiterals<'click' | 'change' | (`on${string}` & {})>;
-//=> 'click' | 'change' | `on${string}`
-
-type E = CollapseLiterals<LiteralUnion<'foo' | 'bar', string> | null | undefined>;
-//=> string | null | undefined
-```
-*/
-type CollapseLiterals<T> = {} extends T ? T : T extends infer U & {} ? U : T;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/some-extend.d.ts
-/**
-@see {@link SomeExtend}
-*/
-type SomeExtendOptions = {
-  /**
-  Consider `never` elements to match the target type only if the target type itself is `never` (or `any`).
-  	- When set to `true` (default), `never` is _not_ treated as a bottom type, instead, it is treated as a type that matches only itself (or `any`).
-  - When set to `false`, `never` is treated as a bottom type, and behaves as it normally would.
-  	@default true
-  	@example
-  ```
-  import type {SomeExtend} from 'type-fest';
-  	type A = SomeExtend<[1, 2, never], string, {strictNever: true}>;
-  //=> false
-  	type B = SomeExtend<[1, 2, never], string, {strictNever: false}>;
-  //=> true
-  	type C = SomeExtend<[1, never], never, {strictNever: true}>;
-  //=> true
-  	type D = SomeExtend<[1, never], never, {strictNever: false}>;
-  //=> true
-  	type E = SomeExtend<[never], any, {strictNever: true}>;
-  //=> true
-  	type F = SomeExtend<[never], any, {strictNever: false}>;
-  //=> true
-  ```
-  */
-  strictNever?: boolean;
-};
-type DefaultSomeExtendOptions = {
-  strictNever: true;
-};
-/**
-Returns a boolean for whether some element in an array type extends another type.
-
-@example
-```
-import type {SomeExtend} from 'type-fest';
-
-type A = SomeExtend<['1', '2', 3], number>;
-//=> true
-
-type B = SomeExtend<[1, 2, 3], string>;
-//=> false
-
-type C = SomeExtend<[string, number | string], number>;
-//=> boolean
-
-type D = SomeExtend<[true, boolean, true], false>;
-//=> boolean
-```
-
-Note: Behaviour of optional elements depend on the `exactOptionalPropertyTypes` compiler option. When the option is disabled, the target type must include `undefined` for a successful match.
-
-```
-// @exactOptionalPropertyTypes: true
-import type {SomeExtend} from 'type-fest';
-
-type A = SomeExtend<[1?, 2?, '3'?], string>;
-//=> true
-```
-
-```
-// @exactOptionalPropertyTypes: false
-import type {SomeExtend} from 'type-fest';
-
-type A = SomeExtend<[1?, 2?, '3'?], string>;
-//=> boolean
-
-type B = SomeExtend<[1?, 2?, '3'?], string | undefined>;
-//=> true
-```
-
-@see {@link SomeExtendOptions}
-
-@category Utilities
-@category Array
-*/
-type SomeExtend<TArray extends UnknownArray, Type, Options extends SomeExtendOptions = {}> = _SomeExtend<CollapseRestElement<TArray>, Type, ApplyDefaultOptions<SomeExtendOptions, DefaultSomeExtendOptions, Options>>;
-type _SomeExtend<TArray extends UnknownArray, Type, Options extends Required<SomeExtendOptions>> = IfNotAnyOrNever<TArray, TArray extends readonly [infer First, ...infer Rest] ? IsNever<First> extends true ? Or<Or<IsNever<Type>, IsAny<Type>>, Not<Options['strictNever']>> extends true // If target `Type` is also `never`, or is `any`, or `strictNever` is disabled, return `true`.
-? true : _SomeExtend<Rest, Type, Options> : First extends Type ? true : _SomeExtend<Rest, Type, Options> : false, false, false>;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/or-all.d.ts
-/**
-Returns a boolean for whether any of the given elements is `true`.
-
-Use-cases:
-- Check if at least one condition in a list of booleans is met.
-
-@example
-```
-import type {OrAll} from 'type-fest';
-
-type FFT = OrAll<[false, false, true]>;
-//=> true
-
-type FFF = OrAll<[false, false, false]>;
-//=> false
-```
-
-Note: When `boolean` is passed as an element, it is distributed into separate cases, and the final result is a union of those cases.
-For example, `OrAll<[false, boolean]>` expands to `OrAll<[false, true]> | OrAll<[false, false]>`, which simplifies to `true | false` (i.e., `boolean`).
-
-@example
-```
-import type {OrAll} from 'type-fest';
-
-type A = OrAll<[false, boolean]>;
-//=> boolean
-
-type B = OrAll<[true, boolean]>;
-//=> true
-```
-
-Note: If `never` is passed as an element, it is treated as `false` and the result is computed accordingly.
-
-@example
-```
-import type {OrAll} from 'type-fest';
-
-type A = OrAll<[never, never, true]>;
-//=> true
-
-type B = OrAll<[never, never, false]>;
-//=> false
-
-type C = OrAll<[never, never, never]>;
-//=> false
-
-type D = OrAll<[never, never, boolean]>;
-//=> boolean
-```
-
-Note: If `any` is passed as an element, it is treated as `boolean` and the result is computed accordingly.
-
-@example
-```
-import type {OrAll} from 'type-fest';
-
-type A = OrAll<[false, any]>;
-//=> boolean
-
-type B = OrAll<[true, any]>;
-//=> true
-```
-
-Note: `OrAll<[]>` evaluates to `false` because there are no `true` elements in an empty tuple. See [Wikipedia: Clause (logic) > Empty clauses](https://en.wikipedia.org/wiki/Clause_(logic)#Empty_clauses:~:text=The%20truth%20evaluation%20of%20an%20empty%20disjunctive%20clause%20is%20always%20false.).
-
-@see {@link Or}
-@see {@link AndAll}
-*/
-type OrAll<T extends readonly boolean[]> = SomeExtend<T, true>;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/or.d.ts
-/**
-Returns a boolean for whether either of two given types is true.
-
-Use-case: Constructing complex conditional types where at least one condition must be satisfied.
-
-@example
-```
-import type {Or} from 'type-fest';
-
-type TT = Or<true, true>;
-//=> true
-
-type TF = Or<true, false>;
-//=> true
-
-type FT = Or<false, true>;
-//=> true
-
-type FF = Or<false, false>;
-//=> false
-```
-
-Note: When `boolean` is passed as an argument, it is distributed into separate cases, and the final result is a union of those cases.
-For example, `Or<false, boolean>` expands to `Or<false, true> | Or<false, false>`, which simplifies to `true | false` (i.e., `boolean`).
-
-@example
-```
-import type {Or} from 'type-fest';
-
-type A = Or<false, boolean>;
-//=> boolean
-
-type B = Or<boolean, false>;
-//=> boolean
-
-type C = Or<true, boolean>;
-//=> true
-
-type D = Or<boolean, true>;
-//=> true
-
-type E = Or<boolean, boolean>;
-//=> boolean
-```
-
-Note: If `never` is passed as an argument, it is treated as `false` and the result is computed accordingly.
-
-@example
-```
-import type {Or} from 'type-fest';
-
-type A = Or<true, never>;
-//=> true
-
-type B = Or<never, true>;
-//=> true
-
-type C = Or<false, never>;
-//=> false
-
-type D = Or<never, false>;
-//=> false
-
-type E = Or<boolean, never>;
-//=> boolean
-
-type F = Or<never, boolean>;
-//=> boolean
-
-type G = Or<never, never>;
-//=> false
-```
-
-@see {@link OrAll}
-@see {@link And}
-@see {@link Xor}
-*/
-type Or<A extends boolean, B extends boolean> = OrAll<[A, B]>;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/all-extend.d.ts
-/**
-@see {@link AllExtend}
-*/
-type AllExtendOptions = {
-  /**
-  Consider `never` elements to match the target type only if the target type itself is `never` (or `any`).
-  	- When set to `true` (default), `never` is _not_ treated as a bottom type, instead, it is treated as a type that matches only itself (or `any`).
-  - When set to `false`, `never` is treated as a bottom type, and behaves as it normally would.
-  	@default true
-  	@example
-  ```
-  import type {AllExtend} from 'type-fest';
-  	type A = AllExtend<[1, 2, never], number, {strictNever: true}>;
-  //=> false
-  	type B = AllExtend<[1, 2, never], number, {strictNever: false}>;
-  //=> true
-  	type C = AllExtend<[never, never], never, {strictNever: true}>;
-  //=> true
-  	type D = AllExtend<[never, never], never, {strictNever: false}>;
-  //=> true
-  	type E = AllExtend<['a', 'b', never], any, {strictNever: true}>;
-  //=> true
-  	type F = AllExtend<['a', 'b', never], any, {strictNever: false}>;
-  //=> true
-  	type G = AllExtend<[never, 1], never, {strictNever: true}>;
-  //=> false
-  	type H = AllExtend<[never, 1], never, {strictNever: false}>;
-  //=> false
-  ```
-  */
-  strictNever?: boolean;
-};
-type DefaultAllExtendOptions = {
-  strictNever: true;
-};
-/**
-Returns a boolean for whether every element in an array type extends another type.
-
-@example
-```
-import type {AllExtend} from 'type-fest';
-
-type A = AllExtend<[1, 2, 3], number>;
-//=> true
-
-type B = AllExtend<[1, 2, '3'], number>;
-//=> false
-
-type C = AllExtend<[number, number | string], number>;
-//=> boolean
-
-type D = AllExtend<[true, boolean, true], true>;
-//=> boolean
-```
-
-Note: Behaviour of optional elements depend on the `exactOptionalPropertyTypes` compiler option. When the option is disabled, the target type must include `undefined` for a successful match.
-
-```
-// @exactOptionalPropertyTypes: true
-import type {AllExtend} from 'type-fest';
-
-type A = AllExtend<[1?, 2?, 3?], number>;
-//=> true
-```
-
-```
-// @exactOptionalPropertyTypes: false
-import type {AllExtend} from 'type-fest';
-
-type A = AllExtend<[1?, 2?, 3?], number>;
-//=> boolean
-
-type B = AllExtend<[1?, 2?, 3?], number | undefined>;
-//=> true
-```
-
-@see {@link AllExtendOptions}
-
-@category Utilities
-@category Array
-*/
-type AllExtend<TArray extends UnknownArray, Type, Options extends AllExtendOptions = {}> = _AllExtend<CollapseRestElement<TArray>, Type, ApplyDefaultOptions<AllExtendOptions, DefaultAllExtendOptions, Options>>;
-type _AllExtend<TArray extends UnknownArray, Type, Options extends Required<AllExtendOptions>> = IfNotAnyOrNever<TArray, TArray extends readonly [infer First, ...infer Rest] ? IsNever<First> extends true ? Or<Or<IsNever<Type>, IsAny<Type>>, Not<Options['strictNever']>> extends true // If target `Type` is also `never`, or is `any`, or `strictNever` is disabled, recurse further.
-? _AllExtend<Rest, Type, Options> : false : First extends Type ? _AllExtend<Rest, Type, Options> : false : true, false, false>;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/and-all.d.ts
-/**
-Returns a boolean for whether all of the given elements are `true`.
-
-Use-cases:
-- Check if all conditions in a list of booleans are met.
-
-@example
-```
-import type {AndAll} from 'type-fest';
-
-type TTT = AndAll<[true, true, true]>;
-//=> true
-
-type TTF = AndAll<[true, true, false]>;
-//=> false
-
-type TFT = AndAll<[true, false, true]>;
-//=> false
-```
-
-Note: When `boolean` is passed as an element, it is distributed into separate cases, and the final result is a union of those cases.
-For example, `AndAll<[true, boolean]>` expands to `AndAll<[true, true]> | AndAll<[true, false]>`, which simplifies to `true | false` (i.e., `boolean`).
-
-@example
-```
-import type {AndAll} from 'type-fest';
-
-type A = AndAll<[true, boolean]>;
-//=> boolean
-
-type B = AndAll<[false, boolean]>;
-//=> false
-```
-
-Note: If any of the elements is `never`, the result becomes `false`.
-
-@example
-```
-import type {AndAll} from 'type-fest';
-
-type A = AndAll<[true, true, never]>;
-//=> false
-
-type B = AndAll<[false, never, never]>;
-//=> false
-
-type C = AndAll<[never, never, never]>;
-//=> false
-
-type D = AndAll<[boolean, true, never]>;
-//=> false
-```
-
-Note: If `any` is passed as an element, it is treated as `boolean` and the result is computed accordingly.
-
-@example
-```
-import type {AndAll} from 'type-fest';
-
-type A = AndAll<[false, any]>;
-//=> false
-
-type B = AndAll<[true, any]>;
-//=> boolean
-```
-
-Note: `AndAll<[]>` evaluates to `true` due to the concept of [vacuous truth](https://en.wikipedia.org/wiki/Logical_conjunction#:~:text=In%20keeping%20with%20the%20concept%20of%20vacuous%20truth%2C%20when%20conjunction%20is%20defined%20as%20an%20operator%20or%20function%20of%20arbitrary%20arity%2C%20the%20empty%20conjunction%20(AND%2Ding%20over%20an%20empty%20set%20of%20operands)%20is%20often%20defined%20as%20having%20the%20result%20true.), i.e., there are no `false` elements in an empty tuple.
-
-@see {@link And}
-@see {@link OrAll}
-*/
-type AndAll<T extends readonly boolean[]> = AllExtend<T, true>;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/and.d.ts
-/**
-Returns a boolean for whether two given types are both true.
-
-Use-case: Constructing complex conditional types where multiple conditions must be satisfied.
-
-@example
-```
-import type {And} from 'type-fest';
-
-type TT = And<true, true>;
-//=> true
-
-type TF = And<true, false>;
-//=> false
-
-type FT = And<false, true>;
-//=> false
-
-type FF = And<false, false>;
-//=> false
-```
-
-Note: When `boolean` is passed as an argument, it is distributed into separate cases, and the final result is a union of those cases.
-For example, `And<true, boolean>` expands to `And<true, true> | And<true, false>`, which simplifies to `true | false` (i.e., `boolean`).
-
-@example
-```
-import type {And} from 'type-fest';
-
-type A = And<true, boolean>;
-//=> boolean
-
-type B = And<boolean, true>;
-//=> boolean
-
-type C = And<false, boolean>;
-//=> false
-
-type D = And<boolean, false>;
-//=> false
-
-type E = And<boolean, boolean>;
-//=> boolean
-```
-
-Note: If either of the types is `never`, the result becomes `false`.
-
-@example
-```
-import type {And} from 'type-fest';
-
-type A = And<true, never>;
-//=> false
-
-type B = And<never, true>;
-//=> false
-
-type C = And<false, never>;
-//=> false
-
-type D = And<never, false>;
-//=> false
-
-type E = And<boolean, never>;
-//=> false
-
-type F = And<never, boolean>;
-//=> false
-
-type G = And<never, never>;
-//=> false
-```
-
-@see {@link AndAll}
-@see {@link Or}
-@see {@link Xor}
-*/
-type And<A extends boolean, B extends boolean> = AndAll<[A, B]>;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/greater-than.d.ts
-/**
-Returns a boolean for whether a given number is greater than another number.
-
-@example
-```
-import type {GreaterThan} from 'type-fest';
-
-type A = GreaterThan<1, -5>;
-//=> true
-
-type B = GreaterThan<1, 1>;
-//=> false
-
-type C = GreaterThan<1, 5>;
-//=> false
-```
-
-Note: If either argument is the non-literal `number` type, the result is `boolean`.
-
-@example
-```
-import type {GreaterThan} from 'type-fest';
-
-type A = GreaterThan<number, 1>;
-//=> boolean
-
-type B = GreaterThan<1, number>;
-//=> boolean
-
-type C = GreaterThan<number, number>;
-//=> boolean
-```
-
-@example
-```
-import type {GreaterThan} from 'type-fest';
-
-// Use `GreaterThan` to constrain a function parameter to positive numbers.
-declare function setPositive<N extends number>(value: GreaterThan<N, 0> extends true ? N : never): void;
-
-setPositive(1); // ✅ Allowed
-setPositive(2); // ✅ Allowed
-
-// @ts-expect-error
-setPositive(0);
-
-// @ts-expect-error
-setPositive(-1);
-```
-*/
-type GreaterThan<A extends number, B extends number> = A extends number // For distributing `A`
-? B extends number // For distributing `B`
-? number extends A | B ? boolean : [IsEqual<A, PositiveInfinity>, IsEqual<A, NegativeInfinity>, IsEqual<B, PositiveInfinity>, IsEqual<B, NegativeInfinity>] extends infer R extends [boolean, boolean, boolean, boolean] ? Or<And<IsEqual<R[0], true>, IsEqual<R[2], false>>, And<IsEqual<R[3], true>, IsEqual<R[1], false>>> extends true ? true : Or<And<IsEqual<R[1], true>, IsEqual<R[3], false>>, And<IsEqual<R[2], true>, IsEqual<R[0], false>>> extends true ? false : true extends R[number] ? false : [IsNegative<A>, IsNegative<B>] extends infer R extends [boolean, boolean] ? [true, false] extends R ? false : [false, true] extends R ? true : [false, false] extends R ? PositiveNumericStringGt<`${A}`, `${B}`> : PositiveNumericStringGt<`${NumberAbsolute<B>}`, `${NumberAbsolute<A>}`> : never : never : never // Should never happen
-: never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/greater-than-or-equal.d.ts
-/**
-Returns a boolean for whether a given number is greater than or equal to another number.
-
-@example
-```
-import type {GreaterThanOrEqual} from 'type-fest';
-
-type A = GreaterThanOrEqual<1, -5>;
-//=> true
-
-type B = GreaterThanOrEqual<1, 1>;
-//=> true
-
-type C = GreaterThanOrEqual<1, 5>;
-//=> false
-```
-
-Note: If either argument is the non-literal `number` type, the result is `boolean`.
-
-@example
-```
-import type {GreaterThanOrEqual} from 'type-fest';
-
-type A = GreaterThanOrEqual<number, 1>;
-//=> boolean
-
-type B = GreaterThanOrEqual<1, number>;
-//=> boolean
-
-type C = GreaterThanOrEqual<number, number>;
-//=> boolean
-```
-
-@example
-```
-import type {GreaterThanOrEqual} from 'type-fest';
-
-// Use `GreaterThanOrEqual` to constrain a function parameter to non-negative numbers.
-declare function setNonNegative<N extends number>(value: GreaterThanOrEqual<N, 0> extends true ? N : never): void;
-
-setNonNegative(0); // ✅ Allowed
-setNonNegative(1); // ✅ Allowed
-
-// @ts-expect-error
-setNonNegative(-1);
-
-// @ts-expect-error
-setNonNegative(-2);
-```
-*/
-type GreaterThanOrEqual<A extends number, B extends number> = number extends A | B ? boolean : A extends number // For distributing `A`
-? B extends number // For distributing `B`
-? A extends B ? true : GreaterThan<A, B> : never // Should never happen
-: never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/less-than.d.ts
-/**
-Returns a boolean for whether a given number is less than another number.
-
-@example
-```
-import type {LessThan} from 'type-fest';
-
-type A = LessThan<1, -5>;
-//=> false
-
-type B = LessThan<1, 1>;
-//=> false
-
-type C = LessThan<1, 5>;
-//=> true
-```
-
-Note: If either argument is the non-literal `number` type, the result is `boolean`.
-
-@example
-```
-import type {LessThan} from 'type-fest';
-
-type A = LessThan<number, 1>;
-//=> boolean
-
-type B = LessThan<1, number>;
-//=> boolean
-
-type C = LessThan<number, number>;
-//=> boolean
-```
-
-@example
-```
-import type {LessThan} from 'type-fest';
-
-// Use `LessThan` to constrain a function parameter to negative numbers.
-declare function setNegative<N extends number>(value: LessThan<N, 0> extends true ? N : never): void;
-
-setNegative(-1); // ✅ Allowed
-setNegative(-2); // ✅ Allowed
-
-// @ts-expect-error
-setNegative(0);
-
-// @ts-expect-error
-setNegative(1);
-```
-*/
-type LessThan<A extends number, B extends number> = GreaterThanOrEqual<A, B> extends infer Result ? Result extends true ? false : true : never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/internal/tuple.d.ts
-// Should never happen
-/**
-Returns the maximum value from a tuple of integers.
-
-Note:
-- Float numbers are not supported.
-
-@example
-```
-type A = TupleMax<[1, 2, 5, 3]>;
-//=> 5
-
-type B = TupleMax<[1, 2, 5, 3, 99, -1]>;
-//=> 99
-```
-*/
-type TupleMax<A extends number[], Result extends number = NegativeInfinity> = number extends A[number] ? never : A extends [infer F extends number, ...infer R extends number[]] ? GreaterThan<F, Result> extends true ? TupleMax<R, F> : TupleMax<R, Result> : Result;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/partial-deep.d.ts
-/**
-@see {@link PartialDeep}
-*/
-type PartialDeepOptions = {
-  /**
-  Whether to affect the individual elements of arrays and tuples.
-  	@default false
-  */
-  readonly recurseIntoArrays?: boolean;
-  /**
-  Allows `undefined` values in non-tuple arrays.
-  	- When set to `true`, elements of non-tuple arrays can be `undefined`.
-  - When set to `false`, only explicitly defined elements are allowed in non-tuple arrays, ensuring stricter type checking.
-  	@default false
-  	@example
-  You can allow `undefined` values in non-tuple arrays by passing `{recurseIntoArrays: true; allowUndefinedInNonTupleArrays: true}` as the second type argument:
-  	```
-  import type {PartialDeep} from 'type-fest';
-  	type Settings = {
-  	languages: string[];
-  };
-  	declare const partialSettings: PartialDeep<Settings, {recurseIntoArrays: true; allowUndefinedInNonTupleArrays: true}>;
-  	partialSettings.languages = [undefined]; // OK
-  ```
-  */
-  readonly allowUndefinedInNonTupleArrays?: boolean;
-};
-type DefaultPartialDeepOptions = {
-  recurseIntoArrays: false;
-  allowUndefinedInNonTupleArrays: false;
-};
-/**
-Create a type from another type with all keys and nested keys set to optional.
-
-Use-cases:
-- Merging a default settings/config object with another object, the second object would be a deep partial of the default object.
-- Mocking and testing complex entities, where populating an entire object with its keys would be redundant in terms of the mock or test.
-
-@example
-```
-import type {PartialDeep} from 'type-fest';
-
-let settings = {
-	textEditor: {
-		fontSize: 14,
-		fontColor: '#000000',
-		fontWeight: 400,
-	},
-	autocomplete: false,
-	autosave: true,
-};
-
-const applySavedSettings = (savedSettings: PartialDeep<typeof settings>) => (
-	{...settings, ...savedSettings, textEditor: {...settings.textEditor, ...savedSettings.textEditor}}
-);
-
-settings = applySavedSettings({textEditor: {fontWeight: 500}});
-```
-
-By default, this does not affect elements in array and tuple types. You can change this by passing `{recurseIntoArrays: true}` as the second type argument:
-
-```
-import type {PartialDeep} from 'type-fest';
-
-type Shape = {
-	dimensions: [number, number];
-};
-
-const partialShape: PartialDeep<Shape, {recurseIntoArrays: true}> = {
-	dimensions: [], // OK
-};
-
-partialShape.dimensions = [15]; // OK
-```
-
-@see {@link PartialDeepOptions}
-
-@category Object
-@category Array
-@category Set
-@category Map
-*/
-type PartialDeep<T, Options extends PartialDeepOptions = {}> = _PartialDeep<T, ApplyDefaultOptions<PartialDeepOptions, DefaultPartialDeepOptions, Options>>;
-type _PartialDeep<T, Options extends Required<PartialDeepOptions>> = T extends BuiltIns | ((new (...arguments_: any[]) => unknown)) ? T : T extends Map<infer KeyType, infer ValueType> ? PartialMapDeep<KeyType, ValueType, Options> : T extends Set<infer ItemType> ? PartialSetDeep<ItemType, Options> : T extends ReadonlyMap<infer KeyType, infer ValueType> ? PartialReadonlyMapDeep<KeyType, ValueType, Options> : T extends ReadonlySet<infer ItemType> ? PartialReadonlySetDeep<ItemType, Options> : T extends ((...arguments_: any[]) => unknown) ? IsNever<keyof T> extends true ? T // For functions with no properties
-: HasMultipleCallSignatures<T> extends true ? T : ((...arguments_: Parameters<T>) => ReturnType<T>) & PartialObjectDeep<T, Options> : T extends object ? T extends ReadonlyArray<infer ItemType> // Test for arrays/tuples, per https://github.com/microsoft/TypeScript/issues/35156
-? Options['recurseIntoArrays'] extends true ? ItemType[] extends T // Test for arrays (non-tuples) specifically
-? readonly ItemType[] extends T // Differentiate readonly and mutable arrays
-? ReadonlyArray<_PartialDeep<Options['allowUndefinedInNonTupleArrays'] extends false ? ItemType : ItemType | undefined, Options>> : Array<_PartialDeep<Options['allowUndefinedInNonTupleArrays'] extends false ? ItemType : ItemType | undefined, Options>> : PartialObjectDeep<T, Options> // Tuples behave properly
-: T // If they don't opt into array testing, just use the original type
-: PartialObjectDeep<T, Options> : unknown;
-/**
-Same as `PartialDeep`, but accepts only `Map`s and as inputs. Internal helper for `PartialDeep`.
-*/
-type PartialMapDeep<KeyType, ValueType, Options extends Required<PartialDeepOptions>> = {} & Map<_PartialDeep<KeyType, Options>, _PartialDeep<ValueType, Options>>;
-/**
-Same as `PartialDeep`, but accepts only `Set`s as inputs. Internal helper for `PartialDeep`.
-*/
-type PartialSetDeep<T, Options extends Required<PartialDeepOptions>> = {} & Set<_PartialDeep<T, Options>>;
-/**
-Same as `PartialDeep`, but accepts only `ReadonlyMap`s as inputs. Internal helper for `PartialDeep`.
-*/
-type PartialReadonlyMapDeep<KeyType, ValueType, Options extends Required<PartialDeepOptions>> = {} & ReadonlyMap<_PartialDeep<KeyType, Options>, _PartialDeep<ValueType, Options>>;
-/**
-Same as `PartialDeep`, but accepts only `ReadonlySet`s as inputs. Internal helper for `PartialDeep`.
-*/
-type PartialReadonlySetDeep<T, Options extends Required<PartialDeepOptions>> = {} & ReadonlySet<_PartialDeep<T, Options>>;
-/**
-Same as `PartialDeep`, but accepts only `object`s as inputs. Internal helper for `PartialDeep`.
-*/
-type PartialObjectDeep<ObjectType extends object, Options extends Required<PartialDeepOptions>> = { [KeyType in keyof ObjectType]?: _PartialDeep<ObjectType[KeyType], Options> };
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/subtract.d.ts
-/**
-Returns the difference between two numbers.
-
-Note:
-- A or B can only support `-999` ~ `999`.
-
-@example
-```
-import type {Subtract, PositiveInfinity} from 'type-fest';
-
-type A = Subtract<333, 222>;
-//=> 111
-
-type B = Subtract<111, -222>;
-//=> 333
-
-type C = Subtract<-111, 222>;
-//=> -333
-
-type D = Subtract<18, 96>;
-//=> -78
-
-type E = Subtract<PositiveInfinity, 9999>;
-//=> Infinity
-
-type F = Subtract<PositiveInfinity, PositiveInfinity>;
-//=> number
-```
-
-@category Numeric
-*/
-// TODO: Support big integer.
-type Subtract<A extends number, B extends number> = // Handle cases when A or B is the actual "number" type
-number extends A | B ? number // Handle cases when A and B are both +/- infinity
-: A extends B & (PositiveInfinity | NegativeInfinity) ? number // Handle cases when A is - infinity or B is + infinity
-: A extends NegativeInfinity ? NegativeInfinity : B extends PositiveInfinity ? NegativeInfinity // Handle cases when A is + infinity or B is - infinity
-: A extends PositiveInfinity ? PositiveInfinity : B extends NegativeInfinity ? PositiveInfinity // Handle case when numbers are equal to each other
-: A extends B ? 0 // Handle cases when A or B is 0
-: A extends 0 ? ReverseSign<B> : B extends 0 ? A // Handle remaining regular cases
-: SubtractPostChecks<A, B>;
-/**
-Subtracts two numbers A and B, such that they are not equal and neither of them are 0, +/- infinity or the `number` type
-*/
-type SubtractPostChecks<A extends number, B extends number, AreNegative = [IsNegative<A>, IsNegative<B>]> = AreNegative extends [false, false] ? SubtractPositives<A, B> : AreNegative extends [true, true] // When both numbers are negative we subtract the absolute values and then reverse the sign
-? ReverseSign<SubtractPositives<NumberAbsolute<A>, NumberAbsolute<B>>> // When the signs are different we can add the absolute values and then reverse the sign if A < B
-: [...TupleOf<NumberAbsolute<A>>, ...TupleOf<NumberAbsolute<B>>] extends infer R extends unknown[] ? LessThan<A, B> extends true ? ReverseSign<R['length']> : R['length'] : never;
-/**
-Subtracts two positive numbers.
-*/
-type SubtractPositives<A extends number, B extends number> = LessThan<A, B> extends true // When A < B we can reverse the result of B - A
-? ReverseSign<SubtractIfAGreaterThanB<B, A>> : SubtractIfAGreaterThanB<A, B>;
-/**
-Subtracts two positive numbers A and B such that A > B.
-*/
-type SubtractIfAGreaterThanB<A extends number, B extends number> = // This is where we always want to end up and do the actual subtraction
-TupleOf<A> extends [...TupleOf<B>, ...infer R] ? R['length'] : never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/sum.d.ts
-/**
-Returns the sum of two numbers.
-
-Note:
-- A or B can only support `-999` ~ `999`.
-
-@example
-```
-import type {Sum, PositiveInfinity, NegativeInfinity} from 'type-fest';
-
-type A = Sum<111, 222>;
-//=> 333
-
-type B = Sum<-111, 222>;
-//=> 111
-
-type C = Sum<111, -222>;
-//=> -111
-
-type D = Sum<PositiveInfinity, -9999>;
-//=> Infinity
-
-type E = Sum<PositiveInfinity, NegativeInfinity>;
-//=> number
-```
-
-@category Numeric
-*/
-// TODO: Support big integer.
-type Sum<A extends number, B extends number> = // Handle cases when A or B is the actual "number" type
-number extends A | B ? number // Handle cases when A and B are both +/- infinity
-: A extends B & (PositiveInfinity | NegativeInfinity) ? A // A or B could be used here as they are equal
-// Handle cases when A and B are opposite infinities
-: A | B extends PositiveInfinity | NegativeInfinity ? number // Handle cases when A is +/- infinity
-: A extends PositiveInfinity | NegativeInfinity ? A // Handle cases when B is +/- infinity
-: B extends PositiveInfinity | NegativeInfinity ? B // Handle cases when A or B is 0 or it's the same number with different signs
-: A extends 0 ? B : B extends 0 ? A : A extends ReverseSign<B> ? 0 // Handle remaining regular cases
-: SumPostChecks<A, B>;
-/**
-Adds two numbers A and B, such that they are not equal with different signs and neither of them are 0, +/- infinity or the `number` type
-*/
-type SumPostChecks<A extends number, B extends number, AreNegative = [IsNegative<A>, IsNegative<B>]> = AreNegative extends [false, false] // When both numbers are positive we can add them together
-? SumPositives<A, B> : AreNegative extends [true, true] // When both numbers are negative we add the absolute values and then reverse the sign
-? ReverseSign<SumPositives<NumberAbsolute<A>, NumberAbsolute<B>>> // When the signs are different we can subtract the absolute values, remove the sign
-// and then reverse the sign if the larger absolute value is negative
-: NumberAbsolute<Subtract<NumberAbsolute<A>, NumberAbsolute<B>>> extends infer Result extends number ? TupleMax<[NumberAbsolute<A>, NumberAbsolute<B>]> extends infer Max_ extends number ? Max_ extends A | B // The larger absolute value is positive, so the result is positive
-? Result // The larger absolute value is negative, so the result is negative
-: ReverseSign<Result> : never : never;
-/**
-Adds two positive numbers.
-*/
-type SumPositives<A extends number, B extends number> = [...TupleOf<A>, ...TupleOf<B>]['length'] extends infer Result extends number ? Result : never;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/paths.d.ts
-/**
-Paths options.
-
-@see {@link Paths}
-*/
-type PathsOptions = {
-  /**
-  The maximum depth to recurse when searching for paths. Range: 0 ~ 10.
-  	@default 5
-  */
-  maxRecursionDepth?: number;
-  /**
-  Use bracket notation for array indices and numeric object keys.
-  	@default false
-  	@example
-  ```
-  import type {Paths} from 'type-fest';
-  	type ArrayExample = {
-  	array: ['foo'];
-  };
-  	type A = Paths<ArrayExample, {bracketNotation: false}>;
-  //=> 'array' | 'array.0'
-  	type B = Paths<ArrayExample, {bracketNotation: true}>;
-  //=> 'array' | 'array[0]'
-  ```
-  	@example
-  ```
-  import type {Paths} from 'type-fest';
-  	type NumberKeyExample = {
-  	1: ['foo'];
-  };
-  	type A = Paths<NumberKeyExample, {bracketNotation: false}>;
-  //=> 1 | '1' | '1.0'
-  	type B = Paths<NumberKeyExample, {bracketNotation: true}>;
-  //=> '[1]' | '[1][0]'
-  ```
-  */
-  bracketNotation?: boolean;
-  /**
-  Only include leaf paths in the output.
-  	@default false
-  	@example
-  ```
-  import type {Paths} from 'type-fest';
-  	type Post = {
-  	id: number;
-  	author: {
-  		id: number;
-  		name: {
-  			first: string;
-  			last: string;
-  		};
-  	};
-  };
-  	type AllPaths = Paths<Post, {leavesOnly: false}>;
-  //=> 'id' | 'author' | 'author.id' | 'author.name' | 'author.name.first' | 'author.name.last'
-  	type LeafPaths = Paths<Post, {leavesOnly: true}>;
-  //=> 'id' | 'author.id' | 'author.name.first' | 'author.name.last'
-  ```
-  	@example
-  ```
-  import type {Paths} from 'type-fest';
-  	type ArrayExample = {
-  	array: Array<{foo: string}>;
-  	tuple: [string, {bar: string}];
-  };
-  	type AllPaths = Paths<ArrayExample, {leavesOnly: false}>;
-  //=> 'array' | 'tuple' | `array.${number}` | `array.${number}.foo` | 'tuple.0' | 'tuple.1' | 'tuple.1.bar'
-  	type LeafPaths = Paths<ArrayExample, {leavesOnly: true}>;
-  //=> `array.${number}.foo` | 'tuple.0' | 'tuple.1.bar'
-  ```
-  */
-  leavesOnly?: boolean;
-  /**
-  Only include paths at the specified depth. By default all paths up to {@link PathsOptions.maxRecursionDepth | `maxRecursionDepth`} are included.
-  	Note: Depth starts at `0` for root properties.
-  	@default number
-  	@example
-  ```
-  import type {Paths} from 'type-fest';
-  	type Post = {
-  	id: number;
-  	author: {
-  		id: number;
-  		name: {
-  			first: string;
-  			last: string;
-  		};
-  	};
-  };
-  	type DepthZero = Paths<Post, {depth: 0}>;
-  //=> 'id' | 'author'
-  	type DepthOne = Paths<Post, {depth: 1}>;
-  //=> 'author.id' | 'author.name'
-  	type DepthTwo = Paths<Post, {depth: 2}>;
-  //=> 'author.name.first' | 'author.name.last'
-  	type LeavesAtDepthOne = Paths<Post, {leavesOnly: true; depth: 1}>;
-  //=> 'author.id'
-  ```
-  */
-  depth?: number;
-};
-type DefaultPathsOptions = {
-  maxRecursionDepth: 5;
-  bracketNotation: false;
-  leavesOnly: false;
-  depth: number;
-};
-/**
-Generate a union of all possible paths to properties in the given object.
-
-It also works with arrays.
-
-Use-case: You want a type-safe way to access deeply nested properties in an object.
-
-@example
-```
-import type {Paths} from 'type-fest';
-
-type Project = {
-	filename: string;
-	listA: string[];
-	listB: [{filename: string}];
-	folder: {
-		subfolder: {
-			filename: string;
-		};
-	};
-};
-
-type ProjectPaths = Paths<Project>;
-//=> 'filename' | 'listA' | 'listB' | 'folder' | `listA.${number}` | 'listB.0' | 'listB.0.filename' | 'folder.subfolder' | 'folder.subfolder.filename'
-
-declare function open<Path extends ProjectPaths>(path: Path): void;
-
-open('filename'); // Pass
-open('folder.subfolder'); // Pass
-open('folder.subfolder.filename'); // Pass
-// @ts-expect-error
-open('foo'); // TypeError
-
-// Also works with arrays
-open('listA.1'); // Pass
-open('listB.0'); // Pass
-// @ts-expect-error
-open('listB.1'); // TypeError. Because listB only has one element.
-```
-
-@category Object
-@category Array
-*/
-type Paths$1<T, Options extends PathsOptions = {}> = _Paths<T, ApplyDefaultOptions<PathsOptions, DefaultPathsOptions, Options>>;
-type _Paths<T, Options extends Required<PathsOptions>, CurrentDepth extends number = 0> = T extends NonRecursiveType | Exclude<MapsSetsOrArrays, UnknownArray> ? never : IsAny<T> extends true ? never : T extends object ? InternalPaths<Required<T>, Options, CurrentDepth> : never;
-type InternalPaths<T, Options extends Required<PathsOptions>, CurrentDepth extends number> = { [Key in keyof T]: Key extends string | number // Limit `Key` to `string | number`
-? (And<Options['bracketNotation'], IsNumberLike<Key>> extends true ? `[${Key}]` : CurrentDepth extends 0 // Return both `Key` and `ToString<Key>` because for number keys, like `1`, both `1` and `'1'` are valid keys.
-? Key | ToString<Key> : `.${(Key | ToString<Key>)}`) extends infer TransformedKey extends string | number ? ((Options['leavesOnly'] extends true ? Options['maxRecursionDepth'] extends CurrentDepth ? TransformedKey : IsNever<T[Key]> extends true ? TransformedKey : T[Key] extends infer Value // For distributing `T[Key]`
-? (Value extends readonly [] | NonRecursiveType | Exclude<MapsSetsOrArrays, UnknownArray> ? TransformedKey : IsNever<keyof Value> extends true // Check for empty object & `unknown`, because `keyof unknown` is `never`.
-? TransformedKey : never) : never // Should never happen
-: TransformedKey) extends infer _TransformedKey // If `depth` is provided, the condition becomes truthy only when it matches `CurrentDepth`.
-// Otherwise, since `depth` defaults to `number`, the condition is always truthy, returning paths at all depths.
-? CurrentDepth extends Options['depth'] ? _TransformedKey : never : never) // Recursively generate paths for the current key
-| (GreaterThan<Options['maxRecursionDepth'], CurrentDepth> extends true // Limit the depth to prevent infinite recursion
-? `${TransformedKey}${_Paths<T[Key], Options, Sum<CurrentDepth, 1>> & (string | number)}` : never) : never : never }[keyof T & (T extends UnknownArray ? number : unknown)];
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/literal-union.d.ts
-type _LiteralStringUnion<T> = LiteralUnion<T, string>;
-/**
-Allows creating a union type by combining primitive types and literal types without sacrificing auto-completion in IDEs for the literal type part of the union.
-
-Currently, when a union type of a primitive type is combined with literal types, TypeScript loses all information about the combined literals. Thus, when such type is used in an IDE with autocompletion, no suggestions are made for the declared literals.
-
-This type is a workaround for [Microsoft/TypeScript#29729](https://github.com/Microsoft/TypeScript/issues/29729). It will be removed as soon as it's not needed anymore.
-
-@example
-```
-import type {LiteralUnion} from 'type-fest';
-
-// Before
-
-type Pet = 'dog' | 'cat' | string;
-
-const petWithoutAutocomplete: Pet = '';
-// Start typing in your TypeScript-enabled IDE.
-// You **will not** get auto-completion for `dog` and `cat` literals.
-
-// After
-
-type Pet2 = LiteralUnion<'dog' | 'cat', string>;
-
-const petWithAutoComplete: Pet2 = '';
-// You **will** get auto-completion for `dog` and `cat` literals.
-```
-
-@category Type
-*/
-type LiteralUnion<LiteralType, BaseType extends Primitive> = LiteralType | (BaseType & Record<never, never>);
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/key-as-string.d.ts
-/**
-Get keys of the given type as strings.
-
-Number keys are converted to strings.
-
-Use-cases:
-- Get string keys from a type which may have number keys.
-- Makes it possible to index using strings retrieved from template types.
-
-@example
-```
-import type {KeyAsString} from 'type-fest';
-
-type Foo = {
-	1: number;
-	stringKey: string;
-};
-
-type StringKeysOfFoo = KeyAsString<Foo>;
-//=> 'stringKey' | '1'
-```
-
-@category Object
-*/
-type KeyAsString<BaseType> = `${Extract<keyof BaseType, string | number>}`;
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/split.d.ts
-/**
-Split options.
-
-@see {@link Split}
-*/
-type SplitOptions = {
-  /**
-  When enabled, instantiations with non-literal string types (e.g., `string`, `Uppercase<string>`, `on${string}`) simply return back `string[]` without performing any splitting, as the exact structure cannot be statically determined.
-  	@default true
-  	@example
-  ```ts
-  import type {Split} from 'type-fest';
-  	type Example1 = Split<`foo.${string}.bar`, '.', {strictLiteralChecks: false}>;
-  //=> ['foo', string, 'bar']
-  	type Example2 = Split<`foo.${string}`, '.', {strictLiteralChecks: true}>;
-  //=> string[]
-  	type Example3 = Split<'foobarbaz', `b${string}`, {strictLiteralChecks: false}>;
-  //=> ['foo', 'r', 'z']
-  	type Example4 = Split<'foobarbaz', `b${string}`, {strictLiteralChecks: true}>;
-  //=> string[]
-  ```
-  */
-  strictLiteralChecks?: boolean;
-};
-type DefaultSplitOptions = {
-  strictLiteralChecks: true;
-};
-/**
-Represents an array of strings split using a given character or character set.
-
-Use-case: Defining the return type of a method like `String.prototype.split`.
-
-@example
-```
-import type {Split} from 'type-fest';
-
-declare function split<S extends string, D extends string>(string: S, separator: D): Split<S, D>;
-
-type Item = 'foo' | 'bar' | 'baz' | 'waldo';
-const items = 'foo,bar,baz,waldo';
-const array: Item[] = split(items, ',');
-```
-
-@see {@link SplitOptions}
-
-@category String
-@category Template literal
-*/
-type Split<S extends string, Delimiter extends string, Options extends SplitOptions = {}> = SplitHelper<S, Delimiter, ApplyDefaultOptions<SplitOptions, DefaultSplitOptions, Options>>;
-type SplitHelper<S extends string, Delimiter extends string, Options extends Required<SplitOptions>, Accumulator extends string[] = []> = S extends string // For distributing `S`
-? Delimiter extends string // For distributing `Delimiter`
-// If `strictLiteralChecks` is `false` OR `S` and `Delimiter` both are string literals, then perform the split
-? Or<Not<Options['strictLiteralChecks']>, And<IsStringLiteral<S>, IsStringLiteral<Delimiter>>> extends true ? S extends `${infer Head}${Delimiter}${infer Tail}` ? SplitHelper<Tail, Delimiter, Options, [...Accumulator, Head]> : Delimiter extends '' ? S extends '' ? Accumulator : [...Accumulator, S] : [...Accumulator, S] // Otherwise, return `string[]`
-: string[] : never // Should never happen
-: never; // Should never happen
-//#endregion
-//#region ../../node_modules/.pnpm/type-fest@5.5.0/node_modules/type-fest/source/get.d.ts
-type GetOptions = {
-  /**
-  Include `undefined` in the return type when accessing properties.
-  	Setting this to `false` is not recommended.
-  	@default true
-  */
-  strict?: boolean;
-};
-type DefaultGetOptions = {
-  strict: true;
-};
-/**
-Like the `Get` type but receives an array of strings as a path parameter.
-*/
-type GetWithPath<BaseType, Keys, Options extends Required<GetOptions>> = Keys extends readonly [] ? BaseType : Keys extends readonly [infer Head, ...infer Tail] ? GetWithPath<PropertyOf<BaseType, Extract<Head, string>, Options>, Extract<Tail, string[]>, Options> : never;
-/**
-Adds `undefined` to `Type` if `strict` is enabled.
-*/
-type Strictify<Type, Options extends Required<GetOptions>> = Options['strict'] extends false ? Type : (Type | undefined);
-/**
-If `Options['strict']` is `true`, includes `undefined` in the returned type when accessing properties on `Record<string, any>`.
-
-Known limitations:
-- Does not include `undefined` in the type on object types with an index signature (for example, `{a: string; [key: string]: string}`).
-*/
-type StrictPropertyOf<BaseType, Key extends keyof BaseType, Options extends Required<GetOptions>> = Record<string, any> extends BaseType ? string extends keyof BaseType ? Strictify<BaseType[Key], Options> // Record<string, any>
-: BaseType[Key] // Record<'a' | 'b', any> (Records with a string union as keys have required properties)
-: BaseType[Key];
-/**
-Splits a dot-prop style path into a tuple comprised of the properties in the path. Handles square-bracket notation.
-
-@example
-```
-type A = ToPath<'foo.bar.baz'>;
-//=> ['foo', 'bar', 'baz']
-
-type B = ToPath<'foo[0].bar.baz'>;
-//=> ['foo', '0', 'bar', 'baz']
-```
-*/
-type ToPath<S extends string> = Split<FixPathSquareBrackets<S>, '.', {
-  strictLiteralChecks: false;
-}>;
-/**
-Replaces square-bracketed dot notation with dots, for example, `foo[0].bar` -> `foo.0.bar`.
-*/
-type FixPathSquareBrackets<Path extends string> = Path extends `[${infer Head}]${infer Tail}` ? Tail extends `[${string}` ? `${Head}.${FixPathSquareBrackets<Tail>}` : `${Head}${FixPathSquareBrackets<Tail>}` : Path extends `${infer Head}[${infer Middle}]${infer Tail}` ? `${Head}.${FixPathSquareBrackets<`[${Middle}]${Tail}`>}` : Path;
-/**
-Returns true if `LongString` is made up out of `Substring` repeated 0 or more times.
-
-@example
-```
-type A = ConsistsOnlyOf<'aaa', 'a'>; //=> true
-type B = ConsistsOnlyOf<'ababab', 'ab'>; //=> true
-type C = ConsistsOnlyOf<'aBa', 'a'>; //=> false
-type D = ConsistsOnlyOf<'', 'a'>; //=> true
-```
-*/
-type ConsistsOnlyOf<LongString extends string, Substring extends string> = LongString extends '' ? true : LongString extends `${Substring}${infer Tail}` ? ConsistsOnlyOf<Tail, Substring> : false;
-/**
-Convert a type which may have number keys to one with string keys, making it possible to index using strings retrieved from template types.
-
-@example
-```
-type WithNumbers = {foo: string; 0: boolean};
-type WithStrings = WithStringKeys<WithNumbers>;
-
-type WithNumbersKeys = keyof WithNumbers;
-//=> 'foo' | 0
-type WithStringsKeys = keyof WithStrings;
-//=> 'foo' | '0'
-```
-*/
-type WithStringKeys<BaseType> = { [Key in KeyAsString<BaseType>]: UncheckedIndex<BaseType, Key> };
-/**
-Perform a `T[U]` operation if `T` supports indexing.
-*/
-type UncheckedIndex<T, U extends string | number> = [T] extends [Record<string | number, any>] ? T[U] : never;
-/**
-Get a property of an object or array. Works when indexing arrays using number-literal-strings, for example, `PropertyOf<number[], '0'> = number`, and when indexing objects with number keys.
-
-Note:
-- Returns `unknown` if `Key` is not a property of `BaseType`, since TypeScript uses structural typing, and it cannot be guaranteed that extra properties unknown to the type system will exist at runtime.
-- Returns `undefined` from nullish values, to match the behaviour of most deep-key libraries like `lodash`, `dot-prop`, etc.
-*/
-type PropertyOf<BaseType, Key extends string, Options extends Required<GetOptions>> = BaseType extends null | undefined ? undefined : Key extends keyof BaseType ? StrictPropertyOf<BaseType, Key, Options> // Handle arrays and tuples
-: BaseType extends readonly unknown[] ? Key extends `${number}` // For arrays with unknown length (regular arrays)
-? number extends BaseType['length'] ? Strictify<BaseType[number], Options> // For tuples: check if the index is valid
-: Key extends keyof BaseType ? Strictify<BaseType[Key & keyof BaseType], Options> // Out-of-bounds access for tuples
-: unknown // Non-numeric string key for arrays/tuples
-: unknown // Handle array-like objects
-: BaseType extends {
-  [n: number]: infer Item;
-  length: number; // Note: This is needed to avoid being too lax with records types using number keys like `{0: string; 1: boolean}`.
-} ? (ConsistsOnlyOf<Key, DigitCharacter> extends true ? Strictify<Item, Options> : unknown) : Key extends keyof WithStringKeys<BaseType> ? StrictPropertyOf<WithStringKeys<BaseType>, Key, Options> : unknown; // This works by first splitting the path based on `.` and `[...]` characters into a tuple of string keys. Then it recursively uses the head key to get the next property of the current object, until there are no keys left. Number keys extract the item type from arrays, or are converted to strings to extract types from tuples and dictionaries with number keys.
-/**
-Get a deeply-nested property from an object using a key path, like Lodash's `.get()` function.
-
-Use-case: Retrieve a property from deep inside an API response or some other complex object.
-
-@example
-```
-import type {Get} from 'type-fest';
-
-declare function get<BaseType, const Path extends string | readonly string[]>(object: BaseType, path: Path): Get<BaseType, Path>;
-
-type ApiResponse = {
-	hits: {
-		hits: Array<{
-			_id: string;
-			_source: {
-				name: Array<{
-					given: string[];
-					family: string;
-				}>;
-				birthDate: string;
-			};
-		}>;
-	};
-};
-
-const getName = (apiResponse: ApiResponse) => get(apiResponse, 'hits.hits[0]._source.name');
-//=> (apiResponse: ApiResponse) => {
-// 	given: string[];
-// 	family: string;
-// }[] | undefined
-
-// Path also supports a readonly array of strings
-const getNameWithPathArray = (apiResponse: ApiResponse) => get(apiResponse, ['hits', 'hits', '0', '_source', 'name']);
-//=> (apiResponse: ApiResponse) => {
-// 	given: string[];
-// 	family: string;
-// }[] | undefined
-
-// Non-strict mode:
-type A = Get<string[], '3', {strict: false}>;
-//=> string
-
-type B = Get<Record<string, string>, 'foo', {strict: true}>;
-//=> string | undefined
-```
-
-@category Object
-@category Array
-@category Template literal
-*/
-type Get<BaseType, Path extends readonly string[] | _LiteralStringUnion<ToString<Paths$1<BaseType, {
-  bracketNotation: false;
-  maxRecursionDepth: 2;
-}> | Paths$1<BaseType, {
-  bracketNotation: true;
-  maxRecursionDepth: 2;
-}>>>, Options extends GetOptions = {}> = GetWithPath<BaseType, Path extends string ? ToPath<Path> : Path, ApplyDefaultOptions<GetOptions, DefaultGetOptions, Options>>;
-//#endregion
 //#region src/types/shared.d.ts
+/**
+ * The validation mode determines when validation occurs.
+ * - `lazy`: Validates on blur or submission.
+ * - `eager`: Validates on blur, then on every change if an error exists.
+ */
+type ValidationMode = 'eager' | 'lazy';
 /**
  * Interaction events that can trigger a validation check for a field.
  * - onBlur: Trigger validation when the field loses focus.
@@ -2787,6 +71,11 @@ type UseNotFormConfig<TSchema extends ObjectSchema> = {
    * @default { onBlur: true, onChange: true, onInput: true }
    */
   validateOn?: Partial<Record<ValidationTrigger, boolean>>;
+  /**
+   * The validation mode of the form.
+   * @default { eager: true }
+   */
+  validationMode?: Partial<Record<ValidationMode, boolean>>;
   /**
    * Callback triggered when form validation passes and the form is submitted.
    * @param values The validated output data from the schema.
@@ -2796,221 +85,288 @@ type UseNotFormConfig<TSchema extends ObjectSchema> = {
 //#endregion
 //#region src/types/not-form.d.ts
 /**
- * The core state and methods provided by a form instance.
- * @template TSchema The validation schema type derived from ObjectSchema.
+ * The complete state and API of a form instance returned by `useNotForm`.
+ * @template TSchema The validation schema type derived from `ObjectSchema`.
  */
-type NotFormInstance<TSchema extends ObjectSchema> = {
-  /**
-   * A convenience self-reference to the form instance.
-   * Useful when you prefer to destructure the composable return value but still need
-   * to pass the full instance to NotForm or other components.
-   * @example
-   * const { values, submit, instance } = useNotForm({ schema, onSubmit })
-   * // <NotForm :form="instance" />
-   */
-  instance: NotFormInstance<TSchema>; /** The initial values the form was created or last reset with */
-  readonly initialValues: UseNotFormConfig<TSchema>['initialValues']; /** The initial errors the form was created or last reset with */
-  readonly initialErrors: UseNotFormConfig<TSchema>['initialErrors'];
+type NotFormInstance<TSchema extends ObjectSchema> = Raw<{
+  /** The values the form was initialised or last reset with. */readonly initialValues: UseNotFormConfig<TSchema>['initialValues']; /** The errors the form was initialised or last reset with. */
+  readonly initialErrors: UseNotFormConfig<TSchema>['initialErrors']; /** The resolved validation triggers for this form. */
+  readonly validateOn: Required<NonNullable<UseNotFormConfig<TSchema>['validateOn']>>; /** The resolved validation mode for this form. */
+  readonly validationMode: Required<NonNullable<UseNotFormConfig<TSchema>['validationMode']>>;
   /**
-   * The validation triggers of the form.
-   * @default { onBlur: true, onChange: true, onInput: true }
+   * Deeply reactive object of field values.
+   *
+   * Access directly — no `.value` needed:
+   * ```ts
+   * form.values.email
+   * ```
+   *
+   * Use with `v-model` for two-way binding:
+   * ```vue
+   * <input v-model="form.values.email" />
+   * ```
    */
-  readonly validateOn: UseNotFormConfig<TSchema>['validateOn']; /** Deeply reactive object of field values */
-  values: Ref<StandardSchemaV1.InferInput<TSchema>>;
+  values: StandardSchemaV1.InferInput<TSchema>;
   /**
-   * Updates a specific field value by path.
-   * Also marks the field as touched and updates its dirty state.
-   * @param path Dot-separated path to the field.
-   * @param value The new value to apply.
+   * Sets a field value by dot-separated path.
+   *
+   * Useful for deeply nested paths or custom inputs that do not use `v-model`.
+   * Does **not** trigger validation — the field's event handlers are responsible for that.
+   *
+   * ```ts
+   * form.setValue('address.city', 'Lagos')
+   * ```
    */
   setValue: <const TPath extends Paths<StandardSchemaV1.InferInput<TSchema>>>(path: TPath, value: Get<StandardSchemaV1.InferInput<TSchema>, TPath, {
     strict: false;
   }>) => void;
   /**
-   * Updates multiple field values at once.
-   * Each path is processed through setValue individually.
-   * @param values Partial object of field paths to new values.
+   * The set of field paths the user has interacted with.
+   * Populated for all paths when the form is submitted.
    */
-  setValues: (values: DeepPartial<StandardSchemaV1.InferInput<TSchema>>) => void; /** Reactive set of field paths that have been touched */
-  touchedFields: Ref<Set<Paths<StandardSchemaV1.InferInput<TSchema>>>>; /** Whether any field in the form has been touched */
+  touchedFields: Set<Paths<StandardSchemaV1.InferInput<TSchema>>>; /** Whether any field has been touched. */
   isTouched: ComputedRef<boolean>;
   /**
-   * Marks a specific field as touched.
-   * @param path Dot-separated path to the field.
-   */
-  touchField: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => void;
-  /**
-   * Marks a specific field as not touched.
-   * @param path Dot-separated path to the field.
+   * Marks a field as touched.
+   * Typically called automatically by the field's `onBlur` handler.
    */
-  unTouchField: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => void; /** Marks all fields in the form as touched */
-  touchAllFields: () => void; /** Marks all fields in the form as not touched */
-  unTouchAllFields: () => void; /** Reactive set of field paths that have been dirtied */
-  dirtyFields: Ref<Set<Paths<StandardSchemaV1.InferInput<TSchema>>>>; /** Whether any field in the form has been dirtied */
+  touchField: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => void; /** The set of field paths whose current value differs from the initial value. */
+  dirtyFields: Set<Paths<StandardSchemaV1.InferInput<TSchema>>>; /** Whether any field value differs from its initial value. */
   isDirty: ComputedRef<boolean>;
   /**
-   * Marks a specific field as dirty.
-   * @param path Dot-separated path to the field.
-   */
-  dirtyField: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => void;
-  /**
-   * Marks a specific field as not dirty.
-   * @param path Dot-separated path to the field.
+   * Marks a field as dirty.
+   * Typically called automatically when a field value changes.
    */
-  unDirtyField: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => void; /** Marks all fields in the form as dirty */
-  dirtyAllFields: () => void; /** Marks all fields in the form as not dirty */
-  unDirtyAllFields: () => void; /** The raw issues from the last validation */
-  errors: Ref<StandardSchemaV1.Issue[]>;
+  dirtyField: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => void; /** The raw validation issues produced by the last validation run. */
+  errors: StandardSchemaV1.Issue[];
   /**
-   * A flat object mapping field paths to their first error message.
-   * Useful for direct template access: errorsMap['user.email']
+   * A flat map of field path to its first error message.
+   *
+   * Convenient for direct template access without calling `getFieldErrors`:
+   * ```vue
+   * <p>{{ form.errorsMap['address.city'] }}</p>
+   * ```
    */
   errorsMap: ComputedRef<Partial<Record<Paths<StandardSchemaV1.InferInput<TSchema>>, string>>>;
   /**
-   * Sets a single field error, replacing any existing error for that path.
-   * @param error The issue to apply.
-   */
-  setError: (error: StandardSchemaV1.Issue) => void;
-  /**
-   * Replaces all current errors with the provided issues.
-   * @param errors The new set of issues.
+   * Replaces an existing error for the same path, or appends it if none exists.
+   * Useful for setting server-side errors after submission.
    */
-  setErrors: (errors: StandardSchemaV1.Issue[]) => void; /** Removes all active validation issues */
+  setError: (error: StandardSchemaV1.Issue) => void; /** Replaces all current errors with the provided issues. */
+  setErrors: (errors: StandardSchemaV1.Issue[]) => void; /** Removes all active validation errors. */
   clearErrors: () => void;
   /**
    * Returns all validation issues for a specific field path.
-   * @param path Dot-separated path to the field.
+   *
+   * ```ts
+   * form.getFieldErrors('address.city')
+   * ```
    */
-  getFieldErrors: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => StandardSchemaV1.Issue[]; /** Whether any field or the full form is currently being validated */
+  getFieldErrors: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => StandardSchemaV1.Issue[]; /** Whether a validation run is currently in progress. */
   isValidating: Ref<boolean>;
   /**
    * Validates the entire form against the schema.
-   * @returns A promise resolving to the validation result.
+   * Replaces all current errors with the result.
    */
   validate: () => Promise<StandardSchemaV1.Result<StandardSchemaV1.InferOutput<TSchema>>>;
   /**
-   * Validates a specific field against the schema.
-   * Only replaces errors for that field, leaving other fields untouched.
-   * @param path Dot-separated path to the field.
-   * @returns A promise resolving to the validation result.
+   * Validates a single field against the schema.
+   * Only replaces errors for that field — all other fields are left untouched.
    */
-  validateField: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => Promise<StandardSchemaV1.Result<StandardSchemaV1.InferOutput<TSchema>>>; /** Whether the form is valid */
-  isValid: ComputedRef<boolean>; /** Whether the form is currently submitting */
+  validateField: (path: Paths<StandardSchemaV1.InferInput<TSchema>>) => Promise<StandardSchemaV1.Result<StandardSchemaV1.InferOutput<TSchema>>>; /** Whether the form currently has no validation errors. */
+  isValid: ComputedRef<boolean>; /** Whether the form is currently running its submit handler. */
   isSubmitting: Ref<boolean>;
   /**
-   * Validates and then triggers form submission.
-   * Marks all fields as touched and dirty before validating.
-   * Calls onSubmit if validation passes, otherwise prevents native submission.
-   * @param event The native form submission event.
+   * Validates the form and runs `onSubmit` if it passes.
+   *
+   * Marks all fields as touched and dirty before validating so all errors surface.
+   * If validation fails, submission is aborted.
+   * Bind to the native form's `@submit` event:
+   *
+   * ```vue
+   * <form @submit="form.submit">
+   * ```
    */
   submit: (event: Event) => Promise<void>;
   /**
-   * Resets the form to its initial or provided state.
-   * Clears all touched and dirty fields.
-   * If new values or errors are provided, they become the new baseline.
-   * @param values Optional new initial values to reset to.
-   * @param errors Optional new initial errors to reset to.
+   * Resets the form to its initial state, or to new values and errors if provided.
+   *
+   * Clears all touched and dirty tracking. If `values` or `errors` are passed,
+   * they replace the stored baseline so subsequent resets return to the new state.
+   *
+   * ```ts
+   * // Reset to original initial values
+   * form.reset()
+   *
+   * // Reset to new values (becomes the new baseline)
+   * form.reset({ name: 'Jane' })
+   * ```
    */
   reset: (values?: DeepPartial<StandardSchemaV1.InferInput<TSchema>>, errors?: StandardSchemaV1.Issue[]) => void;
+}>;
+/** Props for the `NotForm` component. */
+type NotFormProps = {
+  /** The form instance to provide to all descendant `NotField` components. */form: NotFormInstance<any>;
 };
-/**
- * Props for the NotForm component
- * @template TSchema The validation schema type derived from ObjectSchema.
- */
-type NotFormProps<TSchema extends ObjectSchema> = {
-  /** The form instance to use */instance: NotFormInstance<TSchema>;
-};
+/** Slots for the `NotForm` component. */
 type NotFormSlots = {
-  /** The default slot */default: [];
+  default: [];
 };
 //#endregion
 //#region src/composables/use-not-form.d.ts
 declare function useNotForm<TSchema extends ObjectSchema>(config: UseNotFormConfig<TSchema>): NotFormInstance<TSchema>;
 //#endregion
 //#region src/components/not-form.vue.d.ts
-declare const __VLS_export$1: <TSchema extends ObjectSchema>(__VLS_props: NonNullable<Awaited<typeof __VLS_setup>>["props"], __VLS_ctx?: __VLS_PrettifyLocal$1<Pick<NonNullable<Awaited<typeof __VLS_setup>>, "attrs" | "emit" | "slots">>, __VLS_exposed?: NonNullable<Awaited<typeof __VLS_setup>>["expose"], __VLS_setup?: Promise<{
-  props: _$vue.PublicProps & __VLS_PrettifyLocal$1<NotFormProps<TSchema>> & (typeof globalThis extends {
-    __VLS_PROPS_FALLBACK: infer P;
-  } ? P : {});
-  expose: (exposed: {}) => void;
-  attrs: any;
-  slots: NotFormSlots;
-  emit: {};
-}>) => _$vue.VNode & {
-  __ctx?: Awaited<typeof __VLS_setup>;
+type __VLS_Slots$1 = NotFormSlots;
+declare const __VLS_base$1: _$vue.DefineComponent<NotFormProps, {}, {}, {}, {}, _$vue.ComponentOptionsMixin, _$vue.ComponentOptionsMixin, {}, string, _$vue.PublicProps, Readonly<NotFormProps> & Readonly<{}>, {}, {}, {}, {}, string, _$vue.ComponentProvideOptions, false, {}, any>;
+declare const __VLS_export$2: __VLS_WithSlots$1<typeof __VLS_base$1, __VLS_Slots$1>;
+declare const _default$1: typeof __VLS_export$2;
+type __VLS_WithSlots$1<T, S> = T & {
+  new (): {
+    $slots: S;
+  };
 };
-declare const _default$1: typeof __VLS_export$1;
-type __VLS_PrettifyLocal$1<T> = (T extends any ? { [K in keyof T]: T[K] } : { [K in keyof T as K]: T[K] }) & {};
 //#endregion
 //#region src/types/not-field.d.ts
-/** The event handlers provided by a field instance for binding to native or custom inputs. */
+/**
+ * Native DOM event handlers exposed by a field.
+ * Spread onto a native input or bind individually to custom components.
+ *
+ * ```vue
+ * <!-- spread -->
+ * <input v-bind="events" />
+ *
+ * <!-- individual -->
+ * <CustomCombobox @focusout="onBlur" @pick="onChange" />
+ * ```
+ */
 type NotFieldEvents = {
-  /** Triggered when the field loses focus */onBlur: () => void; /** Triggered on every keystroke or value change */
-  onInput: () => void; /** Triggered when the field value is committed */
-  onChange: () => void; /** Triggered when the field gains focus */
+  /** Triggered when the field loses focus. */onBlur: () => void; /** Triggered on every keystroke or value change. */
+  onInput: () => void; /** Triggered when the field value is committed. */
+  onChange: () => void; /** Triggered when the field gains focus. */
   onFocus: () => void;
 };
-/**
- * Props for the NotField component
- * @template TSchema The validation schema type derived from ObjectSchema.
- * @template TPath The dot-separated path to the field within the form state.
- */
-type NotFieldProps<TSchema extends ObjectSchema, TPath extends Paths<StandardSchemaV1.InferInput<TSchema>>> = {
-  /** The dot-separated path to the field within the form state */path: TPath; /** Optional form instance — takes priority over injected context */
-  form?: NotFormInstance<TSchema>;
+/** Props for the `NotField` component. */
+type NotFieldProps = {
+  /** Dot-separated path to this field within the form values. */path: string;
+  /**
+   * Explicit form instance override.
+   * Takes priority over the instance provided by a `NotForm` ancestor.
+   * Required when using `NotField` outside of a `NotForm` (singleton fields).
+   *
+   * ```vue
+   * <NotField :form="form" path="email" v-slot="{ events }">
+   *   <input v-bind="events" />
+   * </NotField>
+   * ```
+   */
+  form?: NotFormInstance<any>;
   /**
    * Per-field validation trigger overrides.
-   * Merged over the form-wide validateOn config — only the keys you specify are overridden.
+   * Merged over the form-wide `validateOn` — only the keys you specify are overridden.
+   *
+   * ```vue
+   * <!-- form validates on blur only, but this field also validates on every input -->
+   * <NotField :validateOn="{ onInput: true }" path="username" />
+   * ```
    */
   validateOn?: Partial<Record<ValidationTrigger, boolean>>;
 };
 /**
- * The core state and methods provided by a field instance.
- * @template TSchema The validation schema type derived from ObjectSchema.
- * @template TPath The dot-separated path to the field within the form state.
+ * Everything available inside the `NotField` default slot.
+ * @template TSchema The validation schema type derived from `ObjectSchema`.
  */
-type NotFieldInstance<TSchema extends ObjectSchema, TPath extends Paths<StandardSchemaV1.InferInput<TSchema>>> = {
-  /** The dot-separated path to the field within the form state */path: TPath; /** The current value of the field */
-  value: any; /** Whether the field is currently being validated */
-  isValidating: boolean; /** Validates this field against the form schema */
-  validate: () => ReturnType<NotFormInstance<TSchema>['validateField']>; /** The validation issues for this field */
-  errors: StandardSchemaV1.Issue[]; /** Marks the field as touched */
-  touch: () => void; /** Marks the field as not touched */
-  unTouch: () => void; /** Marks the field as dirty */
-  dirty: () => void; /** Marks the field as not dirty */
-  unDirty: () => void;
+type NotFieldSlotProps<TSchema extends ObjectSchema> = {
+  /** The dot-separated path to this field. */path: string;
+  /**
+   * The current value of this field — read-only snapshot for display purposes.
+   * Do not mutate directly or use with `v-model`.
+   * For two-way binding use `v-model="form.values.fieldName"` instead.
+   */
+  value: any; /** All validation issues for this field from the last validation run. */
+  errors: StandardSchemaV1.Issue[]; /** Whether this field currently has no validation errors. */
+  isValid: boolean; /** Whether the user has interacted with this field, or the form has been submitted. */
+  isTouched: boolean; /** Whether this field's current value differs from its initial value. */
+  isDirty: boolean; /** Whether an async validator is currently running for this field. */
+  isValidating: boolean;
+  /**
+   * Manually triggers validation for this field.
+   * Useful for custom inputs that manage their own interaction events.
+   */
+  validate: () => ReturnType<NotFormInstance<TSchema>['validateField']>;
   /**
    * All event handlers combined — spread directly onto native inputs.
-   * @example <input v-bind="events" />
+   *
+   * ```vue
+   * <input v-bind="events" />
+   * ```
    */
-  events: NotFieldEvents; /** Triggered when the field loses focus */
-  onBlur: NotFieldEvents['onBlur']; /** Triggered on every keystroke or value change */
-  onInput: NotFieldEvents['onInput']; /** Triggered when the field value is committed */
-  onChange: NotFieldEvents['onChange']; /** Triggered when the field gains focus */
+  events: NotFieldEvents; /** Triggered when the field loses focus. */
+  onBlur: NotFieldEvents['onBlur']; /** Triggered on every keystroke or value change. */
+  onInput: NotFieldEvents['onInput']; /** Triggered when the field value is committed. */
+  onChange: NotFieldEvents['onChange']; /** Triggered when the field gains focus. */
   onFocus: NotFieldEvents['onFocus'];
 };
 /**
- * Slots for the NotField component
- * @template TSchema The validation schema type derived from ObjectSchema.
- * @template TPath The dot-separated path to the field within the form state.
+ * Slots for the `NotField` component.
+ * @template TSchema The validation schema type derived from `ObjectSchema`.
  */
-type NotFieldSlots<TSchema extends ObjectSchema, TPath extends Paths<StandardSchemaV1.InferInput<TSchema>>> = {
-  /** The default slot receives the full field instance */default: (props: NotFieldInstance<TSchema, TPath>) => [];
+type NotFieldSlots<TSchema extends ObjectSchema> = {
+  /** The default slot receives the full field state and event handlers. */default: (props: NotFieldSlotProps<TSchema>) => [];
 };
 //#endregion
 //#region src/components/not-field.vue.d.ts
-declare const __VLS_export: <TSchema extends ObjectSchema, TPath extends Paths<StandardSchemaV1.InferInput<TSchema>>>(__VLS_props: NonNullable<Awaited<typeof __VLS_setup>>["props"], __VLS_ctx?: __VLS_PrettifyLocal<Pick<NonNullable<Awaited<typeof __VLS_setup>>, "attrs" | "emit" | "slots">>, __VLS_exposed?: NonNullable<Awaited<typeof __VLS_setup>>["expose"], __VLS_setup?: Promise<{
-  props: _$vue.PublicProps & __VLS_PrettifyLocal<NotFieldProps<TSchema, TPath>> & (typeof globalThis extends {
+declare const __VLS_export$1: <TSchema extends ObjectSchema>(__VLS_props: NonNullable<Awaited<typeof __VLS_setup>>["props"], __VLS_ctx?: __VLS_PrettifyLocal<Pick<NonNullable<Awaited<typeof __VLS_setup>>, "attrs" | "emit" | "slots">>, __VLS_exposed?: NonNullable<Awaited<typeof __VLS_setup>>["expose"], __VLS_setup?: Promise<{
+  props: _$vue.PublicProps & __VLS_PrettifyLocal<NotFieldProps> & (typeof globalThis extends {
     __VLS_PROPS_FALLBACK: infer P;
   } ? P : {});
   expose: (exposed: {}) => void;
   attrs: any;
-  slots: NotFieldSlots<TSchema, TPath>;
+  slots: NotFieldSlots<TSchema>;
   emit: {};
 }>) => _$vue.VNode & {
   __ctx?: Awaited<typeof __VLS_setup>;
 };
-declare const _default: typeof __VLS_export;
+declare const _default: typeof __VLS_export$1;
 type __VLS_PrettifyLocal<T> = (T extends any ? { [K in keyof T]: T[K] } : { [K in keyof T as K]: T[K] }) & {};
 //#endregion
-export { ArraySchema, DeepPartial, _default as NotField, NotFieldEvents, NotFieldInstance, NotFieldProps, NotFieldSlots, _default$1 as NotForm, NotFormInstance, NotFormProps, NotFormSlots, ObjectSchema, Paths, UseNotFormConfig, ValidationTrigger, useNotForm };
+//#region src/types/not-message.d.ts
+/** Props for the `NotMessage` component. */
+type NotMessageProps = {
+  /** The name/path of the field whose error message should be displayed */path: string; /** HTML Tag `NotMessage` should render as - default is `span`. */
+  as?: string;
+  /**
+   * Explicit form instance override.
+   * Takes priority over the instance provided by a `NotForm` ancestor.
+   * Required when using `NotMessage` outside of a `NotForm` (singleton fields).
+   *
+   * ```vue
+   * <NotMessage :form="form" path="email" />
+   * ```
+   */
+  form?: NotFormInstance<any>;
+};
+/** Everything available inside the `NotMessage` default slot. */
+type NotMessageSlotProps = {
+  /** The first active validation error message for the specified field */message?: string; /** Attributes passed to the `NotMessage` component */
+  attributes?: ReturnType<typeof useAttrs>;
+};
+/** Slots for the `NotMessage` component. */
+type NotMessageSlots = {
+  /** The default slot receives the error message context for custom rendering */default: (props: NotMessageSlotProps) => [];
+};
+//#endregion
+//#region src/components/not-message.vue.d.ts
+type __VLS_Slots = NotMessageSlots;
+declare const __VLS_base: _$vue.DefineComponent<NotMessageProps, {}, {}, {}, {}, _$vue.ComponentOptionsMixin, _$vue.ComponentOptionsMixin, {}, string, _$vue.PublicProps, Readonly<NotMessageProps> & Readonly<{}>, {
+  as: string;
+}, {}, {}, {}, string, _$vue.ComponentProvideOptions, false, {}, any>;
+declare const __VLS_export: __VLS_WithSlots<typeof __VLS_base, __VLS_Slots>;
+declare const _default$2: typeof __VLS_export;
+type __VLS_WithSlots<T, S> = T & {
+  new (): {
+    $slots: S;
+  };
+};
+//#endregion
+export { ArraySchema, DeepPartial, _default as NotField, NotFieldEvents, NotFieldProps, NotFieldSlotProps, NotFieldSlots, _default$1 as NotForm, NotFormInstance, NotFormProps, NotFormSlots, _default$2 as NotMessage, NotMessageProps, NotMessageSlotProps, NotMessageSlots, ObjectSchema, Paths, UseNotFormConfig, ValidationMode, ValidationTrigger, useNotForm };