Vendure UI

Apply Vendure's component decisions and strong-default screen recipes while keeping domain data and application state in the consumer.

Classify the host

Inspect the task and repository before choosing imports.

1. Treat code as a Dashboard extension when it imports or calls defineDashboardExtension from @vendure/dashboard, or when a VendurePlugin declares a dashboard entry.
2. In a Dashboard extension, import design-system UI and dashboard layout/form APIs from @vendure/dashboard. Do not mix in direct @vendure-io/ui imports unless the repository documents an exception.
3. In a standalone consumer, import each component from its exact @vendure-io/ui/components/atoms/* or components/molecules/* subpath. Do not create barrel imports.
4. Inspect the installed package source and types before assuming an export or prop. The source is the API authority.

Complete classification when the host and import surface are explicit.

Choose the composition

Follow this order: