@wix/web5-core 1.63.48 → 1.63.49

package/dist/types/privacy/providers/shopifyProvider.d.ts

@@ -1,26 +0,0 @@
-/**
- * Shopify Customer Privacy API provider — DL #218.
- *
- * Two things about this API shape the provider:
- *
- * 1. **It is not on the page by default.** `window.Shopify.customerPrivacy` is
- *    `undefined` until somebody asks for it with `Shopify.loadFeatures`. The
- *    theme app extension warms it so it is ready before the bundle mounts;
- *    this provider still requests it, because the extension may not be
- *    installed and the request is idempotent.
- *
- * 2. **`visitorConsentCollected` may have already fired.** The bundle executes
- *    into an already-rendered storefront page (DL #217), so `read()` answers
- *    from current state and the event is only ever an update.
- *
- * The region rule is the one judgement encoded here, and it keys off
- * `isRegulationEnforced()` rather than `shouldShowBanner()`. The two are not
- * interchangeable: the banner reflects what the *merchant* configured, while
- * enforcement reflects what the *visitor's jurisdiction* requires. A store with
- * an empty consent configuration reports "no banner needed" everywhere,
- * including inside the EU.
- */
-import { type ConsentProvider } from '../types';
-export declare const isShopifyHost: () => boolean;
-export declare const createShopifyConsentProvider: () => ConsentProvider;
-//# sourceMappingURL=shopifyProvider.d.ts.map

package/dist/types/privacy/providers/shopifyProvider.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"shopifyProvider.d.ts","sourceRoot":"","sources":["../../../../src/privacy/providers/shopifyProvider.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAEH,OAAO,EAEL,KAAK,eAAe,EAGrB,MAAM,UAAU,CAAC;AAiDlB,eAAO,MAAM,aAAa,QAAO,OAAgC,CAAC;AAyIlE,eAAO,MAAM,4BAA4B,QAAO,eAwB9C,CAAC"}

package/dist/types/privacy/types.d.ts

@@ -1,32 +0,0 @@
-/**
- * Consent vocabulary shared by the gate and every provider.
- *
- * DL #218. Three states, because "we have not been told" is not the same
- * answer as "no" and must not be collapsed into one: a visitor who has not
- * been asked can still be unlocked by their own action, a visitor who
- * refused never can.
- */
-export type ConsentState = 'granted' | 'denied' | 'unknown';
-/**
- * `necessary` is never gated — auth tokens and the configuration fetch are
- * what make the widget work at all, and a visitor who loaded the page asked
- * for that much. Everything else answers to the gate.
- */
-export type ConsentPurpose = 'necessary' | 'performance' | 'analytics' | 'marketing';
-export type GatedPurpose = Exclude<ConsentPurpose, 'necessary'>;
-export type ConsentSnapshot = Record<GatedPurpose, ConsentState>;
-export declare const UNKNOWN_CONSENT: ConsentSnapshot;
-/**
- * A consent provider adapts one host's CMP to the gate.
- *
- * `read()` must answer synchronously with what is known *now*. Providers are
- * installed into an already-rendered storefront page (DL #217), so a provider
- * that only subscribes is inert — the event it waits for may have fired long
- * before the bundle executed. Always read first, then subscribe.
- */
-export interface ConsentProvider {
-    readonly name: string;
-    read(): ConsentSnapshot;
-    subscribe(onChange: (snapshot: ConsentSnapshot) => void): () => void;
-}
-//# sourceMappingURL=types.d.ts.map

package/dist/types/privacy/types.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../../../src/privacy/types.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,MAAM,MAAM,YAAY,GAAG,SAAS,GAAG,QAAQ,GAAG,SAAS,CAAC;AAE5D;;;;GAIG;AACH,MAAM,MAAM,cAAc,GACtB,WAAW,GACX,aAAa,GACb,WAAW,GACX,WAAW,CAAC;AAEhB,MAAM,MAAM,YAAY,GAAG,OAAO,CAAC,cAAc,EAAE,WAAW,CAAC,CAAC;AAEhE,MAAM,MAAM,eAAe,GAAG,MAAM,CAAC,YAAY,EAAE,YAAY,CAAC,CAAC;AAEjE,eAAO,MAAM,eAAe,EAAE,eAI5B,CAAC;AAEH;;;;;;;GAOG;AACH,MAAM,WAAW,eAAe;IAC9B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,IAAI,IAAI,eAAe,CAAC;IACxB,SAAS,CAAC,QAAQ,EAAE,CAAC,QAAQ,EAAE,eAAe,KAAK,IAAI,GAAG,MAAM,IAAI,CAAC;CACtE"}