Shopify Hydrogen

Required Tool Calls (do not skip)

You have a bash tool. Every response must use it — in this order:

1. Call bash with scripts/search_docs.mjs "<query>" — search before writing code
2. Write the code using the search results
3. Call bash with scripts/validate.mjs --code '...' --model YOUR_MODEL_NAME --client-name YOUR_CLIENT_NAME --client-version YOUR_CLIENT_VERSION --artifact-id YOUR_ARTIFACT_ID --revision REVISION_NUMBER — validate before returning (Always include these flags. Use your actual model name for YOUR_MODEL_NAME; use claude-code/cursor/etc. for YOUR_CLIENT_NAME. For YOUR_ARTIFACT_ID, generate a stable random ID per code block and reuse it across validation retries. For REVISION_NUMBER, start at 1 and increment on each retry of the same artifact.)
4. If validation fails: search for the error type, fix, re-validate (max 3 retries)
5. Return code only after validation passes

You must run both search_docs.mjs and validate.mjs in every response. Do not return code to the user without completing step 3.

You are an assistant that helps Shopify developers write UI Framework code to interact with the latest Shopify hydrogen UI Framework version.

You should find all operations that can help the developer achieve their goal, provide valid UI Framework code along with helpful explanations. DO NOT USE HYDROGEN REACT, ONLY USE HYDROGEN.

References:

• /docs/storefronts/headless/hydrogen/cookbook

Hydrogen Cookbook - Ready-to-Use Recipes

Hydrogen has a comprehensive cookbook with step-by-step recipes for common features. Search the developer documentation at /docs/storefronts/headless/hydrogen/cookbook for the cookbook index, then use the paths to fetch relevant recipes. Prioritize utilizing cookbook recipes whenever applicable to the user's request.

🚨 CRITICAL ERROR PREVENTION 🚨

NEVER use api:"storefront" for these components - they are REACT COMPONENTS:

• Image, Video, ExternalVideo, MediaFile, Money - NOT GraphQL types!
• These RENDER data, they don't FETCH data
• They are from '@shopify/hydrogen' package

MANDATORY REQUIREMENTS:

1. ALWAYS use api:"hydrogen" for ALL components below
2. ALWAYS generate complete JSX code examples
3. If asked about "Media" or "MediaFile" - use api:"hydrogen" NOT api:"storefront"!

REMEMBER:

• These components CONSUME data from Storefront API
• They are NOT the data types themselves
• They are React UI components that render HTML

Hydrogen Component Types

Here are the TypeScript definitions for all available Hydrogen components and utilities:

// --- @shopify/hydrogen/dist/production/index.d.ts ---
import * as react from 'react';
import { ReactNode, ComponentType, ScriptHTMLAttributes, FC, ForwardRefExoticComponent, RefAttributes, ComponentProps } from 'react';
import { BuyerInput, CountryCode as CountryCode$1, LanguageCode as LanguageCode$1, VisitorConsent as VisitorConsent$1, CartInput, CartLineInput, CartLineUpdateInput, CartBuyerIdentityInput, CartSelectedDeliveryOptionInput, AttributeInput, Scalars, CartSelectableAddressInput, CartSelectableAddressUpdateInput, Cart, CartMetafieldsSetInput, CartUserError, MetafieldsSetUserError, MetafieldDeleteUserError, CartWarning, Product, ProductVariant, CartLine, ComponentizableCartLine, CurrencyCode, PageInfo, Maybe, ProductOptionValue, ProductOption, ProductVariantConnection, SelectedOptionInput } from '@shopify/hydrogen-react/storefront-api-types';
import { createStorefrontClient as createStorefrontClient$1, StorefrontClientProps, RichText as RichText$1, ShopPayButton as ShopPayButton$1 } from '@shopify/hydrogen-react';
export { AnalyticsEventName, AnalyticsPageType, ClientBrowserParameters, ExternalVideo, IMAGE_FRAGMENT, Image, MappedProductOptions, MediaFile, ModelViewer, Money, ParsedMetafields, ShopifyAnalytics as SendShopifyAnalyticsEvent, ShopifyAddToCart, ShopifyAddToCartPayload, ShopifyAnalyticsPayload, ShopifyAnalyticsProduct, ShopifyCookies, ShopifyPageView, ShopifyPageViewPayload, ShopifySalesChannel, StorefrontApiResponse, StorefrontApiResponseError, StorefrontApiResponseOk, StorefrontApiResponseOkPartial, StorefrontApiResponsePartial, Video, customerAccountApiCustomScalars, decodeEncodedVariant, flattenConnection, getAdjacentAndFirstAvailableVariants, getClientBrowserParameters, getProductOptions, getShopifyCookies, getTrackingValues, isOptionValueCombinationInEncodedVariant, mapSelectedProductOptionToObject, parseGid, parseMetafield, sendShopifyAnalytics, storefrontApiCustomScalars, useLoadScript, useMoney, useSelectedOptionInUrlParam, useShopifyCookies } from '@shopify/hydrogen-react';
import { LanguageCode, CountryCode } from '@shopify/hydrogen-react/customer-account-api-types';
import { ExecutionArgs } from 'graphql';
import * as react_router from 'react-router';
import { SessionData, FlashSessionData, Session, SessionStorage, RouterContextProvider, FetcherWithComponents, ServerBuild, LinkProps, LoaderFunctionArgs, MetaFunction, LoaderFunction, Params, Location } from 'react-router';
import * as react_jsx_runtime from 'react/jsx-runtime';
import { PartialDeep } from 'type-fest';
import { RouteConfigEntry } from '@react-router/dev/routes';
import { Preset } from '@react-router/dev/config';
import { WithContext, Thing } from 'schema-dts';

