Measured entry
tripled-comment-thread-shadcnui
chatminimal-flatmotion on file
A client-side React comment thread shipped as a shadcn registry component. It includes nested replies, likes, composing, sorting controls, menus, and motion, with demo data held in local state. It relies on Framer Motion, Lucide icons, shadcn Avatar, Button, Dropdown Menu, and Textarea primitives, plus the shared cn utility and theme tokens.



Measured
Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 1 |
| Axe serious | 1 |
| Axe moderate | 1 |
| Axe minor | 0 |
| Gzip marginal | 104.8 KB (170.2 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 1m 52s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/@uitripled/react-shadcn/src/components/components/comments/comment-thread.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A capable interaction demo and useful starting point, but not a finished comment system. It builds and mounts in the prepared environment, while the accessibility findings need correction before release. The bare mount fails, so it needs a shadcn-style setup and should be adopted only if its dependency cost and integration work fit the project.
Use it if
- You need a ready-made discussion mockup with nested replies and optimistic local interactions.
- Your app already uses shadcn primitives, Tailwind theme tokens, Lucide icons, and Framer Motion.
- You are prepared to connect comment, reply, like, share, sort, and report actions to real application logic.
Skip it if
- You need a production comment system with persistence, authentication, moderation, or server synchronization included.
- Your accessibility gate cannot accept invalid ARIA list structure, insufficient contrast, or duplicate landmark naming without remediation.
- Your bundle budget does not justify adding the motion and UI primitive stack for one thread.
- You want a framework-neutral component or do not use shadcn-style aliases and theme tokens.
Install
| Declared dependencies | framer-motion, react, radix-ui |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add React, Framer Motion, Lucide React, and Radix-backed equivalents for Avatar, Button, Dropdown Menu, and Textarea. Configure the at-sign path alias, provide a cn class-merging helper, add Tailwind and the expected semantic theme tokens, and run it in a client-capable React environment.
Source and credit
This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.
Author repository
github.com/moumen-soliman/uitripledAlternatives
Other published entries for the chat pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hextaui-alertminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 26.8KB
- Bare
- fail
- Prov
- NO
- kibo-bannerminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 33.0KB
- Bare
- fail
- Prov
- NO
- ruixen-comment-threadunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 40.2KB
- Bare
- fail
- Prov
- NO
- ruixen-smart-paste-inputunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 44.4KB
- Bare
- fail
- Prov
- NO
- ruixen-faq-chat-accordionunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 67.7KB
- Bare
- fail
- Prov
- NO
- ruixen-gradient-chat-inputgradient-glow
- Renders
- YES
- A11y
- 0
- Gzip
- 72.6KB
- Bare
- fail
- Prov
- NO