create-brainerce-store 1.77.0 → 1.79.0

package/dist/index.js

@@ -31,7 +31,7 @@ var require_package = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "create-brainerce-store",
-      version: "1.77.0",
+      version: "1.79.0",
       description: "Scaffold a production-ready e-commerce storefront connected to Brainerce",
       bin: {
         "create-brainerce-store": "dist/index.js"
@@ -305,7 +305,17 @@ var BRAINERCE_RUNTIME_DEPS = Object.freeze({
   // bare 0, so an older SDK fails type-check at scaffold time. This floor is
   // load-bearing now; it is no longer only about provably getting the
   // corrected README.
-  brainerce: "^2.4.0",
+  //
+  // 2.5.0 is the first SDK that carries the KIT fields, and this floor is
+  // load-bearing for exactly the reason the ones above are. `2.4.0` already
+  // typed `Product.type` as `'SIMPLE' | 'VARIABLE' | 'KIT'` — so
+  // `product.type === 'KIT'` compiles against it and looks fine — but it has no
+  // `kitComponents` and no `kitAvailable`. The scaffolded product card reads
+  // `product.kitAvailable` and the product page reads `product.kitComponents`
+  // off an SDK-typed `Product`, so on an older SDK a scaffolded store fails
+  // type-check at creation. Verified against the published 2.4.0 tarball: zero
+  // files mention either field.
+  brainerce: "^2.5.0",
   "isomorphic-dompurify": "^3.8.0"
 });
 

package/messages/en.json

@@ -11,7 +11,6 @@
     "no": "No",
     "total": "Total",
     "subtotal": "Subtotal",
-    "subtotalExclTax": "Subtotal (excl. tax)",
     "discount": "Discount",
     "generalDiscount": "General Discount",
     "couponDiscount": "Coupon",
@@ -123,6 +122,7 @@
     "addSelectedToCart": "Add Selected to Cart",
     "totalPrice": "Total: {price}",
     "addingAll": "Adding...",
+      "whatsInTheBox": "What's in the box",
     "by": "By"
   },
   "reviews": {
@@ -244,6 +244,7 @@
     "paymentNotConfigured": "Payment Not Configured",
     "paymentNotConfiguredDesc": "Payment has not been set up for this store yet. Please contact the store owner.",
     "paymentError": "Payment Error",
+    "paymentUnavailable": "Payment is unavailable for this store right now. Please contact the store.",
     "paymentRedirectBlocked": "Payment redirect blocked for security reasons. Please contact support.",
     "sandboxTitle": "Sandbox Mode",
     "sandboxDescription": "This is a test order. No real payment will be processed.",
@@ -434,7 +435,7 @@
     "orderPrefix": "Order",
     "productFallback": "Product",
     "statusDraft": "Draft",
-    "statusPending": "Pending",
+    "statusPending": "Awaiting processing",
     "statusProcessing": "Processing",
     "statusOnHold": "On hold",
     "statusPaid": "Paid",
@@ -516,6 +517,8 @@
     "loading": "Loading your order...",
     "errorTitle": "Order not found",
     "notFound": "We couldn't find an order matching this link.",
+    "unavailableTitle": "We could not load your order",
+    "unavailableBody": "Something went wrong on our side. Your order is safe. Please try again in a moment.",
     "missingCheckoutInfo": "Missing order information.",
     "returnHome": "Return Home"
   },
@@ -602,6 +605,9 @@
   "giftCard": {
     "placeholder": "Gift card code",
     "invalidCode": "That gift card code cannot be used on this order.",
+    "applyFailed": "We could not apply that gift card right now. Please try again.",
+    "locked": "Payment has already started, so this order can no longer take a gift card.",
+    "lockedHint": "A gift card is added before the payment step.",
     "removeFailed": "We could not remove that gift card.",
     "applied": "Gift card applied — {amount}"
   }

package/messages/he.json

@@ -11,7 +11,6 @@
     "no": "לא",
     "total": "סה\"כ",
     "subtotal": "סיכום ביניים",
-    "subtotalExclTax": "סיכום ביניים (לפני מע\"מ)",
     "discount": "הנחה",
     "generalDiscount": "הנחה כללית",
     "couponDiscount": "קופון",