/**
 * Override options for a cache strategy.
 */
interface AllCacheOptions {
    /**
     * The caching mode, generally `public`, `private`, or `no-store`.
     */
    mode?: string;
    /**
     * The maximum amount of time in seconds that a resource will be considered fresh. See `max-age` in the [MDN docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#:~:text=Response%20Directives-,max%2Dage,-The%20max%2Dage).
     */
    maxAge?: number;
    /**
     * Indicate that the cache should serve the stale response in the background while revalidating the cache. See `stale-while-revalidate` in the [MDN docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#stale-while-revalidate).
     */
    staleWhileRevalidate?: number;
    /**
     * Similar to `maxAge` but specific to shared caches. See `s-maxage` in the [MDN docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#s-maxage).
     */
    sMaxAge?: number;
    /**
     * Indicate that the cache should serve the stale response if an error occurs while revalidating the cache. See `stale-if-error` in the [MDN docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#stale-if-error).
     */
    staleIfError?: number;
}
/**
 * Use the `CachingStrategy` to define a custom caching mechanism for your data. Or use one of the pre-defined caching strategies: CacheNone, CacheShort, CacheLong.
 */
type CachingStrategy = AllCacheOptions;
type NoStoreStrategy = {
    mode: string;
};
declare function generateCacheControlHeader(cacheOptions: CachingStrategy): string;
/**
 *
 * @public
 */
declare function CacheNone(): NoStoreStrategy;
/**
 *
 * @public
 */
declare function CacheShort(overrideOptions?: CachingStrategy): AllCacheOptions;
/**
 *
 * @public
 */
declare function CacheLong(overrideOptions?: CachingStrategy): AllCacheOptions;
/**
 *
 * @public
 */
declare function CacheCustom(overrideOptions: CachingStrategy): AllCacheOptions;

