Measured entry
hextaui-settings-integrations
A client-side React settings card for listing third-party integrations, their connection state, permissions, and last sync, with connect, reconnect, and confirmed disconnect actions. It ships as a shadcn registry block and expects Tailwind styling, Lucide icons, a cn helper, and local Alert Dialog, Badge, Button, and Card primitives backed by Radix.



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 | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 47.5 KB (112.9 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 44s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/settings/settings-integrations.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A solid settings shell with useful status coverage and sensible confirmation for disconnects. The action wiring is intentionally thin, so production state and errors remain your responsibility. It needs a shadcn-style setup and will not mount as a bare drop-in.
Use it if
- You need a settings view that handles connected, disconnected, expired, and error states in one consistent list.
- Your app can supply async connect, disconnect, and reauthorization callbacks while keeping integration data outside the component.
- You already use shadcn conventions and want permissions, sync recency, loading states, and disconnect confirmation included.
Skip it if
- You need the component to perform OAuth, token storage, polling, or data synchronization itself.
- Your design system does not use Tailwind utilities or shadcn-style local primitives and you do not want to adapt the markup.
- You need optimistic state updates or visible error feedback after an action rejects, since the callbacks do not update or surface errors on their own.
Install
| Declared dependencies | @radix-ui/react-alert-dialog, @radix-ui/react-slot |
|---|---|
| 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 and Lucide icons, Radix Alert Dialog and Slot support, Tailwind utilities and matching theme tokens, a cn class-merging helper, and compatible local Alert Dialog, Badge, Button, and Card components. Replace the registry path aliases with paths your bundler resolves.
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/HextaUIAlternatives
Other published entries for the feature-grid pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-feature-grids-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.3KB
- Bare
- pass
- Prov
- NO
- meraki-feature-grid-list-with-imageminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.5KB
- Bare
- pass
- Prov
- NO
- meraki-feature-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 20.2KB
- Bare
- pass
- Prov
- NO