@@ -123,6 +122,7 @@
     "addSelectedToCart": "הוסף הנבחרים לעגלה",
     "totalPrice": "סה\"כ: {price}",
     "addingAll": "מוסיף...",
+      "whatsInTheBox": "מה יש בקופסה",
     "by": "מאת"
   },
   "reviews": {
@@ -244,6 +244,7 @@
     "paymentNotConfigured": "תשלום לא מוגדר",
     "paymentNotConfiguredDesc": "התשלום עדיין לא הוגדר לחנות זו. אנא פנו לבעל החנות.",
     "paymentError": "שגיאת תשלום",
+    "paymentUnavailable": "לא ניתן לשלם בחנות זו כרגע. ניתן לפנות לחנות.",
     "paymentRedirectBlocked": "הפניית התשלום נחסמה מטעמי אבטחה. אנא פנו לתמיכה.",
     "sandboxTitle": "מצב בדיקה",
     "sandboxDescription": "זוהי הזמנת בדיקה. לא יבוצע תשלום אמיתי.",
@@ -434,7 +435,7 @@
     "orderPrefix": "הזמנה",
     "productFallback": "מוצר",
     "statusDraft": "טיוטה",
-    "statusPending": "ממתין",
+    "statusPending": "ממתין לטיפול",
     "statusProcessing": "בטיפול",
     "statusOnHold": "מושהה",
     "statusPaid": "שולם",
@@ -516,6 +517,8 @@
     "loading": "טוען את ההזמנה שלך...",
     "errorTitle": "ההזמנה לא נמצאה",
     "notFound": "לא הצלחנו למצוא הזמנה שתואמת לקישור הזה.",
+    "unavailableTitle": "לא הצלחנו לטעון את ההזמנה",
+    "unavailableBody": "משהו השתבש אצלנו. ההזמנה שלכם שמורה. נסו שוב בעוד רגע.",
     "missingCheckoutInfo": "חסר מידע הזמנה.",
     "returnHome": "חזרה לדף הבית"
   },
