/**
 * One-time console diagnostic for an app-proxy request that never reached a
 * response.
 *
 * A `fetch` that REJECTS — rather than resolving with a non-2xx `Response` — means
 * the browser refused or could not complete the request: it failed before a
 * response was received. On a Shopify storefront two independent conditions an
 * integrator controls can each produce it — a `proxyBaseUrl` on a host that
 * redirects elsewhere (a browser cannot follow a redirect on a cross-origin
 * request), and a page origin not permitted by the app's Allowed Domains setting —
 * and the SDK cannot observe which, if either, applies. The message therefore
 * asks for both to be checked and asserts nothing about what was detected.
 *
 * The experience resolver's live read is the only warning site. When a product is
 * not covered by a preloaded value or an override, it is the first proxy request a
 * page makes, ahead of any verify or claim, so one site reports the condition for
 * the whole adapter; the same warning on the verifier and claimer would only
 * repeat it.
 *
 * Only an ABSOLUTE base can reach the condition. A relative base is same-origin by
 * construction — never redirected to another origin, never subject to a
 * cross-origin check — so a rejection there has some other cause and earns no
 * advice.
 */
/**
 * Warn that a request to the configured app-proxy base failed before a response
 * was received. A no-op for a relative base and for a base already warned about.
 */
export declare function warnProxyRequestFailed(configuredBase: string): void;
/** Drop the warned bases so a test starts from a page that has warned about nothing. */
export declare function resetProxyRequestWarningForTests(): void;