commerce-sdk-isomorphic 4.0.1-preview-shopper-configurations.0 → 4.0.1

package/README.md

@@ -51,31 +51,19 @@ In the next major version release, the SDK will encode special characters (UTF-8
 
 ### Requirements
 
-- Node `^20.x` or `^22.x`
+- Node `^12.x`, `^14.x`, `^16.x`, `^18.x`
 - The SDK requires B2C Commerce API (SCAPI) to be configured. For more info see [Getting started with SCAPI](https://developer.salesforce.com/docs/commerce/commerce-api/guide/get-started.html).
 
 ### Installation
 
 ```bash
-# This package uses yarn, if you don't have yarn:
-# npm install -g yarn
-yarn install commerce-sdk-isomorphic
+npm install commerce-sdk-isomorphic
 ```
 
 ### Usage
 
 ```javascript
-import ocapi from 'commerce-sdk-isomorphic';
-const { helpers, ShopperLogin, ShopperSearch } = ocapi;
-
-// Named imports also work
-// import {helpers, ShopperLogin, ShopperSearch} from 'commerce-sdk-isomorphic';
-
-// Alternatively, you can use subpath imports to import a single API at a time instead of the entire SDK
-// Useful for when you want a slimmer bundle size and only need a single API
-// import * as helpers from 'commerce-sdk-isomorphic/helpers'
-// import { ShopperProducts } from 'commerce-sdk-isomorphic/shopperProducts';
-// import { ShopperSearch } from 'commerce-sdk-isomorphic/shopperSearch';
+import {helpers, ShopperLogin, ShopperSearch} from 'commerce-sdk-isomorphic';
 
 const config = {
   // SCAPI does not support CORS, so client side requests must use a reverse proxy.
@@ -103,52 +91,6 @@ const searchResult = await shopperSearch.productSearch({
 });
 ```
 
-#### Import Strategies
-
-The SDK supports multiple import patterns to accommodate different use cases:
-
-**Default Import (Full SDK)**
-```javascript
-import ocapi from 'commerce-sdk-isomorphic';
-const { helpers, ShopperLogin, ShopperSearch } = ocapi;
-```
-
-**Named Imports (Full SDK)**
-```javascript
-import { helpers, ShopperLogin, ShopperSearch } from 'commerce-sdk-isomorphic';
-```
-
-**Subpath Imports (Individual APIs and Common dependencies)**
-
-*ESM (ES Modules):*
-```javascript
-import { ShopperLogin } from 'commerce-sdk-isomorphic/shopperLogin';
-import * as helpers from 'commerce-sdk-isomorphic/helpers';
-```
-
-*CommonJS:*
-```javascript
-const { ShopperLogin } = require('commerce-sdk-isomorphic/shopperLogin');
-const helpers = require('commerce-sdk-isomorphic/helpers');
-```
-
-#### Choosing the Right Import Strategy
-
-**Use Default/Named Imports when:**
-- You need multiple APIs from the SDK
-- You want the smallest overall bundle size for comprehensive usage
-- The entire SDK is optimized and maximally compressed as a single bundle
-
-**Note:** Default and named imports load the entire SDK, including all APIs, helpers, and dependencies.
-
-**Use Subpath Imports when:**
-- You only need specific APIs
-- You want to minimize initial bundle size
-- You're implementing dynamic loading for better page performance
-- You need granular control over which APIs are loaded
-
-**Note:** While subpath imports reduce initial bundle size, using them for all APIs will result in a larger total bundle size due to duplicated dependencies required for standalone operation.
-
 #### Fetch Options
 
 You can configure how the SDK makes requests using the `fetchOptions` parameter. It is passed to [node-fetch](https://github.com/node-fetch/node-fetch/1#api) on the server and [whatwg-fetch](https://github.github.io/fetch/) on browser.