@@ -602,6 +605,9 @@
   "giftCard": {
     "placeholder": "קוד כרטיס מתנה",
     "invalidCode": "לא ניתן להשתמש בקוד הזה בהזמנה הזאת.",
+    "applyFailed": "לא הצלחנו לממש את כרטיס המתנה כרגע. נסו שוב.",
+    "locked": "התשלום כבר התחיל, אז אי אפשר להוסיף כרטיס מתנה להזמנה הזאת.",
+    "lockedHint": "כרטיס מתנה מוסיפים לפני שלב התשלום.",
     "removeFailed": "לא הצלחנו להסיר את כרטיס המתנה.",
     "applied": "כרטיס מתנה — {amount}"
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-brainerce-store",
-  "version": "1.77.0",
+  "version": "1.79.0",
   "description": "Scaffold a production-ready e-commerce storefront connected to Brainerce",
   "bin": {
     "create-brainerce-store": "dist/index.js"

package/templates/nextjs/base/.eslintrc.json

@@ -14,6 +14,8 @@
                   "!@/core/lib/auth",
                   "!@/core/lib/brainerce",
                   "!@/core/lib/brainerce.server",
+                  "!@/core/lib/capabilities",
+                  "!@/core/lib/display-price",
                   "!@/core/lib/image-hosts",
                   "!@/core/lib/navigation",
                   "!@/core/lib/product-options",

package/templates/nextjs/base/AGENTS.md.ejs

@@ -91,11 +91,12 @@ and handlers, never JSX. Never hardcode catalog content.
 
 ### Rebuilding the look is free. Dropping a feature is not.
 
-Some files under `src/ui/` are the ONLY place a mandatory checklist entry
-exists in this project. Delete one and the capability leaves the store with
-nothing to notice it by: no type error, no console warning, and no visual hole
-either, because these components auto-hide while the merchant has the feature
-switched off, so a deleted one and an idle one look identical on the page.
+Some files under `src/ui/` (and one under `src/core/`) are the ONLY place a
+mandatory checklist entry exists in this project. Delete one and the capability
+leaves the store with nothing to notice it by: no type error, no console
+warning, and no visual hole either, because these components auto-hide while
+the merchant has the feature switched off, so a deleted one and an idle one
+look identical on the page.
 These are the usual casualties of a redesign, because no art-direction brief
 asks for them by name:
 
@@ -103,6 +104,8 @@ asks for them by name:
 product/  back-in-stock-form · customization-fields · modifier-group-selector
           review-form · reviews-section · frequently-bought-together
           discount-badge · stock-badge
+          product-client-section → the KIT "what's in the box" block
+core/     lib/kit.ts → the KIT stock resolver every badge and button reads
 cart/     reservation-countdown · coupon-input · cart-upgrade-banner
           cart-bundle-offer · tax-estimate-line
 home/     discount-banner-strip
@@ -115,6 +118,21 @@ split them in half: all fine. What has to survive a rebuild is the SDK call
 each one makes and the states it handles (loading, empty, failed, and the
 merchant-has-it-off state that renders nothing).
 
+⛔ **The two KIT entries are the ones a redesign silently breaks.** A `KIT` is
+one product assembled from other catalog products, and three things have to
+survive whatever you do to the markup. (1) It is added to the cart as ONE line
+using the kit's own `productId`, with no `variantId` and no modifier
+selections; never loop `product.kitComponents` into `addToCart`, which charges
+the shopper twice and reserves the stock twice. (2) A kit has NO `inventory`
+object, so every badge and buy button must go through `resolveStockInfo` /
+`canPurchaseProduct` from `@/core/lib/kit`; reading `product.inventory`
+directly gives a kit a red "out of stock" badge beside an ENABLED buy button,
+or worse, renders a sold-out kit as buyable. (3) `kitComponents` is display
+only and arrives on the by-slug read alone, never on list responses. And do not
+assume a kit price is fixed: `kitPricingMode` may be `SUM` or
+`SUM_MINUS_PERCENT`, in which case the price is recomputed from the components
+on every read, so never cache one.
+
 The list is short on purpose and it is NOT the specification. It names the
 files people lose, not every mandatory entry. `get-required-features` is the
 specification, and step 1 of "Verify before declaring done" is what actually

package/templates/nextjs/base/CLAUDE.md.ejs

@@ -93,11 +93,12 @@ return state and handlers, never JSX. Never hardcode catalog content.
 
 ### Rebuilding the look is free. Dropping a feature is not.
 
-Some files under `src/ui/` are the ONLY place a mandatory checklist entry
-exists in this project. Delete one and the capability leaves the store with
-nothing to notice it by: no type error, no console warning, and no visual hole
-either, because these components auto-hide while the merchant has the feature
-switched off, so a deleted one and an idle one look identical on the page.
+Some files under `src/ui/` (and one under `src/core/`) are the ONLY place a
+mandatory checklist entry exists in this project. Delete one and the capability
+leaves the store with nothing to notice it by: no type error, no console
+warning, and no visual hole either, because these components auto-hide while
+the merchant has the feature switched off, so a deleted one and an idle one
+look identical on the page.
 These are the usual casualties of a redesign, because no art-direction brief
 asks for them by name:
 
@@ -105,6 +106,8 @@ asks for them by name:
 product/  back-in-stock-form · customization-fields · modifier-group-selector
           review-form · reviews-section · frequently-bought-together
           discount-badge · stock-badge
+          product-client-section → the KIT "what's in the box" block
+core/     lib/kit.ts → the KIT stock resolver every badge and button reads
 cart/     reservation-countdown · coupon-input · cart-upgrade-banner
           cart-bundle-offer · tax-estimate-line
 home/     discount-banner-strip
@@ -117,6 +120,21 @@ split them in half: all fine. What has to survive a rebuild is the SDK call
 each one makes and the states it handles (loading, empty, failed, and the
 merchant-has-it-off state that renders nothing).
 
+⛔ **The two KIT entries are the ones a redesign silently breaks.** A `KIT` is
+one product assembled from other catalog products, and three things have to
+survive whatever you do to the markup. (1) It is added to the cart as ONE line
+using the kit's own `productId`, with no `variantId` and no modifier
+selections; never loop `product.kitComponents` into `addToCart`, which charges
+the shopper twice and reserves the stock twice. (2) A kit has NO `inventory`
+object, so every badge and buy button must go through `resolveStockInfo` /
+`canPurchaseProduct` from `@/core/lib/kit`; reading `product.inventory`
+directly gives a kit a red "out of stock" badge beside an ENABLED buy button,
+or worse, renders a sold-out kit as buyable. (3) `kitComponents` is display
+only and arrives on the by-slug read alone, never on list responses. And do not
+assume a kit price is fixed: `kitPricingMode` may be `SUM` or
+`SUM_MINUS_PERCENT`, in which case the price is recomputed from the components
+on every read, so never cache one.
+
 The list is short on purpose and it is NOT the specification. It names the
 files people lose, not every mandatory entry. `get-required-features` is the
 specification, and step 1 of "Verify before declaring done" is what actually

package/templates/nextjs/base/src/app/checkout/page.tsx

@@ -132,8 +132,18 @@ function CheckoutContent() {
     try {
       setPlacing(true);
       setPlaceError(null);
-      const { orderId } = await getClient().completeCheckout(checkout.id);
-      router.push(`/order-confirmation?orderId=${encodeURIComponent(orderId)}`);
+      await getClient().completeCheckout(checkout.id);
+      // `checkout_id`, NOT the order id. The confirmation page reads
+      // `checkout_id` and every other caller (payment-step, all three of its
+      // redirect paths) sends that. Sending the order id instead meant the page
+      // found no parameter it recognised, made zero requests, and rendered its
+      // "missing payment information" state over an order that had just been
+      // placed and paid for — with the cart still full.
+      //
+      // The order id `completeCheckout` returns is deliberately not used: the
+      // page resolves the order from the checkout, which is also what makes a
+      // reload of the confirmation URL work.
+      router.push(`/order-confirmation?checkout_id=${encodeURIComponent(checkout.id)}`);
     } catch (err) {
       // Said out loud. A silent failure here leaves someone staring at a button
       // that did nothing, holding a card they believe they have already spent.
@@ -1056,6 +1066,13 @@ function CheckoutContent() {
                       className="mt-3"
                       checkoutId={checkout.id}
                       tenders={checkout.tenders ?? []}
+                      // Mirrors the server's own guard. Once an intent exists
+                      // the checkout takes no more tender changes, so the field
+                      // must stop offering them.
+                      locked={
+                        checkout.status === 'PAYMENT_PENDING' ||
+                        checkout.status === 'PAYMENT_PROCESSING'
+                      }
                       formatAmount={(value) =>
                         formatPrice(parseFloat(value), { currency }) as string
                       }
@@ -1068,36 +1085,31 @@ function CheckoutContent() {
             {/* Totals */}
             {checkout &&
               (() => {
-                // When the store prices include tax (VAT-style), the on-row
-                // `checkout.subtotal` is GROSS — it already contains the tax.
-                // Show the net (tax-excluded) value here, then a separate VAT
-                // line below, so the customer sees the breakdown the merchant
-                // asked for. Falls back to the raw subtotal when no breakdown
-                // is available yet (e.g. shipping address not entered).
-                const isInclusive = checkout.taxBreakdown?.pricesIncludeTax === true;
-                // `taxBreakdown.subtotal` is the NET of every taxed line, and
-                // shipping is one of those lines — so it already contains the
-                // shipping net. Rendering it and then adding `shippingAmount`
-                // below counts shipping twice: a real checkout read
-                // 54.06 + 9.99 + 7.93 = 71.98 beside a 61.99 total, three rows
-                // that visibly refuse to add up next to the figure being charged.
+                // Every row in this column is GROSS, and the tax row below is
+                // informational. That is how a VAT receipt reads, it is what
+                // `TaxDisplay` already says on its own line ("VAT 18% included"),
+                // and it is exactly what the order-history summary renders — one
+                // convention across all three, so a shopper who compares the
+                // checkout against the order they later open sees the same
+                // arithmetic twice.
+                //
+                // This deliberately drops an earlier attempt to show a NET
+                // subtotal for inclusive stores. Two things were wrong with it.
+                // It read `taxBreakdown.subtotal`, which is the net of every
+                // TAXED LINE — shipping included — and then added
+                // `shippingAmount` below, counting shipping twice: a real
+                // checkout printed 54.06 + 9.99 + 7.93 beside a 61.99 total.
+                // And a net subtotal cannot coexist with a tax row labelled
+                // "included": either the shopper adds the tax, contradicting the
+                // label, or they do not, and the column falls short of the total
+                // by the whole VAT. Subtracting the shipping net back out fixes
+                // the arithmetic and leaves the contradiction, so the row that
+                // has to go is the special case itself.
                 //
-                // Subtract the shipping net back out so the column reconciles.
-                // The shipping row keeps showing the GROSS amount, which is what
-                // a shopper recognises from the rate they picked.
-                // `shippingNet` comes from the server, never from
-                // `shippingAmount` minus a guess: subtracting the GROSS is only
-                // correct when shipping is untaxed, and a store that taxes
-                // shipping would silently show a short subtotal.
-                const shippingNet =
-                  typeof checkout.taxBreakdown?.shippingNet === 'number'
-                    ? checkout.taxBreakdown.shippingNet
-                    : parseFloat(checkout.shippingAmount) || 0;
-                const displayedSubtotal =
-                  isInclusive && typeof checkout.taxBreakdown?.subtotal === 'number'
-                    ? checkout.taxBreakdown.subtotal - shippingNet
-                    : parseFloat(checkout.subtotal);
-                const subtotalLabel = isInclusive ? tc('subtotalExclTax') : tc('subtotal');
+                // Gross + gross = total, with the VAT stated beneath it:
+                // 52.00 + 9.99 = 61.99, "VAT 18% included 7.93".
+                const displayedSubtotal = parseFloat(checkout.subtotal);
+                const subtotalLabel = tc('subtotal');
                 return (
                   <div className="border-border space-y-2 border-t pt-4 text-sm">
                     <div className="flex items-center justify-between">

package/templates/nextjs/base/src/app/order-status/page.tsx

@@ -4,6 +4,7 @@ import { Suspense, useEffect, useState } from 'react';
 import { useSearchParams } from 'next/navigation';
 import { Link } from '@/core/lib/navigation';
 import type { Order } from 'brainerce';
+import { BrainerceError } from 'brainerce';
 import { getClient } from '@/core/lib/brainerce';
 import { LoadingSpinner } from '@/ui/shared/loading-spinner';
 import { OrderHistory } from '@/components/account/order-history';
@@ -23,6 +24,8 @@ function OrderStatusContent() {
   const [order, setOrder] = useState<Order | null>(null);
   const [loading, setLoading] = useState(true);
   const [error, setError] = useState<string | null>(null);
+  /** Separates our own outage from a link that names no order. */
+  const [unavailable, setUnavailable] = useState(false);
 
   useEffect(() => {
     if (!checkoutId) {
@@ -39,8 +42,18 @@ function OrderStatusContent() {
         if (!cancelled) setOrder(result);
       } catch (err) {
         if (!cancelled) {
-          const message = err instanceof Error ? err.message : t('notFound');
-          setError(message);
+          // "We could not find your order" and "we could not reach the server"
+          // are different facts, and only one of them is about the customer.
+          // A backend outage rendered as ORDER NOT FOUND on the page people
+          // open from their receipt email -- seen for real during a redeploy.
+          // Telling someone the order they just paid for does not exist is
+          // worse than telling them nothing.
+          //
+          // A 4xx really is "no order for this link". Anything else is us.
+          const missing = err instanceof BrainerceError && err.statusCode < 500;
+          if (!missing) console.error('[order-status] could not load order', err);
+          setUnavailable(!missing);
+          setError(missing ? t('notFound') : t('unavailableBody'));
         }
       } finally {
         if (!cancelled) setLoading(false);
@@ -78,7 +91,9 @@ function OrderStatusContent() {
             d="M12 9v2m0 4h.01m-6.938 4h13.856c1.54 0 2.502-1.667 1.732-2.5L13.732 4c-.77-.834-2.694-.834-3.464 0L3.34 16.5c-.77.833.192 2.5 1.732 2.5z"
           />
         </svg>
-        <h1 className="text-foreground text-2xl font-bold">{t('errorTitle')}</h1>
+        <h1 className="text-foreground text-2xl font-bold">
+          {unavailable ? t('unavailableTitle') : t('errorTitle')}
+        </h1>
         <p className="text-muted-foreground mt-2">{error || t('notFound')}</p>
         <Link
           href="/"