uightA component explorer inside your own dev server

No second process, no second port, no config file. Open /uight and your components are already there.

Zero configuration

With no config and no fixtures, uight lists the components it finds — and the places your own code already uses them — as real, renderable states.

It runs as a Vite plugin in the app's own server. The same aliases, the same CSS, the same Tailwind config. Nothing is mirrored into a second build.

CSF 3 is a declared subset, .storybook/preview is loaded, and anything uight will not run is badged rather than silently skipped.

Fixtures render in a separate realm, so a fixture's global styles and listeners cannot reach the explorer around it.

useFixtureInput at the call site. Controls are never inferred from a prop name, so a control that exists is one you meant.

Every chrome component is replaceable, and the registry ships the source under your own components directory when replacing is not enough.