@quantiya/codevibe-claude-plugin 2.0.4 → 2.0.5

package/node_modules/@quantiya/codevibe-core/node_modules/type-fest/source/object-merge.d.ts

@@ -0,0 +1,199 @@
+import type {If} from './if.d.ts';
+import type {NormalizedKeys} from './internal/object.d.ts';
+import type {IfNotAnyOrNever, IsExactOptionalPropertyTypesEnabled, MapsSetsOrArrays} from './internal/type.d.ts';
+import type {IsNever} from './is-never.d.ts';
+import type {IsOptionalKeyOf} from './is-optional-key-of.d.ts';
+import type {OmitIndexSignature} from './omit-index-signature.d.ts';
+import type {PickIndexSignature} from './pick-index-signature.d.ts';
+import type {RequiredKeysOf} from './required-keys-of.d.ts';
+import type {Simplify} from './simplify.d.ts';
+
+/**
+Merge two object types into a new object type, where keys from the second override keys from the first.
+
+@example
+```ts
+import type {ObjectMerge} from 'type-fest';
+
+type PartialOverride = ObjectMerge<{foo: string; bar: string}, {foo: number; baz: number}>;
+//=> {foo: number; baz: number; bar: string}
+
+type CompleteOverride = ObjectMerge<{foo: string; bar: number}, {foo: number; bar: string; baz: boolean}>;
+//=> {foo: number; bar: string; baz: boolean}
+
+type NoOverride = ObjectMerge<{foo: string; bar: number}, {baz: boolean; qux: bigint}>;
+//=> {baz: boolean; qux: bigint; foo: string; bar: number}
+```
+
+Use-cases:
+
+Can be used to accurately type object spread and `Object.assign`. The built-in inference for these operations can sometimes be unsound, especially when index signatures are involved.
+
+In the following example, both object spread and `Object.assign` produce a type that allows unsafe usage, whereas `ObjectMerge` produces a type that prevents this unsafe access.
+
+@example
+```ts
+import type {ObjectMerge} from 'type-fest';
+
+const left: {a: string} = {a: '1'};
+const right: {[x: string]: number} = {a: 1};
+
+const inferred = {...left, ...right};
+//=> {a: string}
+
+inferred.a.toUpperCase(); // No compile time error, but fails at runtime.
+
+const objectAssign = Object.assign(left, right);
+//=> {a: string} & {[x: string]: number}
+
+objectAssign.a.toUpperCase(); // No compile time error, but fails at runtime.
+
+declare const objectMerge: ObjectMerge<typeof left, typeof right>;
+//=> {[x: string]: string | number; a: string | number}
+
+// @ts-expect-error
+objectMerge.a.toUpperCase(); // Correctly errors at compile time.
+```
+
+Can be used to merge generic type arguments.
+
+In the following example, object spread without `ObjectMerge` produces an intersection type that is not particularly usable, whereas `ObjectMerge` produces a correctly merged and usable result.
+
+@example
+```ts
+import type {ObjectMerge} from 'type-fest';
+
+function withoutObjectMerge<T extends object, U extends object>(left: T, right: U) {
+	return {...left, ...right};
+}
+
+const result1 = withoutObjectMerge({a: 1}, {a: 'one'});
+//=> {a: number} & {a: string}
+
+const {a} = result1;
+//=> never
+
+function withObjectMerge<T extends object, U extends object>(left: T, right: U) {
+	return {...left, ...right} as unknown as ObjectMerge<T, U>;
+}
+
+const result2 = withObjectMerge({b: 1}, {b: 'one'});
+//=> {b: string}
+
+const {b} = result2;
+//=> string
+```
+
+Note: If you want a simple merge where properties from the second object always override properties from the first object without considering runtime implications, refer to the {@link Merge} type.
+
+@see {@link Merge}
+@category Object
+*/
+export type ObjectMerge<First extends object, Second extends object> =
+	IfNotAnyOrNever<First, {
+		ifNot: IfNotAnyOrNever<Second, {
+			ifNot: First extends unknown // For distributing `First`
+				? Second extends unknown // For distributing `Second`
+					? First extends MapsSetsOrArrays
+						? unknown
+						: Second extends MapsSetsOrArrays
+							? unknown
+							: _ObjectMerge<
+								First,
+								Second,
+								NormalizedLiteralKeys<First>,
+								NormalizedLiteralKeys<Second>,
+								IsExactOptionalPropertyTypesEnabled extends true ? Required<First> : First,
+								IsExactOptionalPropertyTypesEnabled extends true ? Required<Second> : Second
+							>
+					: never // Should never happen
+				: never; // Should never happen
+		}>;
+		ifAny: First & Second;
+	}>;
+
+type _ObjectMerge<
+	First extends object,
+	Second extends object,
+	NormalizedFirstLiteralKeys extends PropertyKey,
+	NormalizedSecondLiteralKeys extends PropertyKey,
+	NormalizedFirst extends object,
+	NormalizedSecond extends object,
+> = Simplify<{
+	// Map over literal keys of `Second`, except those that are optional and also present in `First`.
+	-readonly [P in keyof Second as P extends NormalizedSecondLiteralKeys
+		? P extends NormalizedFirstLiteralKeys
+			? If<IsOptionalKeyOf<Second, P>, never, P>
+			: P
+		: never]:
+			| Second[P]
+			| (P extends NormalizedKeys<keyof PickIndexSignature<First>>
+				? If<IsOptionalKeyOf<Second, P>, First[NormalizedKeys<P> & keyof First], never>
+				: never)
+} & {
+	// Map over literal keys of `First`, except those that are not present in `Second`.
+	-readonly [P in keyof First as P extends NormalizedFirstLiteralKeys
+		? P extends NormalizedSecondLiteralKeys
+			? never
+			: P
+		: never]:
+			| First[P]
+				// If there's a matching index signature in `Second`, then add the type for it as well,
+				// for example, in `ObjectMerge<{a: string}, {[x: string]: number}>`, `a` is of type `string | number`.
+			| (P extends NormalizedKeys<keyof Second>
+				? Second[NormalizedKeys<P> & keyof Second]
+				: never);
+} & {
+	// Map over non-literal keys of `Second`.
+	-readonly [P in keyof Second as P extends NormalizedSecondLiteralKeys ? never : P]:
+		| Second[P]
+			// If there's a matching key in `First`, then add the type for it as well,
+			// for example, in `ObjectMerge<{a: number}, {[x: string]: string}>`,
+			// the resulting type is `{[x: string]: number | string; a: number | string}`.
+			// But, exclude keys from `First` that would surely get overwritten,
+			// for example, in `ObjectMerge<{a: number}, {[x: string]: string; a: string}>`,
+			// `a` from `First` would get overwritten by `a` from `Second`, so don't add type for it.
+		| (NormalizedKeys<P> & Exclude<keyof First, NormalizedKeys<RequiredKeysOf<OmitIndexSignature<Second>>>> extends infer NonOverwrittenKeysOfFirst
+			? If<IsNever<NonOverwrittenKeysOfFirst>, // This check is required because indexing with `never` doesn't always yield `never`, for example, `{[x: string]: number}[never]` results in `number`.
+				never,
+				NormalizedFirst[NonOverwrittenKeysOfFirst & keyof NormalizedFirst]>
+			: never); // Should never happen
+} & {
+	// Map over non-literal keys of `First`.
+	-readonly [P in keyof First as P extends NormalizedFirstLiteralKeys ? never : P]:
+		| First[P]
+		| If<IsNever<NormalizedKeys<P> & keyof Second>, // This check is required because indexing with `never` doesn't always yield `never`, for example, `{[x: string]: number}[never]` results in `number`.
+			never,
+			NormalizedSecond[NormalizedKeys<P> & keyof NormalizedSecond]>;
+} & {
+	// Handle optional keys of `Second` that are also present in `First`.
+	// Map over `First` instead of `Second` because the modifier is in accordance with `First`.
+	-readonly [P in keyof First as P extends NormalizedFirstLiteralKeys
+		? P extends NormalizedSecondLiteralKeys
+			? If<IsOptionalKeyOf<Second, NormalizedKeys<P> & keyof Second>, P, never>
+			: never
+		: never]:
+			| First[P]
+			| NormalizedSecond[NormalizedKeys<P> & keyof NormalizedSecond]
+}>;
+
+/**
+Get literal keys of a type, including both string and number representations wherever applicable.
+
+@example
+```ts
+type A = NormalizedLiteralKeys<{0: string; '1'?: number; foo: boolean}>;
+//=> 0 | '0' | 1 | '1' | 'foo'
+
+type B = NormalizedLiteralKeys<{[x: string]: string | number; 0: string; '1'?: number}>;
+//=> 0 | '0' | 1 | '1'
+
+type C = NormalizedLiteralKeys<{[x: string]: unknown}>;
+//=> never
+```
+*/
+type NormalizedLiteralKeys<Type> = Type extends unknown // For distributing `Type`
+	? NormalizedKeys<keyof OmitIndexSignature<Type>>
+	: never; // Should never happen
+
+export {};

