@liquidcommerce/elements-sdk 2.7.35 → 2.7.37

package/docs/v1/guides/checkout-component.md

@@ -668,3 +668,60 @@ checkout: {
 - [Actions API](../api/actions/checkout-actions.md) - Checkout actions reference
 - [Events](./events.md) - All available events
 - [Theming](./theming.md) - Customize appearance
+
+### Preparing complete account delivery details
+
+After `lce:actions.checkout_loaded`, call
+`await elements.actions.checkout.updateCustomerInfo(fields, { saveIfValid: true })`
+to validate and prepare complete account details, then show their editable summary.
+Supply names, email, a US phone number, and a real `birthDate` in `MM/DD/YYYY` format
+(age 21+, year 1930 or later). A shipping street must already be selected.
+Omitted apartment and delivery instructions retain their existing checkout values.
+Partial or invalid details stay in the form; backend validation failures reject the
+promise, show the checkout error, and keep details editable. The host should handle that rejection.
+
+The option skips gifts, saved forms, in-flight saves, and customer forms the shopper
+has edited during the current checkout. It does not overwrite those forms. Edits or
+address/checkout changes during preparation prevent a stale response from closing
+the form. Without the option, this action only prefills fields, as before.
+
+Apple Pay and Google Pay selection displays **Continue with Apple Pay** or
+**Continue with Google Pay**. This opens the wallet to save a payment method; the
+shopper still reviews and places the order afterward. It is not express checkout.
+
+After wallet cancellation, the same Continue action remains available. If authorization
+succeeded but saving the method failed, **Retry saving Apple Pay/Google Pay** reuses
+the existing authorization rather than opening the wallet again.
+
+### Saved account marketing preferences
+
+```ts
+setSavedMarketingPreferences(preferences: { canEmail?: boolean; canSms?: boolean }): Promise<void>
+clearSavedMarketingPreferences(): void
+```
+
+Call `actions.checkout.setSavedMarketingPreferences()` with known recorded account
+choices, including `false`, before checkout loads. Only boolean values are used;
+missing/null/unrecognized values remain unknown. The first checkout prepare uses
+saved values instead of tenant defaults. Each channel's prompt is hidden only
+after the server confirms that saved choice. Unknown channels retain their normal
+checkout prompts. The actions are available in both full and checkout-only clients.
+
+Calling the setter during an active checkout prepares untouched channels and
+preserves shopper checkbox edits. Backend failure rejects the promise, displays
+an error, and leaves prompts available; the host should catch the rejection.
+The same call can retry. Applying values does not call a subscription service.
+It supplies the account's recorded choices to this checkout.
+
+Saved choices persist across cart resets in the same SDK session. Call
+`clearSavedMarketingPreferences()` on sign-out, account change, and host cleanup.
+Clearing reveals the prompts and restores configured guest defaults. It invalidates
+stale responses while draining outstanding preference requests; checkout completion
+prepares the current choices before submitting the checkout token. A load already
+in progress still finishes and reconciles the current account's values. Bind a new
+account only to its own checkout; the host remains responsible for account/cart
+ownership and for reloading checkout when identity changes.
+
+Order completion waits for queued preference work. It cannot race a late saved
+opt-out or proceed with an unconfirmed saved choice. If applying a known choice
+fails, the shopper can retry or explicitly choose the visible channel preference.

package/docs/v1/guides/events.md

@@ -226,6 +226,36 @@ window.addEventListener('lce:actions.address_failed', (event) => {
 
 ## Cart Events
 
+### `lce:actions.cart_shop_retailer`
+
+A shopper activated **Shop {retailer}** from an unmet cart fulfillment minimum. Opt in with
+`customTheme.cart.layout.showShopRetailerButton: true` (default `false`). The cart command
+revalidates the fulfillment, its current retailer and items, fulfillment type, and remaining
+minimum before emitting. Unsupported, empty, stale or already-satisfied fulfillments emit nothing.
+
+```typescript
+interface ICartShopRetailerEventData {
+  retailerId: string;
+  fulfillmentId: string;
+  fulfillmentType: 'onDemand' | 'shipping';
+}
+```
+
+Listen with the exported constant; the usual event envelope is `{ data, metadata }`:
+
+```javascript
+window.addEventListener(`lce:actions.${ELEMENTS_ACTIONS_EVENT.CART_SHOP_RETAILER}`, (event) => {
+  const { retailerId, fulfillmentId, fulfillmentType } = event.detail.data;
+  // Revalidate against client.actions.cart.getDetails(), then close the drawer
+  // and route to your catalog scoped to this retailer and fulfillment type.
+});
+```
+
+The SDK leaves the drawer open and does not navigate. The host handles routing and derives
+retailer names, totals and minimums from current cart details. The event is also sent to `lce:actions`.
+
+
+
 ### `lce:actions.cart_loaded`
 
 Fires when the cart is fully loaded or synced.

package/docs/v1/guides/theming.md

@@ -138,6 +138,7 @@ customTheme: {
       backgroundColor: '#ffffff'
     },
     layout: {
+        showShopRetailerButton: false, // Enable only with a cart_shop_retailer event handler
       showQuantityCounter: true,
       quantityCounterStyle: 'outlined',
       drawerHeaderText: 'Your Shopping Cart',
@@ -227,3 +228,15 @@ const client = await Elements('YOUR_API_KEY', {
 
 - [Configuration Reference](../api/configuration.md)
 - [Component Guides](../guides/)
+
+### Shop the same retailer
+
+Set `customTheme.cart.layout.showShopRetailerButton: true` to show a native **Shop {retailer}**
+button beside each unmet order-minimum warning (below it on mobile). The default is `false`,
+including when the server theme predates this option. It only appears for a current, nonempty
+`onDemand` or `shipping` fulfillment with a positive amount remaining and valid retailer ownership.
+
+Handle `ELEMENTS_ACTIONS_EVENT.CART_SHOP_RETAILER` (`lce:actions.cart_shop_retailer`) to close the
+cart and open your retailer-filtered catalog. The SDK emits identifiers only and performs no
+navigation. Revalidate them against `client.actions.cart.getDetails()` before navigating; see
+[Events](./events.md) for the payload.

package/package.json

@@ -3,7 +3,7 @@
   "description": "LiquidCommerce Elements SDK",
   "license": "UNLICENSED",
   "author": "LiquidCommerce Team",
-  "version": "2.7.35",
+  "version": "2.7.37",
   "homepage": "https://docs.liquidcommerce.co/elements-sdk",
   "repository": {
     "type": "git",
@@ -109,10 +109,10 @@
     "theming"
   ],
   "devDependencies": {
-    "@biomejs/biome": "^2.5.11",
-    "@commitlint/cli": "^21.2.2",
-    "@commitlint/config-conventional": "^21.2.2",
-    "@playwright/test": "1.60.0",
+    "@biomejs/biome": "^2.5.14",
+    "@commitlint/cli": "^21.2.3",
+    "@commitlint/config-conventional": "^21.2.3",
+    "@playwright/test": "1.63.0",
     "@rollup/plugin-alias": "^6.0.0",
     "@rollup/plugin-commonjs": "^29.0.3",
     "@rollup/plugin-json": "^6.1.0",
@@ -126,18 +126,18 @@
     "@semantic-release/npm": "^13.1.5",
     "@semantic-release/release-notes-generator": "^14.1.1",
     "@types/core-js": "^2.5.8",
-    "@types/node": "^26.4.0",
+    "@types/node": "^26.6.2",
     "conventional-changelog": "8.1.3",
     "husky": "^9.1.7",
-    "jsdom": "26.1.0",
+    "jsdom": "30.1.0",
     "process": "^0.11.10",
-    "rollup": "^4.63.1",
+    "rollup": "^4.63.4",
     "rollup-obfuscator": "^4.1.1",
     "rollup-plugin-typescript2": "^0.37.0",
     "semantic-release": "^25.0.9",
     "ts-node": "^10.9.2",
     "typescript": "6.0.3",
-    "vitest": "2.1.9"
+    "vitest": "5.0.1"
   },
   "engines": {
     "node": ">=22"