Measured entry

hextaui-team-files

teamminimal-flat

A client-side React card for browsing team files, searching names and tags, uploading by picker or drop, and exposing per-file actions. It ships as a shadcn registry item and expects React, Lucide icons, Radix-backed menu primitives, shared UI components, Tailwind theme classes, and a cn utility. Storage and mutations remain the host application's job.

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

Verdict

A practical presentation layer for a team file list, with clean responsive behavior and callback-driven integration points. It needs a shadcn-style setup because the bare project cannot resolve its shared utility import. Choose it when you are prepared to supply the actual file workflow and error states.

Use it if

  • You need a compact file panel and can connect its upload, download, delete, and access callbacks to your own service.
  • Your app already uses shadcn conventions and you want search, tags, file metadata, an empty state, and optional AI-access controls in one card.
  • You need a layout that stays contained across narrow and wide screens without adding a provider.

Skip it if

  • You need a complete file manager with storage, previews, folders, permissions, progress, or error feedback built in.
  • Your design system does not use shadcn-style aliases, utilities, components, or Tailwind theme tokens and you do not want to port them.
  • You need validation messages for rejected files or robust handling of failed async actions without extending the component.

Install

Installation record for hextaui-team-files
Declared dependencies@radix-ui/react-slot, @radix-ui/react-dropdown-menu
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 the expected path aliases and cn utility, recreate or install the badge, button, card, dropdown-menu, empty, and input-group components, and provide their Tailwind theme tokens. Also install Lucide React plus the Radix slot and dropdown-menu packages, then wire the action callbacks to real storage APIs.

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.