Open source · vishwajit-vm Designed · Phase 3
Strutvane UI
Metadata-driven React UI for Strutvane or any OpenAPI backend
@strutvane/ui turns API metadata into a complete admin interface: list pages with filters, bulk actions and export, create and edit forms, detail pages, and auth and admin screens. It reads the Strutvane manifest — or infers one from any OpenAPI 3.x API — and every component is owned, shadcn-compatible code you can override or eject.
Built for: Full-stack teams using Strutvane, and front-end developers who just want a UI for an existing OpenAPI backend.
Packages on npm
@strutvane/ui↗Name reserved · planned for 0.3
↓ Scroll to explore the problem, architecture and stack
The problem
Admin UIs are 80% the same tables, forms and filters, yet teams rebuild them for every resource — and front-end filters, validation and permissions quietly drift away from what the API actually enforces.
Why it matters
Driving the UI from the same metadata as the API keeps them in sync, and owned components mean the generated screens are a starting point, not a cage.
What you can do with it
How it’s built
A simplified view of the architecture — follow the dots as a request moves down the layers.
A request, step by step
- The UI loads the manifest — from Strutvane, inferred from OpenAPI, or a local ui.resources.ts.
- Resources register their routes; list state lives in the URL so views are shareable.
- List queries go to the server, which does all filtering, sorting and paging.
- The registry picks the right widget for each field: field override → named widget → field type → default.
- Validation errors map to the deepest matching field (for example lines[1].amount), else its parent, else a form banner.
Tech stack
What I built
- Designed the UI package: a headless core with no React, a React renderer, and owned components in your web/ folder.
- Proved it in spike 08: 48 tests, axe-core 0 accessibility violations, 500 virtualized rows, and 5 real UI defects found and fixed.
- Designed one shared filter builder for the URL parser and the filter bar, so client and server filters can’t drift (ADR-0014).
- Designed a typed component registry and error placement that maps a 422 issue to the exact field it belongs to.
Hard problems & how I solved them
✅ All list operations run on the server, and the URL parser and filter bar share one filter builder (ADR-0014).
✅ A typed registry resolves components field-first, and one shared field wrapper owns accessibility for every widget.