create-cartbase 0.1.7 → 0.1.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-cartbase",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "Scaffold a Cartbase storefront: npm create cartbase my-store",
   "license": "MIT",
   "type": "module",

package/template/app/AGENTS.md

@@ -23,7 +23,13 @@ Everything you need is local:
 
 House rules: totals and prices are SERVER truth (render them verbatim);
 always pass a pricing context; consent before tracking; the store API is
-proxied same-origin via next.config rewrites. Part one of the library (the
-part you build the store with) is yours to compose freely; part two (the
-part that takes the money: cart, checkout, payment) is locked and must be
-used, never reimplemented.
+proxied same-origin via next.config rewrites.
+
+What you may change: **everything except payments.** Payments are the one
+thing that cannot be ejected. The cart and the checkout are yours to
+shape, and you should rarely need to eject them: both are built to be
+restyled through the theme tokens and their slots, which is the intended
+route and keeps you on our updates. Eject when tokens genuinely are not
+enough, and know what it means, because we say so at the moment you do
+it: that file leaves our support, stops receiving our fixes, and its
+safety is yours from then on.

package/template/app/CLAUDE.md

@@ -23,7 +23,13 @@ Everything you need is local:
 
 House rules: totals and prices are SERVER truth (render them verbatim);
 always pass a pricing context; consent before tracking; the store API is
-proxied same-origin via next.config rewrites. Part one of the library (the
-part you build the store with) is yours to compose freely; part two (the
-part that takes the money: cart, checkout, payment) is locked and must be
-used, never reimplemented.
+proxied same-origin via next.config rewrites.
+
+What you may change: **everything except payments.** Payments are the one
+thing that cannot be ejected. The cart and the checkout are yours to
+shape, and you should rarely need to eject them: both are built to be
+restyled through the theme tokens and their slots, which is the intended
+route and keeps you on our updates. Eject when tokens genuinely are not
+enough, and know what it means, because we say so at the moment you do
+it: that file leaves our support, stops receiving our fixes, and its
+safety is yours from then on.

package/template/app/docs/components.md

@@ -217,7 +217,7 @@ pure UI over the theme tokens.
 ---
 
 ## Family: lib (`@cartbase/storefront/lib/*`)
-Pure helpers — no React except `dual-price`, no fetches. The SDK never
+Pure helpers — no React except `price`, no fetches. The SDK never
 invents server truths: prices/totals arrive computed from the API
 (`variant.calculated_price`, `cart.total`); these helpers only select and
 format.
@@ -226,10 +226,11 @@ format.
 - `lib/money` — `convertToLocale({amount, currency_code, …})` Intl currency
   formatting (amounts are decimal EUR major units per the store contract);
   `noDivisionCurrencies`.
-- `lib/dual-price` — `<DualPrice amount currencyCode />`: EUR price with the
-  statutory BGN dual display (1 EUR = 1.95583 лв., Bulgarian dual-display
-  law through 2026-08); non-EUR currencies render single. Also exports
-  `EUR_TO_BGN_RATE`.
+- `lib/price` — `<Price amount currencyCode className />`: the amount in its
+  own currency, formatted through `convertToLocale`. Every price in the
+  library renders through it. It shows ONE currency; a store that wants a
+  second one displayed adds it in its own locale layer rather than in
+  every price.
 - `lib/cart-helpers` — `isProductLine` / `isFeeLine` / `productTotal` /
   `productItemCount` / `findFeeLine` + `COD_FEE_METADATA_KEY`. THE single
   source of truth for hiding the backend-injected COD-fee line in cart
@@ -412,7 +413,7 @@ code-first through the error-copy maps, never raw API strings.
   `fields.billingDetails.address` override — the strict-completeness
   IntegrationError fix). `PaymentButton` = the Buy button: re-entry-guarded
   click → `performBuyClick`, cycling processing narration, translated
-  inline errors, DualPrice total.
+  inline errors, Price total.
 - **SDK calls** — renders `checkout.listPaymentProviders` results via the
   hook's `hasCard`/`hasCod`; the click path runs the hook's calls.
 - **Props contract** — hook state + `buyButtonNotReady(Reason?)`,
@@ -964,7 +965,7 @@ component also takes a `labels` prop pick.
 ### `<OrderTotals totals currencyCode items? methodFeeLabel? />` — `order/order-totals`
 
 - **Purpose** — the money breakdown: Subtotal / Shipping (FREE badge at
-  0) / COD fee / Discount (negated) / Tax / Total, all via `DualPrice`.
+  0) / COD fee / Discount (negated) / Tax / Total, all via `Price`.
 - **Data seam** — `OrderTotalsSource` (the decorated cart satisfies it:
   `item_subtotal`, `shipping_subtotal`, `discount_total`, `tax_total`,
   `total`, `payment_method_fee_total`, `payment_method_fee_label`); the summary snapshot adapts

package/template/app/package.json

@@ -9,7 +9,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@cartbase/storefront": "^0.8.0",
+    "@cartbase/storefront": "^0.9.0",
     "next": "16.2.4",
     "react": "19.2.4",
     "react-dom": "19.2.4"