ecomcn

shadcn/ui gives you ~40 primitives and a handful of dashboard blocks. It has never shipped a buy box, a faceted filter panel, or an order summary — the things every store rebuilds from scratch. ecomcn is those things: 30 blocks that take a shopper from the home page to the parcel at the door, each one a file you own, installed with the same command as a button.

The demo store is built from nothing else — filter a listing, open a product, add to the bag, check out through address, delivery and payment, and land on the order confirmation with tracking.

Browse — filter-panel, sort-toolbar, product-grid, product-card	Cart — cart-sheet, cart-line-item
Product — review-summary	Checkout — payment-selector

Blocks are organised by the decision a buyer is making, not by widget type. That's why you can find what you need by the problem you have.

ecomcn is listed in the shadcn Registry Directory, so blocks install by name — no setup:

npx shadcn@latest add @ecomcn/product-card
npx shadcn@latest add @ecomcn/order-summary

The first add looks @ecomcn up in the directory and writes it into your components.json. Blocks that pull other ecomcn blocks resolve on their own — product-grid brings product-card, which brings price-tag.

Start with the house theme if you want the look from the screenshots:

npx shadcn@latest add @ecomcn/theme-editorial

Older shadcn CLI, or want the registry pinned in your config? Register it yourself once per project, then use the same add commands. {name} is literal — the CLI substitutes the item name.

npx shadcn@latest registry add @ecomcn=https://ecomcn.vercel.app/r/{name}.json

• Motion, with a morph — the quick view and size guide grow out of what opened them, the cart sheet grows out of the bag button, panels grow to their real height, and all of it falls back to a fade under prefers-reduced-motion. motion and lucide-react are the only runtime dependencies, and only on the blocks that use them
• Intl.NumberFormat pricing with currency and locale props on every money-rendering block
• Loading, empty, out-of-stock and error states shipped in the same file
• Keyboard paths for every hover affordance, and no colour-only state
• Both shadcn bases — every block installs and compiles against Base UI and Radix, checked in CI on every change
• Checkout without card data — payment-selector is a slot for your provider's own fields (Stripe, Adyen, PayPal) and never renders a card number
• Source you own — no provider, no config object, no API to fight

30 blocks across five stages, from the home page to the parcel at the door — the whole catalogue, shipped. Full spec, with per-block design notes and the hard parts: docs/BLOCK-CATALOG.md.

Plus theme-editorial, the house theme from the screenshots. See the blocks composed into a listing page and a product page, or shop through the demo store.

registry.json                       root catalogue (include-based)
src/registry/ecomcn/<block>/
  registry.json                     one item file per block
  <block>.tsx                       the source that gets copied
src/lib/utils.ts                    cn()
scripts/verify-install.mjs          installs every block into clean Base UI + Radix apps
scripts/check-registry.mjs          the Registry Directory requirements, as checks
docs/                               catalogue, design rules, publishing guide
.github/workflows/registry.yml      validate → build → typecheck → install test

pnpm install
pnpm registry:validate     # schema, duplicate names, include paths, missing files
pnpm registry:build        # emits public/r/*.json
pnpm registry:check        # rebuilds public/r, then checks the directory requirements
pnpm dev                   # site + docs; re-syncs the registry mirrors on every change
pnpm test:install          # installs everything into a throwaway app and compiles

Then install into a scratch project and see what an adopter sees:

npx shadcn@latest add https://localhost:3000/r/product-card.json

Read CONTRIBUTING.md — especially the six rules. Open a New block proposal issue before writing code.

MIT. Anything more restrictive and teams won't clear it with legal, which defeats the point.

The product photos on the docs site are free Unsplash photos, used under the Unsplash License and loaded from Unsplash's CDN. They are not in this repo, not in any registry item, and not covered by the MIT licence.