commerce-sdk-isomorphic 4.0.1-preview-shopper-test.0 → 4.1.0

package/lib/helpers.d.ts

@@ -81,6 +81,7 @@ type BrowserRequestInit = RequestInit;
  * Using the right properties in the right context is left to the user.
  */
 type FetchOptions = NodeRequestInit & BrowserRequestInit;
+type FetchFunction = (input: RequestInfo, init?: FetchOptions | undefined) => Promise<Response>;
 /**
  * Base options that can be passed to the `ClientConfig` class.
  */
@@ -92,12 +93,12 @@ interface ClientConfigInit<Params extends BaseUriParameters> {
     };
     parameters: Params;
     fetchOptions?: FetchOptions;
+    fetch?: FetchFunction;
     transformRequest?: (data: unknown, headers: {
         [key: string]: string;
     }) => Required<FetchOptions>["body"];
     throwOnBadResponse?: boolean;
 }
-type FetchFunction = (input: RequestInfo, init?: FetchOptions | undefined) => Promise<Response>;
 /**
  * Configuration parameters common to Commerce SDK clients
  */
@@ -109,23 +110,22 @@ declare class ClientConfig<Params extends BaseUriParameters> implements ClientCo
     };
     parameters: Params;
     fetchOptions: FetchOptions;
+    fetch?: FetchFunction;
     transformRequest: NonNullable<ClientConfigInit<Params>["transformRequest"]>;
     throwOnBadResponse: boolean;
     constructor(config: ClientConfigInit<Params>);
     static readonly defaults: Pick<Required<ClientConfigInit<never>>, "transformRequest">;
 }
-/*
-* Copyright (c) 2022, Salesforce, Inc.
-* All rights reserved.
-* SPDX-License-Identifier: BSD-3-Clause
-* For full license text, see the LICENSE file in the repo root or https://opensource.org/licenses/BSD-3-Clause
-*/
 declare const isBrowser: boolean;
 declare const isNode: boolean;
 declare const globalObject: typeof globalThis;
 declare const hasFetchAvailable: boolean;
-// TODO: Remove this function in the next major version
-// eslint-disable-next-line @typescript-eslint/no-unsafe-assignment
+// TODO: Adopt native fetch in the next major version.
+// Using the built-in fetch (Node 18+) caused downstream unit tests that rely on
+// `nock` to fail because `nock` hooks into the core HTTP/HTTPS modules, while
+// the native fetch implementation leverages undici instead. Until we can roll
+// out a coordinated breaking change, we continue to use the node-fetch
+// polyfill so existing tests keep passing.
 declare const fetch: FetchFunction;
 /**
  * Grant Type