Getting Started

The Vue registry is assembled from the package-local registry definitions in packages/vue/src/registry/* and published under apps/vue/public/r.

Consumer setup

Projects that install Tile UI through the shadcn CLI should register the Tile UI namespace in components.json:

{
	"registries": {
		"@tile-ui": "https://vue.tileui.zmorg.cn/r/{name}.json"
	}
}

Once configured, registry dependencies such as @tile-ui/core and @tile-ui/utils resolve without hardcoding the docs site domain into each item payload.

Install an item

pnpm dlx shadcn@latest add @tile-ui/button

The CLI resolves shared dependencies automatically, so installing @tile-ui/button also brings in @tile-ui/core, @tile-ui/utils, and @tile-ui/styles when needed. The styles item copies the shared Sass support files and merges its semantic CSS variables into the global stylesheet configured by components.json; no separate styles command or default-theme import is required.

Tile uses the same semantic variables as current shadcn themes. Existing shadcn values remain the source of truth. Tile’s default theme and reset are optional choices described in Theming, not registry prerequisites.

Build flow

corepack pnpm registry:build:vue

What is included

• Vue TSX component sources
• SCSS files from the shared design system
• Composables and framework-agnostic helpers

The docs site reads the published registry metadata from apps/vue/public/r/registry.json, so the site and the public registry stay aligned.

Registry output

Items write files into a predictable structure:

components/ui/*
composables/*
styles/*