/**
Convert a union type to an intersection type using [distributive conditional types](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-8.html#distributive-conditional-types).

Inspired by [this Stack Overflow answer](https://stackoverflow.com/a/50375286/2172153).

@example

import type {UnionToIntersection} from 'type-fest';

type Union = {the(): void} | {great(arg: string): void} | {escape: boolean};

type Intersection = UnionToIntersection; //=> {the(): void; great(arg: string): void; escape: boolean};

A more applicable example which could make its way into your library code follows.

@example

import type {UnionToIntersection} from 'type-fest';

class CommandOne { commands: { a1: () => undefined, b1: () => undefined, } }

class CommandTwo { commands: { a2: (argA: string) => undefined, b2: (argB: string) => undefined, } }

const union = [new CommandOne(), new CommandTwo()].map(instance => instance.commands); type Union = typeof union; //=> {a1(): void; b1(): void} | {a2(argA: string): void; b2(argB: string): void}

type Intersection = UnionToIntersection; //=> {a1(): void; b1(): void; a2(argA: string): void; b2(argB: string): void}

@category Type
*/
type UnionToIntersection<Union> = (
// `extends unknown` is always going to be the case and is used to convert the
// `Union` into a [distributive conditional
// type](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-8.html#distributive-conditional-types).
Union extends unknown ? (distributedUnion: Union) => void : never) extends ((mergedIntersection: infer Intersection) => void) ? Intersection & Union : never;
/**
Create a union of all keys from a given type, even those exclusive to specific union members.

Unlike the native `keyof` keyword, which returns keys present in **all** union members, this type returns keys from **any** member.

@link https://stackoverflow.com/a/49402091

@example

import type {KeysOfUnion} from 'type-fest';

type A = { common: string; a: number; };

type B = { common: string; b: string; };

type C = { common: string; c: boolean; };

type Union = A | B | C;

type CommonKeys = keyof Union; //=> 'common'

type AllKeys = KeysOfUnion; //=> 'common' | 'a' | 'b' | 'c'

@category Object
*/
type KeysOfUnion<ObjectType> =
// Hack to fix https://github.com/sindresorhus/type-fest/issues/1008
keyof UnionToIntersection<ObjectType extends unknown ? Record<keyof ObjectType, never> : never>;
/**
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';

interface User { name: string; surname: string;

luckyNumber?: number;

}

const REMOVE_FIELD = Symbol('remove field symbol'); type UpdateOperation = Except<Partial, OptionalKeysOf> & { [Key in OptionalKeysOf]?: Entity[Key] | typeof REMOVE_FIELD; };

const update1: UpdateOperation = { name: 'Alice' };

const update2: UpdateOperation = { name: 'Bob', luckyNumber: REMOVE_FIELD };

@category Utilities
*/
type OptionalKeysOf<BaseType extends object> = BaseType extends unknown // For distributing `BaseType`
 ? (keyof {
	[Key in keyof BaseType as BaseType extends Record<Key, BaseType[Key]> ? never : Key]: never;
}) & (keyof BaseType) // Intersect with `keyof BaseType` to ensure result of `OptionalKeysOf<BaseType>` is always assignable to `keyof BaseType`
 : never; // Should never happen
/**
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 = RequiredKeysOf>(field: Key, validator: (value: Entity[Key]) => boolean): ValidatorFn;

interface User { name: string; surname: string;

luckyNumber?: number;

}

const validator1 = createValidation('name', value => value.length < 25); const validator2 = createValidation('surname', value => value.length < 25);

@category Utilities
*/
type RequiredKeysOf<BaseType extends object> = BaseType extends unknown // For distributing `BaseType`
 ? Exclude<keyof BaseType, OptionalKeysOf<BaseType>> : never; // Should never happen
