export declare const SHOP_ORIGIN_COOKIE_NAME = "shoptable_shop_origin";
export declare const SHOPIFY_APP_API_KEY_COOKIE_NAME = "shoptable_api_key";
export declare const JWT_COOKIE_NAME = "shoptable_jwt";
export declare const baseCookieConfig: {
    readonly secure: true;
    /**
       * We can do strict since we're not doing an embedded app at the moment.
       */
    readonly sameSite: "strict";
    readonly path: "/";
    readonly domain: "shoptable.app";
};
export declare const JSAccessibleCookieConfig: {
    /**
       * False so that the React app can access them.
       *
       * A cookie with the HttpOnly attribute is inaccessible to the JavaScript Document.cookie API;
       * it is sent only to the server. For example, cookies that persist server-side sessions don't
       * need to be available to JavaScript, and should have the HttpOnly attribute.
       * This precaution helps mitigate cross-site scripting (XSS) attacks.
       *
       * Source: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies
       */
    readonly httpOnly: false;
    readonly secure: true;
    /**
       * We can do strict since we're not doing an embedded app at the moment.
       */
    readonly sameSite: "strict";
    readonly path: "/";
    readonly domain: "shoptable.app";
};
export declare const AuthCookieConfig: {
    /**
       * The JWT needs to be stored inside an httpOnly cookie, a special kind of cookie that’s only sent in HTTP requests to the server,
       * and it’s never accessible (both for reading or writing) from JavaScript running in the browser.
       */
    readonly httpOnly: true;
    readonly secure: true;
    /**
       * We can do strict since we're not doing an embedded app at the moment.
       */
    readonly sameSite: "strict";
    readonly path: "/";
    readonly domain: "shoptable.app";
};
