arviahq/tidex — explained in plain English
Analysis updated 2026-07-16 · repo last pushed 2026-06-17
Browse and test your React component library without writing separate story files for each component.
Run automated accessibility, interaction, and visual regression tests in CI against your components.
Give designers and product managers a live gallery to tweak props and see results instantly.
Explore and manage design tokens alongside your component documentation in one place.
| arviahq/tidex | arashthr/hugo-flow | argeneau12e/kairos-tx | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | TypeScript | TypeScript | TypeScript |
| Last pushed | 2026-06-17 | — | — |
| Maintenance | Active | — | — |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 3/5 | 3/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing React component library with TypeScript types, you point it at your components folder via a single config file and run a scan command.
Tidex is a tool for teams who build React component libraries and want a visual workbench to browse, test, and document those components without the usual overhead. Instead of requiring developers to write a separate story file for every button, card, or modal, it scans your existing source code and automatically builds a full explorer with live controls, auto-generated docs, design tokens, and built-in accessibility, interaction, and visual testing. The way it works is straightforward in concept: you run a command that scans your components folder, reads the TypeScript types on each component, and generates everything needed to render an interactive preview. From those types it infers what props each component accepts, what variants exist, and how callbacks should wire up to state. The result is a manager UI with tabs for props, variants, docs, tests, visual regression, interactions, and design foundations, all driven by what your code already declares. You configure it through a single config file rather than managing multiple addon configurations. The primary audience is design system teams and frontend developers maintaining a shared component library, especially in monorepos. For example, a company with an internal UI kit used across multiple products could use this to give designers and product managers a live gallery where they can tweak props and see results, while engineers get automated accessibility checks, screenshot-based visual regression tests, and interaction tests that run in CI. It positions itself as a lighter-weight alternative to Storybook by eliminating the need to hand-write and maintain separate story files for every component. A few things stand out about how the project is built. Testing is powered by Playwright under the hood, and the scan output is persisted as JSON artifacts in a hidden folder, which keeps the generated material separate from source code. It also offers a plugin API for adding custom panels or hooking into the generation pipeline, and it works in monorepo setups. The project is quite new (two stars at time of writing), so it is early-stage and likely still evolving rapidly.
Tidex automatically builds an interactive explorer for React component libraries by scanning your source code and reading TypeScript types, no separate story files needed. It generates live previews, docs, design tokens, and accessibility, interaction, and visual testing for teams maintaining shared UI kits.
Mainly TypeScript. The stack also includes TypeScript, React, Playwright.
Active — commit in last 30 days (last push 2026-06-17).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.