@salesforce/commerce-sdk-react 3.1.0 → 3.1.1-preview.0

package/CHANGELOG.md

@@ -1,29 +1,10 @@
-## v3.1.0 (Oct 28, 2024)
-
--   [Server Affinity] Attach dwsid to SCAPI request headers [#2090](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2090)
--   Add the `authorizeCustomer` and `getPasswordResetToken` to the `ShopperLoginMutations` [#2056](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2056)
--   Add useDNT hook to commerce-sdk-react and put DNT in auth [#2067](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2067/files)
--   Add Trusted Agent on Behalf of (TAOB) support for SLAS APIs [#2077](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2077)
--   Add optional `refreshTokenRegisteredCookieTTL` and `refreshTokenGuestCookieTTL` to Commerce API config [#2077](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2077)
--   Improve refresh token error logging [#2028](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2028)
--   Remove ocapi session-bridging on phased launches [#2011](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2011)
--   Add `defaultDnt` to support setting the dnt flag for SLAS. Upgrade `commerce-sdk-isomorphic` to v3.1.1 [#1979](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1979)
--   Update logout helper to work for guest users [#1997](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1997)
--   Update `useCustomMutation` hook to accept request body as a parameter to the mutate function [#2030](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2030)
--   Simplify `useCustomMutation` hook implementation [#2034](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2034)
--   Documentation for `useCustomMutation` hook along with new dynamic `body` param option [#2042](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/2042)
-
-## v3.0.1 (Sep 04, 2024)
-
--   Fixed an issue where the `expires` attribute in cookies, ensuring it uses seconds instead of days. [#1994](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1994)
+## v3.1.1-preview.0 (Dec 02, 2024)
 
 ## v3.0.0 (Aug 07, 2024)
-
--   Add `meta.displayName` to queries. It can be used to identify queries in performance metrics or logs. [#1895](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1895)
--   Upgrade to commerce-sdk-isomorphic v3.0.0 [#1914](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1914)
+- Add `meta.displayName` to queries. It can be used to identify queries in performance metrics or logs. [#1895](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1895)
+- Upgrade to commerce-sdk-isomorphic v3.0.0 [#1914](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1914)
 
 ### :warning: Planned API Changes :warning:
-
 #### Shopper Context
 
 Starting July 31st 2024, all endpoints in the Shopper context API will require the `siteId` parameter for new customers. This field is marked as optional for backward compatibility and will be changed to mandatory tentatively by January 2025. You can read more about the planned change [here](https://developer.salesforce.com/docs/commerce/commerce-api/references/shopper-context?meta=Summary) in the notes section.
@@ -32,79 +13,73 @@ Starting July 31st 2024, all endpoints in the Shopper context API will require t
 
 SLAS will soon require new tenants to pass `channel_id` as an argument for retrieving guest access tokens. You can read more about the planned change [here](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html#guest-tokens).
 
-Please be aware that existing tenants are on a temporary allow list and will see no immediate disruption to service. We do ask that all users seek to adhere to the `channel_id` requirement before the end of August to enhance your security posture before the holiday peak season.
+Please be aware that existing tenants are on a temporary allow list and will see no immediate disruption to service.  We do ask that all users seek to adhere to the `channel_id` requirement before the end of August to enhance your security posture before the holiday peak season.
 
 In practice, we recommend:
-
--   For customers using the SLAS helpers with a private client, it is recommended to upgrade to `v3.0.0` of the `commerce-sdk-react`.
+- For customers using the SLAS helpers with a private client, it is recommended to upgrade to `v3.0.0` of the `commerce-sdk-react`.
 
 ## v2.0.2 (Jul 12, 2024)
-
--   Updated StorefrontPreview component to make siteId available [#1874](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1874)
+- Updated StorefrontPreview component to make siteId available [#1874](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1874)
 
 ## v2.0.1 (Jul 08, 2024)
-
--   Fix private slas proxy config for commerce api in provider [#1883](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1883)
--   Fix `useCustomQuery` error handling [#1883](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1883)
--   Fix `updateCustomer` squashing existing data [#1883](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1883)
--   Fix `transferBasket` updating the wrong customer basket [#1887](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1887)
+- Fix private slas proxy config for commerce api in provider [#1883](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1883)
+- Fix `useCustomQuery` error handling [#1883](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1883)
+- Fix `updateCustomer` squashing existing data [#1883](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1883)
+- Fix `transferBasket` updating the wrong customer basket [#1887](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1887)
 
 ## v2.0.0 (Jun 25, 2024)
-
--   Add `useCustomQuery` and `useCustomMutation` for SCAPI custom endpoint support [#1793](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1793)
--   Add Shopper Stores hooks [#1788](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1788)
--   Add a helper method to add an item to either new or existing basket [#1677](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1677)
--   Add `updateItemsInBasket` mutation [#1852](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1852)
--   Upgrade to commerce-sdk-isomorphic v2.1.0 [#1852](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1852)
+- Add `useCustomQuery` and `useCustomMutation` for SCAPI custom endpoint support [#1793](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1793)
+- Add Shopper Stores hooks [#1788](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1788)
+- Add a helper method to add an item to either new or existing basket [#1677](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1677)
+- Add `updateItemsInBasket` mutation [#1852](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1852)
+- Upgrade to commerce-sdk-isomorphic v2.1.0 [#1852](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1852)
 
 ## v1.4.2 (Apr 17, 2024)
-
--   Update SLAS private proxy path [#1752](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1752)
+- Update SLAS private proxy path [#1752](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1752)
 
 ## v1.4.1 (Apr 16, 2024)
-
--   Add missing params keys `allVariationProperties` and `perPricebook` for Shopper Search [#1750](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1750)
+- Add missing params keys `allVariationProperties` and `perPricebook`  for Shopper Search [#1750](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1750)
 
 ## v1.4.0 (Apr 15, 2024)
 
--   Add Support for SLAS private flow [#1722](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1722)
--   Fix invalid query params warnings and allow custom query [#1655](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1655)
--   Fix cannot read properties of undefined (reading 'unshift') [#1689](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1689)
--   Add Shopper SEO hook [#1688](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1688)
--   Update useLocalStorage implementation to be more responsive [#1703](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1703)
--   Storefront Preview: avoid stale cached Commerce API responses, whenever the Shopper Context is set [#1701](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1701)
+- Add Support for SLAS private flow [#1722](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1722)
+- Fix invalid query params warnings and allow custom query [#1655](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1655)
+- Fix cannot read properties of undefined (reading 'unshift') [#1689](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1689)
+- Add Shopper SEO hook [#1688](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1688)
+- Update useLocalStorage implementation to be more responsive [#1703](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1703)
+- Storefront Preview: avoid stale cached Commerce API responses, whenever the Shopper Context is set [#1701](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1701)
 
 ## v1.3.0 (Jan 19, 2024)
 
--   Add support for node 20 [#1612](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1612)
+- Add support for node 20 [#1612](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1612)
 
 ## v1.2.0 (Dec 08, 2023)
 
--   Add StorefrontPreview component 'onContextChange' property to prepare for future Storefront Preview release [#1527](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1527)
--   Update engine compatibility to include npm 10 [#1597](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1597)
+- Add StorefrontPreview component 'onContextChange' property to prepare for future Storefront Preview release [#1527](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1527)
+- Update engine compatibility to include npm 10 [#1597](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1597)
 
 ## v1.1.0 (Nov 03, 2023)
 
--   Add StorefrontPreview component [#1508](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1508)
--   Using `login` for authentication instead of `email` in registration process [#1464](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1464)
--   Fix bug to remove cookies using the default attributes used when setting cookie [#1505](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1505)
+- Add StorefrontPreview component [#1508](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1508)
+- Using `login` for authentication instead of `email` in registration process [#1464](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1464)
+- Fix bug to remove cookies using the default attributes used when setting cookie [#1505](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1505)
 
 ## v1.0.2 (Sep 21, 2023)
 
--   commerce-sdk-react: have typedoc-related deps as dev dependencies [#1425](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1425)
--   Updated commerce-sdk-isomorphic to v1.10.4 [#137](https://github.com/SalesforceCommerceCloud/commerce-sdk-isomorphic/pull/137)
+- commerce-sdk-react: have typedoc-related deps as dev dependencies [#1425](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1425)
+- Updated commerce-sdk-isomorphic to v1.10.4 [#137](https://github.com/SalesforceCommerceCloud/commerce-sdk-isomorphic/pull/137)
 
 ## v1.0.1 (Jul 26, 2023)
 
--   Updated the expiry of the guest refresh token cookie to 30 days, to match the actual [duration of the token](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html?q=refresh+token#access-tokens-and-refresh-tokens). [#1342](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1342)
--   Fix potential security vulnerability in `semver` dependency [#1358](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1358)
--   Fix request headers to be the intended headers, rather than parameters [#1377](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1377)
+- Updated the expiry of the guest refresh token cookie to 30 days, to match the actual [duration of the token](https://developer.salesforce.com/docs/commerce/commerce-api/guide/slas.html?q=refresh+token#access-tokens-and-refresh-tokens). [#1342](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1342)
+- Fix potential security vulnerability in `semver` dependency [#1358](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1358)
+- Fix request headers to be the intended headers, rather than parameters [#1377](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1377)
 
 ## v1.0.0 (Jun 15, 2023)
 
--   First public release of package on npm under `@salesforce/commerce-sdk-react`
--   Add missing cache invalidation for contexts/customers/login/order [#1073](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1073)
--   Upgrade React 18, React DOM 18, @types/react@18, @types/react-dom@v18 Testing library 14 [#1166](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1166)
+- First public release of package on npm under `@salesforce/commerce-sdk-react`
+- Add missing cache invalidation for contexts/customers/login/order [#1073](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1073)
+- Upgrade React 18, React DOM 18, @types/react@18, @types/react-dom@v18 Testing library 14 [#1166](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1166)
 
 ## Older Versions Without Namespace
 
@@ -112,28 +87,28 @@ The older versions below were published without the `@salesforce` namespace.
 
 ## v2.7.1 (May 11, 2023)
 
--   Re-generate lock files and fix hook lib tests [#1186](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1186)
--   Add additional properties to ShopperLogin test types [#1185](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1185)
--   Add missing cache invalidation for contexts/customers/login/order [#1073](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1073)
--   Fix Shopper Baskets Test case [#1082](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1082)
--   Implement remaining Shopper Baskets cache logic [#1070](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1070)
--   Decode pre-fetched token and save auth data in storage [#1052](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1052)
--   Allow query hook parameters to be null. [#1046](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1046)
--   Implement updateCustomerPassword as no-op. [#1031](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1031)
+- Re-generate lock files and fix hook lib tests [#1186](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1186)
+- Add additional properties to ShopperLogin test types [#1185](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1185)
+- Add missing cache invalidation for contexts/customers/login/order [#1073](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1073)
+- Fix Shopper Baskets Test case [#1082](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1082)
+- Implement remaining Shopper Baskets cache logic [#1070](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1070)
+- Decode pre-fetched token and save auth data in storage [#1052](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1052)
+- Allow query hook parameters to be null. [#1046](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1046)
+- Implement updateCustomerPassword as no-op. [#1031](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/1031)
 
 ## v2.7.0 (Mar 03, 2023)
 
--   Add Page/Region/Component components for shopper experience/page designer page rendering [#963](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/963)
--   Namespace `Auth` storage keys with site identifier to allow multi-site support [#911](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/911)
--   Add Shopper Experience `usePage` and `usePages` hooks[#958](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/958)
+- Add Page/Region/Component components for shopper experience/page designer page rendering [#963](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/963)
+- Namespace `Auth` storage keys with site identifier to allow multi-site support [#911](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/911)
+- Add Shopper Experience `usePage` and `usePages` hooks[#958](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/958)
 
 ## v2.6.0 (Jan 25, 2023)
 
 ## v2.5.0 (Jan 05, 2023)
 
--   Exclude test files in package file to avoid publishing them [#856](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/856)
--   Pass in 'headers' and 'rawResponse' options to mutation hooks [#845](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/845)
--   Commerce hooks: basket mutations [#834](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/834)
--   Remove overriding of params in mutation hooks [#859](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/859)
+- Exclude test files in package file to avoid publishing them [#856](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/856)
+- Pass in 'headers' and 'rawResponse' options to mutation hooks [#845](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/845)
+- Commerce hooks: basket mutations [#834](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/834)
+- Remove overriding of params in mutation hooks [#859](https://github.com/SalesforceCommerceCloud/pwa-kit/pull/859)
 
 ## v2.4.0 (Dec 01, 2022)

package/README.md

@@ -321,135 +321,7 @@ const Example = ({basketId}) => {
 }
 ```
 
-##### `useCustomMutation`
-
-The `useCustomMutation` hook facilitates communication with the SCAPI custom endpoint. It has a different signature than the other declared mutation hooks.
-
-###### Parameters
-
-- `options` (Object): Configuration for the API request.
-  - `method` (String): The HTTP method to use (e.g., 'POST', 'GET').
-  - `customApiPathParameters` (Object): Contains parameters to define the API path.
-    - `endpointPath` (String): Specific endpoint path to target in the API.
-    - `apiName` (String): The name of the API.
-
-- `clientConfig` (Object): Configuration settings for the client.
-  - `parameters` (Object): Essential parameters required by the Salesforce Commerce Cloud API.
-    - `clientId` (String): Your client ID.
-    - `siteId` (String): Your site ID.
-    - `organizationId` (String): Your organization ID.
-    - `shortCode` (String): Short code for your organization.
-  - `proxy` (String): Proxy address for API calls.
-
-- `rawResponse` (Boolean): Determines whether to receive the raw response from the API or a parsed version.
-
-###### `mutate` Method
-
-The `mutation.mutate(args)` function is used to execute the mutation. It accepts an argument `args`, which is an object that may contain the following properties:
-
-- `headers` (Object): Optional headers to send with the request.
-- `parameters` (Object): Optional query parameters to append to the API URL.
-- `body` (Object): Optional the payload for POST, PUT, PATCH methods.
-
-##### Usage
-
-Below is a sample usage of the `useCustomMutation` hook within a React component.
-
-
-
-```jsx
-const clientConfig = {
-    parameters: {
-        clientId: 'CLIENT_ID',
-        siteId: 'SITE_ID',
-        organizationId: 'ORG_ID',
-        shortCode: 'SHORT_CODE'
-    },
-    proxy: 'http://localhost:8888/mobify/proxy/api'
-};
-
-const mutation = useCustomMutation({
-    options: {
-        method: 'POST',
-        customApiPathParameters: {
-            endpointPath: 'test-hello-world',
-            apiName: 'hello-world'
-        }
-    },
-    clientConfig,
-    rawResponse: false
-});
-
-// In your React component
-<button onClick={() => mutation.mutate({
-    body: { test: '123' },
-    parameters: { additional: 'value' },
-    headers: { ['X-Custom-Header']: 'test' }
-})}>
-    Send Request
-</button>
-```
-
-It is a common scenario that a mutate function might pass a value along to a request that is dynamic and therefore can't be available when the hook is declared (contrary to example in [Mutation Hooks](#mutation-hooks) above, which would work for a button that only adds one product to a basket, but doesn't handle a changeable input for adding a different product).
-
-Sending a custom body param is supported, the example below combines this strategy with the use of a `useCustomMutation()` hook, making it possible to dynamically declare a body when calling a custom API endpoint.
-
-```jsx
-import {useCustomMutation} from '@salesforce/commerce-sdk-react'
-const clientConfig = {
-    parameters: {
-        clientId: 'CLIENT_ID',
-        siteId: 'SITE_ID',
-        organizationId: 'ORG_ID',
-        shortCode: 'SHORT_CODE'
-    },
-    proxy: 'http://localhost:8888/mobify/proxy/api'
-};
-
-const mutation = useCustomMutation({
-    options: {
-        method: 'POST',
-        customApiPathParameters: {
-            endpointPath: 'path/to/resource',
-            apiName: 'hello-world'
-        }
-    },
-    clientConfig,
-    rawResponse: false
-});
-
-// use it in a react component
-const ExampleDynamicMutation = () => {
-    const [colors, setColors] = useState(['blue', 'green', 'white'])
-    const [selectedColor, setSelectedColor] = useState(colors[0])
-
-    return (
-        <>
-            <select value={selectedColor} onChange={(e) => setSelectedColor(e.target.value)}>
-                {colors.map((color, index) => (
-                    <option key={index} value={color}>
-                        {color}
-                    </option>
-                ))}
-            </select>
-            <button
-                onClick={() =>
-                    mutation.mutate({
-                        parameters: {
-                            myCustomParam: 'custom parameters'
-                        },
-                        body: {
-                            resourceParam: selectedColor
-                        }
-                    })
-                }
-            />
-        </>
-    )
-}
-```
-
-Mutations also have their named methods exported as constants, available in this way:
+You could also import the mutation options as a constant like:
 
 ```jsx
 import {useShopperBasketsMutation, ShopperBasketsMutations} from '@salesforce/commerce-sdk-react'

package/auth/index.d.ts

@@ -1,7 +1,6 @@
 import { helpers, ShopperLoginTypes, ShopperCustomersTypes } from 'commerce-sdk-isomorphic';
 import { ApiClientConfigParams, Prettify, RemoveStringIndex } from '../hooks/types';
 import { CustomerType } from '../hooks/useCustomerType';
-import { DNT_COOKIE_NAME, DWSID_COOKIE_NAME } from '../constant';
 import { Logger } from '../types';
 type TokenResponse = ShopperLoginTypes.TokenResponse;
 type Helpers = typeof helpers;
@@ -10,13 +9,11 @@ interface AuthConfig extends ApiClientConfigParams {
     proxy: string;
     fetchOptions?: ShopperLoginTypes.FetchOptions;
     fetchedToken?: string;
+    OCAPISessionsURL?: string;
     enablePWAKitPrivateClient?: boolean;
     clientSecret?: string;
     silenceWarnings?: boolean;
     logger: Logger;
-    defaultDnt?: boolean;
-    refreshTokenRegisteredCookieTTL?: number;
-    refreshTokenGuestCookieTTL?: number;
 }
 /**
  * The extended field is not from api response, we manually store the auth type,
@@ -29,9 +26,7 @@ export type AuthData = Prettify<RemoveStringIndex<TokenResponse> & {
     idp_access_token: string;
 }>;
 /** A shopper could be guest or registered, so we store the refresh tokens individually. */
-type AuthDataKeys = Exclude<keyof AuthData, 'refresh_token'> | 'refresh_token_guest' | 'refresh_token_registered' | 'access_token_sfra' | typeof DNT_COOKIE_NAME | typeof DWSID_COOKIE_NAME;
-export declare const DEFAULT_SLAS_REFRESH_TOKEN_REGISTERED_TTL: number;
-export declare const DEFAULT_SLAS_REFRESH_TOKEN_GUEST_TTL: number;
+type AuthDataKeys = Exclude<keyof AuthData, 'refresh_token'> | 'refresh_token_guest' | 'refresh_token_registered' | 'access_token_sfra';
 /**
  * This class is used to handle shopper authentication.
  * It is responsible for initializing shopper session, manage access
@@ -47,19 +42,13 @@ declare class Auth {
     private pendingToken;
     private stores;
     private fetchedToken;
+    private OCAPISessionsURL;
     private clientSecret;
     private silenceWarnings;
     private logger;
-    private defaultDnt;
-    private refreshTokenRegisteredCookieTTL;
-    private refreshTokenGuestCookieTTL;
-    private refreshTrustedAgentHandler;
     constructor(config: AuthConfig);
     get(name: AuthDataKeys): string;
     private set;
-    private delete;
-    getDnt(): boolean | undefined;
-    setDnt(preference: boolean | null): Promise<void>;
     private clearStorage;
     /**
      * Every method in this class that returns a `TokenResponse` constructs it via this getter.
@@ -69,11 +58,6 @@ declare class Auth {
      * Used to validate JWT token expiration.
      */
     private isTokenExpired;
-    /**
-     * Gets the Do-Not-Track (DNT) preference from the `dw_dnt` cookie.
-     * If user has set their DNT preference, read the cookie, if not, use the default DNT pref. If the default DNT pref has not been set, default to false.
-     */
-    private getDntPreference;
     /**
      * Returns the SLAS access token or an empty string if the access token
      * is not found in local store or if SFRA wants PWA to trigger refresh token login.
@@ -89,46 +73,12 @@ declare class Auth {
      * @returns {string} access token
      */
     private getAccessToken;
-    /**
-     * For Hybrid storefronts ONLY!!!
-     * This method clears out SLAS access token generated in Plugin SLAS and passed in via "cc-at" cookie.
-     *
-     * In a hybrid setup, whenever any SLAS flow executes in Plugin SLAS and an access token is generated,
-     * the access token is sent over to PWA Kit using cc-at cookie.
-     *
-     * PWA Kit will check to see if cc-at cookie exists, if it does, the access token value in localStorage is updated
-     * with value from the cc-at cookie and is then used for all SCAPI requests made from PWA Kit. The cc-at cookie is then cleared.
-     */
     private clearSFRAAuthToken;
     /**
-     * For Hybrid storefronts ONLY!!!
-     * This method clears the dwsid cookie from the browser.
-     * In a hybrid setup, dwsid points to an ECOM session and is passed between PWA Kit and SFRA/SG sites via "dwsid" cookie.
-     *
-     * Whenever a registered shopper logs in on PWA Kit, we must clear the dwsid cookie if one exists. When shopper navigates
-     * to SFRA as a logged-in shopper, ECOM notices a missing DWSID, generates a new DWSID and triggers the onSession hook which uses
-     * registered shopper refresh-token and restores session and basket on SFRA.
-     */
-    private clearECOMSession;
-    /**
-     * Converts a duration in seconds to a Date object.
-     * This function takes a number representing seconds and returns a Date object
-     * for the current time plus the given duration.
-     *
-     * @param {number} seconds - The number of seconds to add to the current time.
-     * @returns {Date} A Date object for the expiration time.
-     */
-    private convertSecondsToDate;
-    /**
-     * Retrieves our refresh token cookie ttl value
-     */
-    private getRefreshTokenCookieTTLValue;
-    /**
-     * This method stores the TokenResponse object retrieved from SLAS, and
+     * This method stores the TokenResponse object retrived from SLAS, and
      * store the data in storage.
      */
     private handleTokenResponse;
-    refreshAccessToken(): Promise<ShopperLoginTypes.TokenResponse>;
     /**
      * This method queues the requests and handles the SLAS token response.
      *
@@ -138,25 +88,6 @@ declare class Auth {
      */
     queueRequest(fn: () => Promise<TokenResponse>, isGuest: boolean): Promise<ShopperLoginTypes.TokenResponse>;
     logWarning: (msg: string) => void;
-    /**
-     * This method extracts the status and message from a ResponseError that is returned
-     * by commerce-sdk-isomorphic.
-     *
-     * commerce-sdk-isomorphic throws a `ResponseError`, but doesn't export the class.
-     * We can't use `instanceof`, so instead we just check for the `response` property
-     * and assume it is a `ResponseError` if a response is present
-     *
-     * Once commerce-sdk-isomorphic exports `ResponseError` we can revisit if this method is
-     * still required.
-     *
-     * @returns {status_code, responseMessage} contained within the ResponseError
-     * @throws error if the error is not a ResponseError
-     * @Internal
-     */
-    extractResponseError: (error: Error) => Promise<{
-        status_code: string;
-        responseMessage: string;
-    }>;
     /**
      * The ready function returns a promise that resolves with valid ShopperLogin
      * token response.
@@ -166,8 +97,7 @@ declare class Auth {
      * The flow:
      * 1. If we have valid access token - use it
      * 2. If we have valid refresh token - refresh token flow
-     * 3. If we have valid TAOB access token - refresh TAOB token flow
-     * 4. PKCE flow
+     * 3. PKCE flow
      */
     ready(): Promise<ShopperLoginTypes.TokenResponse>;
     /**
@@ -285,54 +215,22 @@ declare class Auth {
      */
     loginRegisteredUserB2C(credentials: Parameters<Helpers['loginRegisteredUserB2C']>[1]): Promise<helpers.TokenResponse>;
     /**
-     * Trusted agent authorization
+     * A wrapper method for commerce-sdk-isomorphic helper: logout.
      *
-     * @warning This method is not supported on the server, it is a client-only method.
      */
-    authorizeTrustedAgent(credentials: {
-        loginId?: string;
-    }): Promise<{
-        url: string;
-        codeVerifier: string;
-    }>;
+    logout(): Promise<ShopperLoginTypes.TokenResponse>;
     /**
-     * Trusted agent login
+     * Make a post request to the OCAPI /session endpoint to bridge the session.
      *
-     * @warning This method is not supported on the server, it is a client-only method.
-     */
-    loginTrustedAgent(credentials: {
-        loginId?: string;
-        code: string;
-        codeVerifier?: string;
-        usid?: string;
-        state?: string;
-        clientSecret?: string;
-    }): Promise<{
-        access_token: string;
-        id_token: string;
-        refresh_token: string;
-        expires_in: number;
-        refresh_token_expires_in: any;
-        token_type: string;
-        usid: string;
-        customer_id: string;
-        enc_user_id: string;
-        idp_access_token: string;
-    } & {
-        [key: string]: any;
-    }>;
-    /**
-     * Trusted agent refresh handler
+     * The HTTP response contains a set-cookie header which sets the dwsid session cookie.
+     * This cookie is used on SFRA, and it allows shoppers to navigate between SFRA and
+     * this PWA site seamlessly; this is often used to enable hybrid deployment.
      *
-     * @warning This method is not supported on the server, it is a client-only method.
-     */
-    registerTrustedAgentRefreshHandler(refreshTrustedAgentHandler: (loginId?: string, usid?: string, refresh?: boolean) => Promise<TokenResponse>): void;
-    refreshTrustedAgent(loginId: string, usid: string): Promise<TokenResponse>;
-    /**
-     * A wrapper method for commerce-sdk-isomorphic helper: logout.
+     * (Note: this method is client side only, b/c MRT doesn't support set-cookie header right now)
      *
+     * @returns {Promise}
      */
-    logout(): Promise<ShopperLoginTypes.TokenResponse>;
+    createOCAPISession(): Promise<Response>;
     /**
      * Decode SLAS JWT and extract information such as customer id, usid, etc.
      *
@@ -341,10 +239,6 @@ declare class Auth {
         isGuest: boolean;
         customerId: string;
         usid: string;
-        dnt: string;
-        loginId: string;
-        isAgent: boolean;
-        agentId: string | null;
     };
 }
 export default Auth;