@mohasinac/appkit 4.42.14 → 4.42.16

package/dist/_internal/server/features/digital-code/pool.js

@@ -21,6 +21,7 @@ import { normalizeError } from "../../../../errors/normalize";
 import { serverLogger } from "../../../../monitoring";
 import { ValidationError } from "../../../../errors";
 import { ORDER_FIELDS } from "../../../../constants/field-names";
+import { firestoreTimestampToDate } from "../../../../utils/type.converter";
 import { PRODUCT_COLLECTION, PRODUCT_CODES_SUBCOLLECTION, } from "../../../../features/products/schemas/firestore";
 /**
  * Where a delivered asset's bytes live.
@@ -181,8 +182,28 @@ export async function listPoolEntries(productId) {
             status: c.status,
             ...(c.fileName ? { fileName: c.fileName } : {}),
             ...(c.orderId ? { orderId: c.orderId } : {}),
-            ...(c.claimedAt ? { claimedAt: new Date(c.claimedAt).toISOString() } : {}),
-            ...(c.createdAt ? { createdAt: new Date(c.createdAt).toISOString() } : {}),
+            /*
+             * 🛑 firestoreTimestampToDate, never `new Date(value)`.
+             *
+             * addPoolEntries writes `createdAt: new Date()`, and the Admin SDK stores
+             * that as a Firestore Timestamp and reads it back as one — NOT as a Date.
+             * `new Date(aTimestamp)` is an Invalid Date, and `.toISOString()` on an
+             * Invalid Date THROWS RangeError, so this map took the whole route down
+             * with a 500.
+             *
+             * It hid for as long as it possibly could: mapping over ZERO documents
+             * never throws, so GET answered `[]` for the entire period the pool had
+             * no writer (Root Cause #103) and only began failing once the first entry
+             * existed. The seller then saw "Nothing in the pool yet" — the component
+             * rendering a failed load as an empty state — and the rational response
+             * is to add the codes again, which silently accumulates duplicates.
+             */
+            ...(c.claimedAt
+                ? { claimedAt: firestoreTimestampToDate(c.claimedAt).toISOString() }
+                : {}),
+            ...(c.createdAt
+                ? { createdAt: firestoreTimestampToDate(c.createdAt).toISOString() }
+                : {}),
         };
     });
 }

package/dist/features/admin/components/AdminStoresView.js

@@ -69,9 +69,17 @@ export function AdminStoresView({ children, ...props }) {
         mapRows: (response) => toRecordArray(response.items).map((item, index) => ({
             id: toStringValue(item.id, `store-${index}`),
             primary: toStringValue(item.storeName, "Unnamed store"),
+            // Verified / Featured are rendered here because an admin's first
+            // question about a store is whether it carries either, and the row
+            // is where that gets scanned. The API has always returned both
+            // (route.ts serialises isVerified/isFeatured) and the editor already
+            // seeds from them — only the list never showed them, so the flags
+            // were invisible until you opened each store one at a time.
             secondary: [
                 toStringValue(item.storeSlug, "No slug"),
                 toStringValue(item.ownerId, "No owner"),
+                ...(item.isVerified ? ["Verified"] : []),
+                ...(item.isFeatured ? ["Featured"] : []),
             ].join(" · "),
             status: toStringValue(item.status, "Pending"),
             updatedAt: toRelativeDate(item.updatedAt ?? item.createdAt),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mohasinac/appkit",
-  "version": "4.42.14",
+  "version": "4.42.16",
   "license": "MIT",
   "publishConfig": {
     "access": "public"