package/node_modules/@quantiya/codevibe-core/node_modules/type-fest/source/omit-deep.d.ts

@@ -0,0 +1,153 @@
+import type {ArraySplice} from './array-splice.d.ts';
+import type {ExactKey, IsArrayReadonly, NonRecursiveType, SetArrayAccess, ToString} from './internal/index.d.ts';
+import type {IsEqual} from './is-equal.d.ts';
+import type {IsNever} from './is-never.d.ts';
+import type {LiteralUnion} from './literal-union.d.ts';
+import type {Paths} from './paths.d.ts';
+import type {SimplifyDeep} from './simplify-deep.d.ts';
+import type {UnionToTuple} from './union-to-tuple.d.ts';
+import type {UnknownArray} from './unknown-array.d.ts';
+
+/**
+Omit properties from a deeply-nested object.
+
+It supports recursing into arrays.
+
+It supports removing specific items from an array, replacing each removed item with unknown at the specified index.
+
+Use-case: Remove unneeded parts of complex objects.
+
+Use [`Omit<T>`](https://www.typescriptlang.org/docs/handbook/utility-types.html#omittype-keys) if you only need one level deep.
+
+@example
+```
+import type {OmitDeep} from 'type-fest';
+
+type Info = {
+	userInfo: {
+		name: string;
+		uselessInfo: {
+			foo: string;
+		};
+	};
+};
+
+type UsefulInfo = OmitDeep<Info, 'userInfo.uselessInfo'>;
+//=> {userInfo: {name: string}}
+
+// Supports removing multiple paths
+type Info1 = {
+	userInfo: {
+		name: string;
+		uselessField: string;
+		uselessInfo: {
+			foo: string;
+		};
+	};
+};
+
+type UsefulInfo1 = OmitDeep<Info1, 'userInfo.uselessInfo' | 'userInfo.uselessField'>;
+//=> {userInfo: {name: string}}
+
+// Supports array
+type A = OmitDeep<[1, 'foo', 2], '1'>;
+//=> [1, unknown, 2]
+
+// Supports recursing into array
+
+type Info2 = {
+	address: [
+		{
+			street: string;
+		},
+		{
+			street2: string;
+			foo: string;
+		},
+	];
+};
+
+type AddressInfo = OmitDeep<Info2, 'address.1.foo'>;
+//=> {address: [{street: string}, {street2: string}]}
+```
+
+@category Object
+@category Array
+*/
+export type OmitDeep<T, PathUnion extends LiteralUnion<Paths<T>, string>> =
+	SimplifyDeep<
+		OmitDeepHelper<T, UnionToTuple<PathUnion>>,
+		UnknownArray>;
+
+/**
+Internal helper for {@link OmitDeep}.
+
+Recursively transforms `T` by applying {@link OmitDeepWithOnePath} for each path in `PathTuple`.
+*/
+type OmitDeepHelper<T, PathTuple extends UnknownArray> =
+	PathTuple extends [infer Path, ...infer RestPaths]
+		? OmitDeepHelper<OmitDeepWithOnePath<T, Path & (string | number)>, RestPaths>
+		: T;
+
+/**
+Omit one path from the given object/array.
+*/
+type OmitDeepWithOnePath<T, Path extends string | number> =
+	T extends NonRecursiveType
+		? T
+		: T extends UnknownArray ? SetArrayAccess<OmitDeepArrayWithOnePath<T, Path>, IsArrayReadonly<T>>
+			: T extends object ? OmitDeepObjectWithOnePath<T, Path>
+				: T;
+
+/**
+Omit one path from the given object.
+*/
+type OmitDeepObjectWithOnePath<ObjectT extends object, P extends string | number> =
+	P extends `${infer RecordKeyInPath}.${infer SubPath}`
+		? {
+			[Key in keyof ObjectT]:
+			IsEqual<RecordKeyInPath, ToString<Key>> extends true
+				? ExactKey<ObjectT, Key> extends infer RealKey
+					? RealKey extends keyof ObjectT
+						? OmitDeepWithOnePath<ObjectT[RealKey], SubPath>
+						: ObjectT[Key]
+					: ObjectT[Key]
+				: ObjectT[Key]
+		}
+		: ExactKey<ObjectT, P> extends infer Key
+			? IsNever<Key> extends true
+				? ObjectT
+				: Key extends PropertyKey
+					? Omit<ObjectT, Key>
+					: ObjectT
+			: ObjectT;
+
+/**
+Omit one path from from the given array.
+
+It replaces the item to `unknown` at the given index.
+
+@example
+```
+type A = OmitDeepArrayWithOnePath<[10, 20, 30, 40], 2>;
+//=> type A = [10, 20, unknown, 40];
+```
+*/
+type OmitDeepArrayWithOnePath<ArrayType extends UnknownArray, P extends string | number> =
+	// Handle paths that are `${number}.${string}`
+	P extends `${infer ArrayIndex extends number}.${infer SubPath}`
+		// If `ArrayIndex` is equal to `number`
+		? number extends ArrayIndex
+			? Array<OmitDeepWithOnePath<NonNullable<ArrayType[number]>, SubPath>>
+			// If `ArrayIndex` is a number literal
+			: ArraySplice<ArrayType, ArrayIndex, 1, [OmitDeepWithOnePath<NonNullable<ArrayType[ArrayIndex]>, SubPath>]>
+		// If the path is equal to `number`
+		: P extends `${infer ArrayIndex extends number}`
+			// If `ArrayIndex` is `number`
+			? number extends ArrayIndex
+				? []
+				// If `ArrayIndex` is a number literal
+				: ArraySplice<ArrayType, ArrayIndex, 1, [unknown]>
+			: ArrayType;
+
+export {};

