vibecodng.com

Free MCP betaIndex and tools live

Measured entry

hextaui-team-chat

chatminimal-flat

A client-side React team chat card shipped as a shadcn registry block. It renders grouped messages, avatars, an empty state, a composer, mentions, and optional AI and attachment controls. It depends on local shadcn-style UI primitives and path aliases, a class-name utility, Lucide icons, and Radix-backed avatar, slot, and separator pieces.

Specimen
Harness screenshot of hextaui-team-chat at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-team-chat at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-team-chat at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

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.

Harness measurements recorded for hextaui-team-chat
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical1
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal38.2 KB (103.6 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 1m 5s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/team/team-chat.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A solid presentational starting point for teams already invested in shadcn conventions, with clean responsive mounting in the configured harness. It needs a shadcn-style setup, and it is not production-ready until the send button is named and attachment behavior is implemented.

Use it if

  • You already use shadcn conventions and want a compact chat shell wired to your own message service.
  • You need empty, sending, grouped-message, mention, and current-user presentation in one copyable component.
  • You are prepared to add an accessible label to the icon-only send control before release.

Skip it if

  • You need a drop-in package that works without local aliases, utilities, design tokens, and registry primitives.
  • You need complete chat behavior such as transport, persistence, live updates, or channel navigation.
  • You expect the attachment control to open a picker and call the upload callback without additional implementation.
  • You cannot remediate the unnamed send button flagged by the accessibility check.

Install

Installation record for hextaui-team-chat
Declared dependencies@radix-ui/react-avatar, @radix-ui/react-slot, @radix-ui/react-separator
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, add React and Lucide icons, the required Radix packages, Tailwind-compatible theme tokens, the local class-name helper and path alias, plus equivalents for Avatar, Button, Card, Empty, Input Group, and Separator. Then wire message delivery, file selection, upload handling, and accessible labeling.

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/preetsuthar17/HextaUI
License
MIT
Record published
2026-08-14

Alternatives

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.