Auto-imports

@vizejs/ui and @vizejs/composable can be used without writing import statements. Both packages ship catalog-driven resolvers: every component family and composable entry in the catalogs is picked up automatically, and every name resolves to its direct subpath (@vizejs/ui/dialog, @vizejs/composable/use-toggle). Auto-imported code therefore tree-shakes exactly like hand-written imports, and the resolvers run only at build time.

Nuxt

Both integrations are opt-in options of @vizejs/nuxt:

// nuxt.config.ts
export default defineNuxtConfig({
  modules: ["@vizejs/nuxt"],
  vize: {
    ui: { prefix: "Vz", exclude: ["tooltip"] },
    composables: true,
  },
});

• ui registers every @vizejs/ui component with addComponent (<VzDialogTrigger>, <VzButton>, ...) and auto-imports the use* helpers the families export (useFieldWiring, useSafeAreaInsets, ...). Options: prefix, per-family include / exclude, composables: false to skip the helpers, and the local mode options.
• composables auto-imports every runtime export of @vizejs/composable with addImports. Options: include / exclude entries ("use-toggle"), names, and the local mode options. When both libraries export the same name, the @vizejs/ui registration wins.

Nuxt generates the typed components.d.ts / imports.d.ts declarations, so templates and scripts are fully typed. The packages are resolved from your project, so the installed versions drive what is registered.

Vite (unplugin-vue-components / unplugin-auto-import)

// vite.config.ts
import Components from "unplugin-vue-components/vite";
import AutoImport from "unplugin-auto-import/vite";
import { VizeUiResolver, VizeUiComposablesResolver } from "@vizejs/ui/resolver";
import { VizeComposableResolver } from "@vizejs/composable/resolver";

export default defineConfig({
  plugins: [
    vue(),
    Components({ resolvers: [VizeUiResolver({ prefix: "Vz" })] }),
    AutoImport({ resolvers: [VizeUiComposablesResolver(), VizeComposableResolver()] }),
  ],
});

Prefer presets? vizeUiImports() and vizeComposableImports() return { "<module>": ["name", ...] } maps for AutoImport({ imports: [...] }). For custom setups, createVizeUiComponentDeclarations() and createVizeComposableDeclarations() render the GlobalComponents / global .d.ts declarations the plugins would otherwise generate.

Pulled sources

When you copy families or composables into the project with vize lib pull, set source: "local" so the pulled copies win:

VizeUiResolver({ source: "local" }); // reads ./vize-lib.lock.json
VizeComposableResolver({ source: "local", root: projectRoot, lockfile: "vize-lib.lock.json" });

Items recorded in vize-lib.lock.json resolve to <root>/<dir>/<entry> (for example src/components/vize/families/actions/button/button.ts); everything else falls back to the package unless fallback: false. The same options exist on the Nuxt ui and composables settings.

Keeping the catalogs in sync

The @vizejs/ui resolver manifest is generated from the family catalog with pnpm --filter @vizejs/ui generate:resolver; a test fails when a catalogued family is missing from it. The composable resolver reads COMPOSABLE_CATALOG directly.