package/node_modules/@quantiya/codevibe-core/node_modules/type-fest/source/omit-index-signature.d.ts

@@ -0,0 +1,98 @@
+/**
+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
+*/
+export type OmitIndexSignature<ObjectType> = {
+	[KeyType in keyof ObjectType as {} extends Record<KeyType, unknown>
+		? never
+		: KeyType]: ObjectType[KeyType];
+};
+
+export {};

package/node_modules/@quantiya/codevibe-core/node_modules/type-fest/source/opaque.d.ts

@@ -0,0 +1,3 @@
+export type * from './tagged.d.ts';
+
+export {};

package/node_modules/@quantiya/codevibe-core/node_modules/type-fest/source/optional-keys-of.d.ts

@@ -0,0 +1,46 @@
+import type {IsOptionalKeyOf} from './is-optional-key-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
+*/
+export 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; // Should never happen
+
+export {};

package/node_modules/@quantiya/codevibe-core/node_modules/type-fest/source/optional.d.ts

@@ -0,0 +1,31 @@
+/**
+Create a type that represents either the value or `undefined`, while stripping `null` from the type.
+
+Use-cases:
+- Enforcing the practice of using `undefined` instead of `null` as the "absence of value" marker.
+- Converting APIs that return `null` (DOM, JSON, legacy libraries) to use `undefined` consistently.
+
+@example
+```
+import type {Optional} from 'type-fest';
+
+// Adds `undefined` to the type
+type MaybeNumber = Optional<number>;
+//=> number | undefined
+
+// Strips `null` from the type
+type NullableString = Optional<string | null>;
+//=> string | undefined
+
+type Config = {
+	name: string;
+	description: Optional<string>;
+	//=> string | undefined
+};
+```
+
+@category Utilities
+*/
+export type Optional<Value> = Exclude<Value, null> | undefined;
+
+export {};

package/node_modules/@quantiya/codevibe-core/node_modules/type-fest/source/or-all.d.ts

@@ -0,0 +1,73 @@
+import type {SomeExtend} from './some-extend.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}
+*/
+export type OrAll<T extends readonly boolean[]> = SomeExtend<T, true>;
+
+export {};

package/node_modules/@quantiya/codevibe-core/node_modules/type-fest/source/or.d.ts

@@ -0,0 +1,82 @@
+import type {OrAll} from './or-all.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}
+*/
+export type Or<A extends boolean, B extends boolean> = OrAll<[A, B]>;
+
+export {};