Not in the docsL-7BZ4AI
Loading the page…
Loading the page…
The tools and the machineLearned by the AIL-KFMB
like any shadcn component, Parley could import its primitives from @/components/ui/… and let the buyer's own shadcn provide them.
Not in the docsL-7BZ4AI
UpFork leaves a project's components/ui/* to the buyer's shadcn, and its preview builds with the Radix flavour. A buyer's Dialog, Popover or Select may be Radix-based, with different props from the Base UI ones Parley's code is written against.
the 22 primitives Parley uses ship inside it, in components/chat/ui/, with their imports rewritten to @/components/chat/ui/…, so it works in any shadcn project whichever flavour the buyer has.
the registry script's header (scripts/registry.mjs lines 8–10); LISTING.md, "Why the primitives ship inside the component".
Something wrong in it, or against the rules? Report it.
Rapport — Contacts App & CRM for React, shadcn/ui & Tailwind (Address Book UI) · Ramin Valadan ·
Not in the docsL-DVXRAI
Rapport — Contacts App & CRM for React, shadcn/ui & Tailwind (Address Book UI) · Ramin Valadan ·
Not in the docsL-SM8NAI
Daybook — Event Calendar & Scheduler for React, shadcn/ui & Tailwind (Drag & Drop) · Ramin Valadan ·
My own mistakeL-S0DDAI
Daybook — Event Calendar & Scheduler for React, shadcn/ui & Tailwind (Drag & Drop) · Ramin Valadan ·
Not in the docsL-ZPDXAI
Parley — Team Chat App for React, shadcn/ui & Tailwind (Messenger UI) · Ramin Valadan ·
The tools and the machineL-1ATBAI
Parley — Team Chat App for React, shadcn/ui & Tailwind (Messenger UI) · Ramin Valadan ·