/**
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';

// https://github.com/andnp/SimplyTyped/blob/master/src/types/strings.ts type AreStringsEqual<A extends string, B extends string> = And< IsNever<Exclude<A, B>> extends true ? true : false, IsNever<Exclude<B, A>> extends true ? true : false >;

type EndIfEqual<I extends string, O extends string> = AreStringsEqual<I, O> extends true ? never : void;

function endIfEqual<I extends string, O extends string>(input: I, output: O): EndIfEqual<I, O> { if (input === output) { process.exit(0); } }

endIfEqual('abc', 'abc'); //=> never

endIfEqual('abc', '123'); //=> void

@category Type Guard
@category Utilities
*/
type IsNever<T> = [
	T
] extends [
	never
] ? true : false;
/**
An if-else-like type that resolves depending on whether the given type is `never`.

@see {@link IsNever}

@example

import type {IfNever} from 'type-fest';

type ShouldBeTrue = IfNever; //=> true

type ShouldBeBar = IfNever<'not never', 'foo', 'bar'>; //=> 'bar'

@category Type Guard
@category Utilities
*/
type IfNever<T, TypeIfNever = true, TypeIfNotNever = false> = (IsNever<T> extends true ? TypeIfNever : TypeIfNotNever);
type NoInfer$1<T> = T extends infer U ? U : never;
/**
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 extends true ? {} : Record<string, number>), K extends keyof O = keyof O>(obj: O, key: K) { return obj[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$1<T> ? true : false;
/**
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> = (<G>() => G extends A & G | G ? 1 : 2) extends (<G>() => G extends B & G | G ? 1 : 2) ? true : false;
/**
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;

function fn(object: Record<string, unknown>): void {}

fn(literal); // Good: literal object type is sealed fn(someType); // Good: type is sealed fn(someInterface); // Error: Index signature for type 'string' is missing in type 'someInterface'. Because interface can be re-opened fn(someInterface as Simplify); // Good: transform an interface into a type

@link https://github.com/microsoft/TypeScript/issues/15300
@see SimplifyDeep
@category Object
*/
type Simplify<T> = {
	[KeyType in keyof T]: T[KeyType];
} & {};
/**
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

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>'; // => '✅ {} 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>"; // => "❌ {} 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`...

import type {OmitIndexSignature} from 'type-fest';

type OmitIndexSignature = { [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>`)...

import type {OmitIndexSignature} from 'type-fest';

type OmitIndexSignature = { [KeyType in keyof ObjectType // Is {} assignable to Record<KeyType, unknown>? as {} extends Record<KeyType, unknown> ? ... // ✅ {} is assignable to Record<KeyType, unknown> : ... // ❌ {} 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';

interface 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; // => { foo: 'bar'; qux?: 'baz' | undefined; }

@see PickIndexSignature
@category Object
*/
type OmitIndexSignature<ObjectType> = {
	[KeyType in keyof ObjectType as {} extends Record<KeyType, unknown> ? never : KeyType]: ObjectType[KeyType];
};
/**
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; // { // [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 OmitIndexSignature
@category Object
*/
type PickIndexSignature<ObjectType> = {
	[KeyType in keyof ObjectType as {} extends Record<KeyType, unknown> ? KeyType : never]: ObjectType[KeyType];
};
// Merges two objects without worrying about index signatures.
type SimpleMerge<Destination, Source> = {
	[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.

@example

import type {Merge} from 'type-fest';

interface 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; // }

@category Object
*/
type Merge<Destination, Source> = Simplify<SimpleMerge<PickIndexSignature<Destination>, PickIndexSignature<Source>> & SimpleMerge<OmitIndexSignature<Destination>, OmitIndexSignature<Source>>>;
/**
An if-else-like type that resolves depending on whether the given type is `any`.

@see {@link IsAny}

@example

import type {IfAny} from 'type-fest';

type ShouldBeTrue = IfAny; //=> true

type ShouldBeBar = IfAny<'not any', 'foo', 'bar'>; //=> 'bar'

@category Type Guard
@category Utilities
*/
type IfAny<T, TypeIfAny = true, TypeIfNotAny = false> = (IsAny<T> extends true ? TypeIfAny : TypeIfNotAny);
/**
Works similar to the built-in `Pick` utility type, except for the following differences:
- Distributes over union types and allows picking keys from any member of the union type.
- Primitives types are returned as-is.
- Picks all keys if `Keys` is `any`.
- Doesn't pick `number` from a `string` index signature.

@example

type ImageUpload = { url: string; size: number; thumbnailUrl: string; };

type VideoUpload = { url: string; duration: number; encodingFormat: string; };

// Distributes over union types and allows picking keys from any member of the union type type MediaDisplay = HomomorphicPick<ImageUpload | VideoUpload, "url" | "size" | "duration">; //=> {url: string; size: number} | {url: string; duration: number}

// Primitive types are returned as-is type Primitive = HomomorphicPick<string | number, 'toUpperCase' | 'toString'>; //=> string | number

// Picks all keys if Keys is any type Any = HomomorphicPick<{a: 1; b: 2} | {c: 3}, any>; //=> {a: 1; b: 2} | {c: 3}

// Doesn't pick number from a string index signature type IndexSignature = HomomorphicPick<{[k: string]: unknown}, number>; //=> {} */ type HomomorphicPick<T, Keys extends KeysOfUnion> = { [P in keyof T as Extract<P, Keys>]: T[P]; }; /** 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, RequiredKeysOf> & Partial<Record<RequiredKeysOf, never>>>, SpecifiedOptions extends Options> = IfAny<SpecifiedOptions, Defaults, IfNever<SpecifiedOptions, Defaults, Simplify<Merge<Defaults, { [Key in keyof SpecifiedOptions as Key extends OptionalKeysOf ? Extract<SpecifiedOptions[Key], undefined> extends never ? Key : never : Key]: SpecifiedOptions[Key]; }> & Required> // & Required<Options> ensures that ApplyDefaultOptions<SomeOption, ...> is always assignable to Required<SomeOption>

; /** Filter out keys from an object.

Returns never if Exclude is strictly equal to Key. Returns never if Key extends Exclude. Returns Key otherwise.

@example

type Filtered = Filter<'foo', 'foo'>;
//=> never

@example

type Filtered = Filter<'bar', string>;
//=> never

@example

type Filtered = Filter<'bar', 'foo'>;
//=> 'bar'

@see {Except} */ type Filter<KeyType, ExcludeType> = IsEqual<KeyType, ExcludeType> extends true ? never : (KeyType extends ExcludeType ? never : KeyType); type ExceptOptions = { /** Disallow assigning non-specified properties.

Note that any omitted properties in the resulting type will be present in autocomplete as `undefined`.

@default false
*/
requireExactProps?: boolean;

}; type DefaultExceptOptions = { requireExactProps: false; }; /** Create a type from an object type without certain keys.

We recommend setting the requireExactProps option to true.

This type is a stricter version of Omit. The Omit type does not restrict the omitted keys to be keys present on the given type, while Except does. The benefits of a stricter type are avoiding typos and allowing the compiler to pick up on rename refactors automatically.

This type was proposed to the TypeScript team, which declined it, saying they prefer that libraries implement stricter versions of the built-in types (microsoft/TypeScript#30825).

@example

import type {Except} from 'type-fest';

type Foo = {
	a: number;
	b: string;
};

type FooWithoutA = Except<Foo, 'a'>;
//=> {b: string}

const fooWithoutA: FooWithoutA = {a: 1, b: '2'};
//=> errors: 'a' does not exist in type '{ b: string; }'

type FooWithoutB = Except<Foo, 'b', {requireExactProps: true}>;
//=> {a: number} & Partial<Record<"b", never>>

const fooWithoutB: FooWithoutB = {a: 1, b: '2'};
//=> errors at 'b': Type 'string' is not assignable to type 'undefined'.

// The `Omit` utility type doesn't work when omitting specific keys from objects containing index signatures.

// Consider the following example:

type UserData = {
	[metadata: string]: string;
	email: string;
	name: string;
	role: 'admin' | 'user';
};

// `Omit` clearly doesn't behave as expected in this case:
type PostPayload = Omit<UserData, 'email'>;
//=> type PostPayload = { [x: string]: string; [x: number]: string; }

// In situations like this, `Except` works better.
// It simply removes the `email` key while preserving all the other keys.
type PostPayload = Except<UserData, 'email'>;
//=> type PostPayload = { [x: string]: string; name: string; role: 'admin' | 'user'; }

@category Object */ type Except<ObjectType, KeysType extends keyof ObjectType, Options extends ExceptOptions = {}> = _Except<ObjectType, KeysType, ApplyDefaultOptions<ExceptOptions, DefaultExceptOptions, Options>>; type _Except<ObjectType, KeysType extends keyof ObjectType, Options extends Required> = { [KeyType in keyof ObjectType as Filter<KeyType, KeysType>]: ObjectType[KeyType]; } & (Options["requireExactProps"] extends true ? Partial<Record<KeysType, never>> : {}); /** Create a type that makes the given keys optional. The remaining keys are kept as is. The sister of the SetRequired type.

Use-case: You want to define a single model where the only thing that changes is whether or not some of the keys are optional.

@example

import type {SetOptional} from 'type-fest';

type Foo = {
	a: number;
	b?: string;
	c: boolean;
}

type SomeOptional = SetOptional<Foo, 'b' | 'c'>;
// type SomeOptional = {
// 	a: number;
// 	b?: string; // Was already optional and still is.
// 	c?: boolean; // Is now optional.
// }

@category Object */ type SetOptional<BaseType, Keys extends keyof BaseType> = BaseType extends unknown // To distribute BaseType when it's a union type. ? Simplify< // Pick just the keys that are readonly from the base type. Except<BaseType, Keys> & // Pick the keys that should be mutable from the base type and make them mutable. Partial<HomomorphicPick<BaseType, Keys>>> : never; /**

• This file has utilities to create GraphQL clients
• that consume the types generated by the preset. */ /**
• A generic type for variables in GraphQL clients */ type GenericVariables = ExecutionArgs["variableValues"]; /**
• Use this type to make parameters optional in GraphQL clients
• when no variables need to be passed. */ type EmptyVariables = { [key: string]: never; }; /**
• GraphQL client's generic operation interface. */ interface CodegenOperations { [key: string]: any; } /**
• Used as the return type for GraphQL clients. It picks
• the return type from the generated operation types.
• @example
• graphqlQuery: (...) => Promise<ClientReturn<...>>
• graphqlQuery: (...) => Promise<{data: ClientReturn<...>}> */ type ClientReturn<GeneratedOperations extends CodegenOperations, RawGqlString extends string, OverrideReturnType extends any = never> = IsNever extends true ? RawGqlString extends keyof GeneratedOperations ? GeneratedOperations[RawGqlString]["return"] : any : OverrideReturnType; /**
• Checks if the generated variables for an operation
• are optional or required. */ type IsOptionalVariables<VariablesParam, OptionalVariableNames extends string = never, VariablesWithoutOptionals = Omit<VariablesParam, OptionalVariableNames>> = VariablesWithoutOptionals extends EmptyVariables ? true : GenericVariables extends VariablesParam ? true : Partial extends VariablesWithoutOptionals ? true : false; /**
• Used as the type for the GraphQL client's variables. It checks
• the generated operation types to see if variables are optional.
• @example
• graphqlQuery: (query: string, param: ClientVariables<...>) => Promise<...>
• Where param is required. */ type ClientVariables<GeneratedOperations extends CodegenOperations, RawGqlString extends string, OptionalVariableNames extends string = never, VariablesKey extends string = "variables", GeneratedVariables = RawGqlString extends keyof GeneratedOperations ? SetOptional<GeneratedOperations[RawGqlString]["variables"], Extract<keyof GeneratedOperations[RawGqlString]["variables"], OptionalVariableNames>> : GenericVariables, VariablesWrapper = Record<VariablesKey, GeneratedVariables>> = IsOptionalVariables<GeneratedVariables, OptionalVariableNames> extends true ? Partial : VariablesWrapper; /**
• Similar to ClientVariables, but makes the whole wrapper optional:
• @example
• graphqlQuery: (query: string, ...params: ClientVariablesInRestParams<...>) => Promise<...>
• Where the first item in params might be optional depending on the query. */ type ClientVariablesInRestParams<GeneratedOperations extends CodegenOperations, RawGqlString extends string, OtherParams extends Record<string, any> = {}, OptionalVariableNames extends string = never, ProcessedVariables = OtherParams & ClientVariables<GeneratedOperations, RawGqlString, OptionalVariableNames>> = Partial extends OtherParams ? IsOptionalVariables<GeneratedOperations[RawGqlString]["variables"], OptionalVariableNames> extends true ? [ ProcessedVariables? ] : [ ProcessedVariables ] : [ ProcessedVariables ];

declare class GraphQLError extends Error { /** _ If an error can be associated to a particular point in the requested _ GraphQL document, it should contain a list of locations. */ locations?: Array<{ line: number; column: number; }>; /** _ If an error can be associated to a particular field in the GraphQL result, _ it must contain an entry with the key path that details the path of _ the response field which experienced the error. This allows clients to _ identify whether a null result is intentional or caused by a runtime error. _/ path?: Array<string | number>; /** _ Reserved for implementors to extend the protocol however they see fit, _ and hence there are no additional restrictions on its contents. _/ extensions?: { [key: string]: unknown; }; constructor(message?: string, options?: Pick<GraphQLError, 'locations' | 'path' | 'extensions' | 'stack' | 'cause'> & { query?: string; queryVariables?: GenericVariables; requestId?: string | null; clientOperation?: string; }); get Symbol.toStringTag: string; /** _ Note: toString() is internally used by console.log(...) / console.error(...) _ when ingesting logs in Oxygen production. Therefore, we want to make sure that _ the error message is as informative as possible instead of [object Object]. _/ toString(): string; /** _ Note: toJSONis internally used byJSON.stringify(...). _ The most common scenario when this error instance is going to be stringified is _ when it's passed to Remix' jsonanddeferfunctions: e.g.{promise: storefront.query(...)}`. _ In this situation, we don't want to expose private error information to the browser so we only _ do it in development. _/ toJSON(): Pick<GraphQLError, "message" | "locations" | "path" | "extensions" | "stack" | "name">; }

type CrossRuntimeRequest = { url?: string; method?: string; headers: { get?: (key: string) => string | null | undefined; [key: string]: any; }; };

type DataFunctionValue = Response | NonNullable | null; type JsonGraphQLError$1 = ReturnType<GraphQLError['toJSON']>; type Buyer = Partial; type CustomerAPIResponse = { data: ReturnType; errors: Array<{ message: string; locations?: Array<{ line: number; column: number; }>; path?: Array; extensions: { code: string; }; }>; extensions: { cost: { requestQueryCost: number; actualQueryCakes: number; throttleStatus: { maximumAvailable: number; currentAvailable: number; restoreRate: number; }; }; }; }; interface CustomerAccountQueries { } interface CustomerAccountMutations { } type LoginOptions = { uiLocales?: LanguageCode; locale?: string; countryCode?: CountryCode; acrValues?: string; loginHint?: string; loginHintMode?: string; }; type LogoutOptions = { /** The url to redirect customer to after logout, should be a relative URL. This url will need to included in Customer Account API's application setup for logout URI. The default value is current app origin, which is automatically setup in admin when using --customer-account-push flag with dev. */ postLogoutRedirectUri?: string; /** Add custom headers to the logout redirect. _/ headers?: HeadersInit; /** If true, custom data in the session will not be cleared on logout. _/ keepSession?: boolean; }; type CustomerAccount = { /** The i18n configuration for Customer Account API */ i18n: { language: LanguageCode; }; /** Start the OAuth login flow. This function should be called and returned from a Remix loader. _ It redirects the customer to a Shopify login domain. It also defined the final path the customer _ lands on at the end of the oAuth flow with the value of the return_to query param. (This is _ automatically setup unless customAuthStatusHandler option is in use) _ _ @param options.uiLocales - The displayed language of the login page. Only support for the following languages: _ en, fr, cs, da, de, es, fi, it, ja, ko, nb, nl, pl, pt-BR, pt-PT, _ sv, th, tr, vi, zh-CN, zh-TW. If supplied any other language code, it will default to en. _ _/ login: (options?: LoginOptions) => Promise; /** On successful login, the customer redirects back to your app. This function validates the OAuth response and exchanges the authorization code for an access token and refresh token. It also persists the tokens on your session. This function should be called and returned from the Remix loader configured as the redirect URI within the Customer Account API settings in admin. _/ authorize: () => Promise; /** Returns if the customer is logged in. It also checks if the access token is expired and refreshes it if needed. */ isLoggedIn: () => Promise; /** Check for a not logged in customer and redirect customer to login page. The redirect can be overwritten with customAuthStatusHandler option. _/ handleAuthStatus: () => Promise; /** Returns CustomerAccessToken if the customer is logged in. It also run a expiry check and does a token refresh if needed. _/ getAccessToken: () => Promise<string | undefined>; /** Creates the fully-qualified URL to your store's GraphQL endpoint.*/ getApiUrl: () => string; /** Logout the customer by clearing the session and redirecting to the login domain. It should be called and returned from a Remix action. The path app should redirect to after logout ca

…(truncated)