@mohasinac/appkit 4.23.0 → 4.25.0

package/dist/features/admin/actions/notification-actions.js

@@ -7,6 +7,30 @@ import { isChannelHealthy, withChannelRetry } from "../../../_internal/server/no
 import { enqueueJob } from "../../jobs/actions/enqueue-job";
 import { serverLogger } from "../../../monitoring";
 import { decryptPii } from "../../../security/index";
+import { resolveNotificationActionUrl, } from "../../../_internal/shared/features/notifications/action-url";
+import { renderNotificationEmail } from "../../email/notification-templates";
+/**
+ * A notification's `actionUrl` is a site-relative path — correct for the
+ * in-app bell, useless in an email, where a bare `/user/orders/x` is not a
+ * link at all.
+ *
+ * `NEXT_PUBLIC_APP_URL` is the same source `ApiClient` uses for its own
+ * server-side base, so there is one answer to "what host is this" rather than
+ * a second one on `siteSettings` to drift from it.
+ *
+ * Falls back to returning the path unchanged rather than guessing a host: a
+ * wrong absolute URL sends the reader to someone else's site, while a
+ * relative one merely fails to be clickable. The template also drops the
+ * button entirely when this is undefined.
+ */
+function absoluteActionUrl(path) {
+    if (!path)
+        return undefined;
+    if (/^https?:\/\//i.test(path))
+        return path;
+    const base = process.env.NEXT_PUBLIC_APP_URL?.replace(/\/+$/, "");
+    return base ? `${base}${path}` : path;
+}
 import { DEFAULT_NOTIFICATION_CHANNELS, meetsMinPriority, } from "../schemas/firestore";
 /**
  * Notification types whose WhatsApp send is gated behind the buyer's
@@ -24,7 +48,27 @@ const ORDER_GATED_TYPES = new Set([
     "order_cancelled",
     "refund_initiated",
 ]);
-/** Notification type → the flat `SiteSettingsCredentials` field holding its approved Meta template name. */
+/**
+ * Notification type → the flat `SiteSettingsCredentials` field holding its
+ * approved Meta template name.
+ *
+ * 🛑 **`Partial` here is CORRECT and is not the `typeToPrefsKey` mistake.**
+ *
+ * The distinction is what a missing key MEANS. A missing `typeToPrefsKey`
+ * entry silently ignored a user's opt-out — a real setting that read as
+ * honoured and was not. A missing entry here means "no Meta-approved template
+ * exists for this type", which is a fact about the Meta account, not a bug:
+ * six of the 28 types have one, and the rest legitimately fall back to
+ * free-form (which Meta accepts inside the 24-hour customer-service window
+ * and rejects outside it — the runner already logs that rejection).
+ *
+ * Getting six approved templates is a Meta Business review process, not a
+ * code change, so listing all 28 here with empty values would be a
+ * `Record<…>` that lies about coverage.
+ *
+ * The six that ARE approved are the order lifecycle, which is also the set
+ * gated behind the buyer's ₹10 addon above — the two lists agree on purpose.
+ */
 const WHATSAPP_TEMPLATE_FIELD = {
     order_placed: "whatsappTemplateOrderPlaced",
     order_confirmed: "whatsappTemplateOrderConfirmed",
@@ -56,6 +100,46 @@ export async function listNotifications(userId, limit = 20) {
 export async function getUnreadNotificationCount(userId) {
     return notificationRepository.getUnreadCount(userId);
 }
+/**
+ * Which portal each notification type belongs to.
+ *
+ * `Record<NotificationType, …>`, so a new type cannot compile without an
+ * answer — the same discipline `typeToPrefsKey` needed after it silently
+ * omitted three types and ignored those users' opt-outs.
+ */
+const TYPE_AUDIENCE = {
+    // Buyer-facing: the order lifecycle they are waiting on.
+    order_placed: "buyer",
+    order_confirmed: "buyer",
+    order_shipped: "buyer",
+    order_delivered: "buyer",
+    order_cancelled: "buyer",
+    refund_initiated: "buyer",
+    payment_review: "buyer",
+    emi_installment_due_soon: "buyer",
+    emi_installment_overdue: "buyer",
+    prize_won: "buyer",
+    prize_reveal_expired: "buyer",
+    product_available: "buyer",
+    bid_placed: "buyer",
+    bid_outbid: "buyer",
+    bid_won: "buyer",
+    bid_lost: "buyer",
+    offer_responded: "buyer",
+    offer_counter_accepted: "buyer",
+    offer_expired: "buyer",
+    review_replied: "buyer",
+    catalogue_images_stale: "buyer",
+    // Seller-facing.
+    auction_ended: "seller", // "your auction closed with no winner"
+    offer_received: "seller",
+    review_approved: "seller",
+    // Account-level, which lives in the user portal for everyone.
+    welcome: "buyer",
+    account_action: "buyer",
+    system: "buyer",
+    promotion: "buyer",
+};
 /**
  * Create an in-app notification and fan out to enabled external channels.
  *
@@ -67,9 +151,26 @@ export async function getUnreadNotificationCount(userId) {
  *   5. The required credentials are set in siteSettings.credentials
  */
 export async function sendNotification(input) {
-    const { userEmail, userPhone, emailHtml, ...notifInput } = input;
+    const { userEmail, userPhone, emailHtml, audience, ...notifInput } = input;
+    /*
+     * Fill `actionUrl` when the caller did not.
+     *
+     * It was set by 5 of 40 call sites, so 35 notifications arrived in the bell
+     * as text with nothing to click. Resolving it HERE rather than asking 35
+     * writers to remember means the destination is right by construction, and
+     * changing where a `bid` notification lands is one edit rather than a sweep.
+     *
+     * A caller-supplied value always wins — a few writers legitimately point at
+     * something the relatedType cannot express (the payment-proof upload page
+     * rather than the order page).
+     */
+    const resolvedActionUrl = notifInput.actionUrl ??
+        resolveNotificationActionUrl(notifInput.relatedType, notifInput.relatedId, audience ?? TYPE_AUDIENCE[notifInput.type] ?? "buyer");
     // Always write the in-app notification first.
-    const notification = await notificationRepository.create(notifInput);
+    const notification = await notificationRepository.create({
+        ...notifInput,
+        ...(resolvedActionUrl ? { actionUrl: resolvedActionUrl } : {}),
+    });
     // Load channel config + credentials (one Firestore read).
     let settings;
     try {
@@ -102,6 +203,20 @@ export async function sendNotification(input) {
     const resolvedPhone = userPhone ??
         (fetchedUserDoc?.phoneNumber ? decryptPii(fetchedUserDoc.phoneNumber) : undefined);
     // Map NotificationType to a NotificationTypePrefs key.
+    /*
+     * 🛑 COMPLETE and compile-checked: `Record<NotificationType, …>`, not
+     * `Partial<Record<string, …>>`.
+     *
+     * The partial version silently omitted `emi_installment_due_soon`,
+     * `emi_installment_overdue` and `payment_review` — and a missing key means
+     * `typeKey` is undefined, so the opt-out check below never fires and the
+     * user's preference is IGNORED. A silently-ignored opt-out is worse than a
+     * missing feature: the toggle is right there, it reads as honoured, and
+     * mail keeps arriving.
+     *
+     * Typed on the union so the next type added cannot compile without an
+     * answer to "which toggle silences this".
+     */
     const typeToPrefsKey = {
         order_placed: "orderUpdates", order_confirmed: "orderUpdates",
         order_shipped: "orderUpdates", order_delivered: "orderUpdates",
@@ -116,6 +231,19 @@ export async function sendNotification(input) {
         product_available: "system",
         prize_won: "orderUpdates",
         prize_reveal_expired: "orderUpdates",
+        // Money owed on an order. Under orderUpdates rather than a new toggle:
+        // an EMI installment IS an order update, and inventing an eighth
+        // preference key means an existing user's saved prefs have no value for
+        // it — which reads as "off" or "on" depending on the default and is a
+        // migration nobody asked for.
+        emi_installment_due_soon: "orderUpdates",
+        emi_installment_overdue: "orderUpdates",
+        // The manual-payment review queue — the buyer's proof was verified,
+        // rejected, or needs re-uploading. Squarely an order update.
+        payment_review: "orderUpdates",
+        // "Your catalogue photos are going stale" — housekeeping about the user's
+        // own account, which is what `system` covers.
+        catalogue_images_stale: "system",
     };
     const typeKey = typeToPrefsKey[type];
     // If the user has explicitly disabled this notification type, skip all external channels.
@@ -138,7 +266,24 @@ export async function sendNotification(input) {
                 await withChannelRetry("email", () => emailProvider.send({
                     to: resolvedEmail,
                     subject: title,
-                    html: emailHtml ?? `<p>${message}</p>`,
+                    /*
+                     * A real template, not `<p>{message}</p>`.
+                     *
+                     * `emailHtml` existed on the input from the day the channel was
+                     * built and NOT ONE of the 40 call sites passed it, so all 28
+                     * types shipped a bare paragraph — no framing, no branding,
+                     * nothing to click. Rendering here rather than asking 40 writers
+                     * to remember is what makes that structurally impossible to
+                     * regress: a caller-supplied `emailHtml` still wins, for the
+                     * handful of flows with genuinely bespoke mail.
+                     */
+                    html: emailHtml ??
+                        renderNotificationEmail(type, {
+                            title,
+                            message,
+                            siteName: fromName,
+                            actionUrl: absoluteActionUrl(resolvedActionUrl),
+                        }),
                     text: message,
                 }));
                 emailStatus = "sent";

package/dist/features/admin/schemas/firestore.d.ts

@@ -4,7 +4,18 @@
  */
 import type { AboutContentDocument } from "../../about/schemas/firestore";
 export declare const ADMIN_CHECKOUT_BYPASS_FLAG_KEY: "adminCheckoutBypass";
-export type NotificationType = "order_placed" | "order_confirmed" | "order_shipped" | "order_delivered" | "order_cancelled" | "bid_placed" | "bid_outbid" | "bid_won" | "bid_lost" | "auction_ended" | "review_approved" | "review_replied" | "product_available" | "promotion" | "system" | "welcome" | "account_action" | "offer_received" | "offer_responded" | "offer_expired" | "offer_counter_accepted" | "refund_initiated" | "prize_won" | "prize_reveal_expired" | "emi_installment_due_soon" | "emi_installment_overdue" | "payment_review";
+export declare const NOTIFICATION_TYPE_VALUES: readonly ["order_placed", "order_confirmed", "order_shipped", "order_delivered", "order_cancelled", "bid_placed", "bid_outbid", "bid_won", "bid_lost", "auction_ended", "review_approved", "review_replied", "product_available", "promotion", "system", "welcome", "account_action", "offer_received", "offer_responded", "offer_expired", "offer_counter_accepted", "refund_initiated", "prize_won", "prize_reveal_expired", "emi_installment_due_soon", "emi_installment_overdue", "payment_review", "catalogue_images_stale"];
+export type NotificationType = (typeof NOTIFICATION_TYPE_VALUES)[number];
+/**
+ * What a notification points AT. Drives the shared `actionUrl` resolver, so a
+ * value here without a per-record page in some role is a notification that
+ * lands nowhere.
+ *
+ * Runtime array for the same reason as the type union above — and
+ * `catalogueItem` was being sent with an `as never` cast rather than added.
+ */
+export declare const NOTIFICATION_RELATED_TYPE_VALUES: readonly ["order", "product", "bid", "review", "blog", "user", "offer", "support_ticket", "scammer", "catalogueItem", "payout", "store"];
+export type NotificationRelatedType = (typeof NOTIFICATION_RELATED_TYPE_VALUES)[number];
 import type { BaseDocument } from "../../../_internal/shared/types/base-document";
 export type NotificationPriority = "low" | "normal" | "high";
 export interface NotificationDocument extends BaseDocument {
@@ -19,7 +30,7 @@ export interface NotificationDocument extends BaseDocument {
     isRead: boolean;
     readAt?: Date;
     relatedId?: string;
-    relatedType?: "order" | "product" | "bid" | "review" | "blog" | "user" | "offer" | "support_ticket" | "scammer";
+    relatedType?: NotificationRelatedType;
     /** Outcome of the async whatsappNotify job for this notification's WhatsApp send, if one was enqueued. */
     whatsappStatus?: "queued" | "sent" | "failed" | "skipped";
     /** jobs/{id} doc that ran (or is running) the WhatsApp send for this notification. */
@@ -43,32 +54,16 @@ export declare const NOTIFICATION_FIELDS: {
     readonly RELATED_TYPE: "relatedType";
     readonly CREATED_AT: "createdAt";
     readonly UPDATED_AT: "updatedAt";
-    readonly TYPE_VALUES: {
-        readonly ORDER_PLACED: NotificationType;
-        readonly ORDER_CONFIRMED: NotificationType;
-        readonly ORDER_SHIPPED: NotificationType;
-        readonly ORDER_DELIVERED: NotificationType;
-        readonly ORDER_CANCELLED: NotificationType;
-        readonly BID_PLACED: NotificationType;
-        readonly BID_OUTBID: NotificationType;
-        readonly BID_WON: NotificationType;
-        readonly BID_LOST: NotificationType;
-        readonly AUCTION_ENDED: NotificationType;
-        readonly REVIEW_APPROVED: NotificationType;
-        readonly REVIEW_REPLIED: NotificationType;
-        readonly PRODUCT_AVAILABLE: NotificationType;
-        readonly PROMOTION: NotificationType;
-        readonly SYSTEM: NotificationType;
-        readonly WELCOME: NotificationType;
-        readonly OFFER_RECEIVED: NotificationType;
-        readonly OFFER_RESPONDED: NotificationType;
-        readonly OFFER_EXPIRED: NotificationType;
-        readonly OFFER_COUNTER_ACCEPTED: NotificationType;
-        readonly REFUND_INITIATED: NotificationType;
-        readonly ACCOUNT_ACTION: NotificationType;
-        readonly PRIZE_WON: NotificationType;
-        readonly PRIZE_REVEAL_EXPIRED: NotificationType;
-    };
+    /**
+     * SCREAMING_SNAKE accessors, DERIVED from `NOTIFICATION_TYPE_VALUES`.
+     *
+     * This was a fifth hand-written copy of the union — 24 of the 28 values,
+     * missing `emi_installment_due_soon`, `emi_installment_overdue`,
+     * `payment_review` and `catalogue_images_stale` — and every entry carried an
+     * `as NotificationType` cast, which is precisely the assertion that lets a
+     * wrong string through. Built from the array now, so it cannot be short.
+     */
+    readonly TYPE_VALUES: { [K in NotificationType as Uppercase<K>]: K; };
     readonly PRIORITY_VALUES: {
         readonly LOW: NotificationPriority;
         readonly NORMAL: NotificationPriority;
@@ -82,7 +77,7 @@ export type NotificationUpdateInput = Partial<Pick<NotificationDocument, "isRead
 export declare const notificationQueryHelpers: {
     readonly byUser: (userId: string) => readonly ["userId", "==", string];
     readonly unread: (userId: string) => readonly [readonly ["userId", "==", string], readonly ["isRead", "==", false]];
-    readonly byType: (type: NotificationType) => readonly ["type", "==", NotificationType];
+    readonly byType: (type: NotificationType) => readonly ["type", "==", "system" | "welcome" | "promotion" | "order_placed" | "order_confirmed" | "order_shipped" | "order_delivered" | "order_cancelled" | "bid_placed" | "bid_outbid" | "bid_won" | "bid_lost" | "auction_ended" | "review_approved" | "review_replied" | "product_available" | "account_action" | "offer_received" | "offer_responded" | "offer_expired" | "offer_counter_accepted" | "refund_initiated" | "prize_won" | "prize_reveal_expired" | "emi_installment_due_soon" | "emi_installment_overdue" | "payment_review" | "catalogue_images_stale"];
 };
 export interface ChatRoomDocument extends BaseDocument {
     buyerId: string;

package/dist/features/admin/schemas/firestore.js

@@ -8,6 +8,85 @@ import { DEFAULT_AUCTION_BID_INCREMENT_TIERS } from "../../../_internal/shared/f
 // single occurrence in schemas. Splitting the literal makes the substring
 // audit-invisible while keeping the runtime key correct.
 export const ADMIN_CHECKOUT_BYPASS_FLAG_KEY = "adminCheckoutBypass";
+/*
+ * 🛑 The ONE notification-type union. Four existed until 2026-08-26:
+ *
+ *   · this one (27) — what `NotificationDocument.type` actually holds
+ *   · `constants/notification-types.ts` (9) — fed the admin filter chips and
+ *     the per-channel allow-list, so the admin list could not filter 18 of
+ *     the 27 real types and an admin literally could not allow-list
+ *     `offer_received` or `payment_review` for email or WhatsApp
+ *   · `features/account/types/index.ts` (5: order|offer|promo|system|message)
+ *     — a different vocabulary entirely, on a `UserNotification` type with
+ *     zero real consumers
+ *   · `seed/factories/notification.factory.ts` (9) — and THIS is the one
+ *     `appkit/src/index.ts` exported publicly as `NotificationType`, so every
+ *     external consumer got the seed factory's guess
+ *
+ * Between them they invented FOUR values no notification has ever had:
+ * `review_posted`, `payout_processed`, `review_received`, `payout_completed`.
+ * Note the first two and the last two are different spellings of the same two
+ * imagined concepts, which is how independent copies drift.
+ *
+ * A runtime array with the type derived from it, so a Zod enum, a chip list
+ * and a `Record<NotificationType, …>` all resolve here and a new value is one
+ * edit. Same shape as `ALL_LISTING_TYPES` after Root Cause #61.
+ */
+export const NOTIFICATION_TYPE_VALUES = [
+    "order_placed",
+    "order_confirmed",
+    "order_shipped",
+    "order_delivered",
+    "order_cancelled",
+    "bid_placed",
+    "bid_outbid",
+    "bid_won",
+    "bid_lost",
+    "auction_ended",
+    "review_approved",
+    "review_replied",
+    "product_available",
+    "promotion",
+    "system",
+    "welcome",
+    "account_action",
+    "offer_received",
+    "offer_responded",
+    "offer_expired",
+    "offer_counter_accepted",
+    "refund_initiated",
+    "prize_won",
+    "prize_reveal_expired",
+    "emi_installment_due_soon",
+    "emi_installment_overdue",
+    "payment_review",
+    // Was being SENT with an `as never` cast on the whole payload, which is how
+    // it stayed off this union: the cast silenced the one signal that would
+    // have said so, and with it every other field's type-check on that call.
+    "catalogue_images_stale",
+];
+/**
+ * What a notification points AT. Drives the shared `actionUrl` resolver, so a
+ * value here without a per-record page in some role is a notification that
+ * lands nowhere.
+ *
+ * Runtime array for the same reason as the type union above — and
+ * `catalogueItem` was being sent with an `as never` cast rather than added.
+ */
+export const NOTIFICATION_RELATED_TYPE_VALUES = [
+    "order",
+    "product",
+    "bid",
+    "review",
+    "blog",
+    "user",
+    "offer",
+    "support_ticket",
+    "scammer",
+    "catalogueItem",
+    "payout",
+    "store",
+];
 export const NOTIFICATIONS_COLLECTION = "notifications";
 export const NOTIFICATIONS_INDEXED_FIELDS = [
     "userId",
@@ -31,32 +110,16 @@ export const NOTIFICATION_FIELDS = {
     RELATED_TYPE: "relatedType",
     CREATED_AT: "createdAt",
     UPDATED_AT: "updatedAt",
-    TYPE_VALUES: {
-        ORDER_PLACED: "order_placed",
-        ORDER_CONFIRMED: "order_confirmed",
-        ORDER_SHIPPED: "order_shipped",
-        ORDER_DELIVERED: "order_delivered",
-        ORDER_CANCELLED: "order_cancelled",
-        BID_PLACED: "bid_placed",
-        BID_OUTBID: "bid_outbid",
-        BID_WON: "bid_won",
-        BID_LOST: "bid_lost",
-        AUCTION_ENDED: "auction_ended",
-        REVIEW_APPROVED: "review_approved",
-        REVIEW_REPLIED: "review_replied",
-        PRODUCT_AVAILABLE: "product_available",
-        PROMOTION: "promotion",
-        SYSTEM: "system",
-        WELCOME: "welcome",
-        OFFER_RECEIVED: "offer_received",
-        OFFER_RESPONDED: "offer_responded",
-        OFFER_EXPIRED: "offer_expired",
-        OFFER_COUNTER_ACCEPTED: "offer_counter_accepted",
-        REFUND_INITIATED: "refund_initiated",
-        ACCOUNT_ACTION: "account_action",
-        PRIZE_WON: "prize_won",
-        PRIZE_REVEAL_EXPIRED: "prize_reveal_expired",
-    },
+    /**
+     * SCREAMING_SNAKE accessors, DERIVED from `NOTIFICATION_TYPE_VALUES`.
+     *
+     * This was a fifth hand-written copy of the union — 24 of the 28 values,
+     * missing `emi_installment_due_soon`, `emi_installment_overdue`,
+     * `payment_review` and `catalogue_images_stale` — and every entry carried an
+     * `as NotificationType` cast, which is precisely the assertion that lets a
+     * wrong string through. Built from the array now, so it cannot be short.
+     */
+    TYPE_VALUES: Object.fromEntries(NOTIFICATION_TYPE_VALUES.map((v) => [v.toUpperCase(), v])),
     PRIORITY_VALUES: {
         LOW: "low",
         NORMAL: "normal",

package/dist/features/cart/actions/cart-actions.d.ts

@@ -4,10 +4,50 @@
  * Pure business functions — auth, rate-limiting, and Next.js specifics
  * are handled by the calling server action in the consumer.
  */
-import type { AddToCartInput, CartDocument, UpdateCartItemInput } from "../schemas";
+import type { AddToCartInput, CartDocument, CartGroupSource, UpdateCartItemInput, UpdateCartGroupMembersInput } from "../schemas";
+/**
+ * Lane gate. While a higher-obligation lane (a won auction, then an accepted
+ * offer) is outstanding, no NEW shopping may be added — otherwise the buyer can
+ * keep deferring something they already committed to by piling more into the
+ * cart. Enforced on the server, not only in the UI: the UI hint is a courtesy,
+ * this is the rule.
+ *
+ * 🛑 Every add-to-cart entry point must call this. It lived inline inside
+ * `addItemToCart` and therefore covered exactly one of the four ways a line can
+ * be created — `addBundleToCartAction` and `POST /api/cart` both call
+ * `cartRepository.addItem` directly and so bypassed it entirely, letting a buyer
+ * with an unpaid auction win keep shopping.
+ *
+ * Returns the loaded cart so the caller doesn't pay a second read.
+ */
+export declare function assertCanAddNewItems(userId: string): Promise<CartDocument>;
 export declare function addItemToCart(userId: string, input: AddToCartInput): Promise<CartDocument>;
 /** Error code the client maps to a lane-aware message. */
 export declare const CART_LANE_BLOCKED = "CART_LANE_BLOCKED";
+/** Max members one grouped line may hold. Keeps the batch read bounded (Rule #6). */
+export declare const GROUP_LINE_MAX_MEMBERS = 20;
+export interface AddGroupLineToCartInput {
+    /** `product.groupId` for a product group, or the `groupedListings` doc id. */
+    groupId: string;
+    groupSource: CartGroupSource;
+    /** Ids and quantities ONLY — every other field is re-resolved server-side. */
+    members: Array<{
+        productId: string;
+        quantity: number;
+    }>;
+}
+/**
+ * Add a buyer-assembled selection of group members as ONE cart line.
+ *
+ * The client sends ids and quantities and nothing else. Accepting a price, a
+ * title or an image from the browser would be a ₹1-group exploit; every
+ * snapshot below is read from Firestore here.
+ *
+ * A rejected member fails the WHOLE request, naming the offender. Silently
+ * dropping it would hand the buyer a line that quietly isn't what they picked —
+ * the "wrong data, no error" failure nobody can report.
+ */
+export declare function addGroupLineToCart(userId: string, input: AddGroupLineToCartInput): Promise<CartDocument>;
 /**
  * Won-auction lines are non-removable and fixed-quantity — the buyer committed
  * to the purchase by bidding, and letting them delete it would turn every
@@ -18,6 +58,12 @@ export declare const CART_LANE_BLOCKED = "CART_LANE_BLOCKED";
  * and the offer simply lapses at its `checkoutDeadline`.
  */
 export declare function updateCartItem(userId: string, itemId: string, input: UpdateCartItemInput): Promise<CartDocument>;
+/**
+ * Replace a grouped line's member quantities. A member set to 0 is dropped;
+ * dropping the last one removes the line (enforced in the repository so a
+ * forgetful caller can't leave an empty ghost line behind).
+ */
+export declare function updateCartGroupMembers(userId: string, itemId: string, input: UpdateCartGroupMembersInput): Promise<CartDocument>;
 export declare function removeCartItem(userId: string, itemId: string): Promise<CartDocument>;
 export declare function clearCart(userId: string): Promise<CartDocument>;
 export declare function mergeGuestCart(userId: string, items: Array<{