Measured entry

hextaui-team-projects

teamminimal-flat

A client-side React project directory shipped as a HextaUI registry block. It renders searchable cards, member avatars, usage metadata, an empty state, a create dialog, and callback-driven actions. It depends on HextaUI or shadcn UI primitives, Radix packages, Lucide icons, Tailwind classes, and the shared cn utility.

Specimen
Harness screenshot of hextaui-team-projects at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-team-projects at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-team-projects 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-projects
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal71.2 KB (136.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 53s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/team/team-projects.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A credible dashboard block for teams already using HextaUI or shadcn primitives. It builds and mounts cleanly in that environment, but bare mounting fails because it needs a shadcn-style setup. Treat its callbacks as integration seams, not a finished project-management feature.

Use it if

  • You need a team dashboard that presents projects, members, activity metadata, and recent updates in one responsive grid.
  • Your application can supply project data and connect create, open, update, and delete callbacks to its own backend.
  • You already use HextaUI or shadcn conventions and want a composed block rather than assembling the primitives yourself.

Skip it if

  • You need a standalone component with no Tailwind theme, path aliases, shared utility, or registry primitives.
  • You expect a complete editing workflow, because the settings item only invokes an update callback without collecting changes.
  • You require built-in permissions or delete confirmation, since those safeguards must be added by the host application.
  • You want a server-only view or need to avoid the client state and UI primitive dependency set.

Install

Installation record for hextaui-team-projects
Declared dependencies@radix-ui/react-avatar, @radix-ui/react-slot, @radix-ui/react-dialog, @radix-ui/react-dropdown-menu, @radix-ui/react-label, @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 Tailwind theme tokens and utilities, configure the at-sign source alias, provide the cn helper, and copy compatible avatar, badge, button, card, dialog, dropdown menu, empty-state, field, input-group, and textarea primitives. Install their Radix dependencies and Lucide React, then preserve the client component boundary.

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.

License
MIT
Record published
2026-08-14

Alternatives

Other published entries for the team pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.