Skip to content

Search documentation

Search guides, examples, and component APIs.

Quick links
↑↓ NavigateEnter OpenEsc Close
Get started

Documentation navigation

Ownership and updates

What belongs to your app

The CLI copies Vue components, public types and visual styles into your project. Edit those files to change markup and presentation. Application text, data, validation and authorization stay in your app. The installed @getweini/vue package owns shared behavior, accessibility relationships and theme foundations. Optional Nebula fonts use a separate CSS import.

The generated weini.json records copied-file hashes, source revisions and foundation requirements separately. Keep it in version control. A foundation upgrade can change behavior without changing copied source; review both.

Review and apply an update

vue
npx @getweini/cli@latest doctor
npx @getweini/cli@latest outdated
npx @getweini/cli@latest update --foundation --dry-run
npx @getweini/cli@latest update --foundation

doctor inspects your real configuration, stylesheet, dependencies, exports and installed files. Missing, incompatible and unverifiable packages are different results. outdated reports copied-source changes and foundation compatibility separately. A normal source update does not silently upgrade the foundation; request that with --foundation.

If a copied file was edited, update stops before overwriting it. Commit your changes, compare the new registry source with your version, and merge deliberately. Do not discard local work or reset hashes to bypass a conflict. Test your actual application after updating. Use --yes only after reviewing the plan.

Versions and public contracts

This documentation describes registry 0.14.2, CLI 0.4.7, and foundation 0.7.9 (published). Consult the changelog and installed-version manifest before upgrading. The registry wire format uses schema v2; API/AI metadata uses schema v1 with immutable release snapshots.

Installed imports such as @getweini/vue/primitives/select are a compatibility contract. Existing paths remain available during this remediation. Advanced package exports are separate from ordinary component imports; unexported source modules are internal. Foundation changes must preserve installed contracts within their declared compatibility range and run packed-consumer checks. A breaking contract requires a new compatible tuple and migration guidance.

Use the canonical manifest, export inventory and AI navigation for exact imports and public parts. AI tools should read the installed version’s contract and executable examples, preserve your edits, and never invent component props from another library.

Supported environments and limits

Vue 3.5 and Tailwind CSS 4 are required. TypeScript 5.9 is the verified baseline. CLI execution supports Node.js 22+ or Bun 1.3+ and detects npm, pnpm, Yarn and Bun lockfiles. Vue/Vite and Nuxt use the same editable source. Browser automation covers current Playwright Chromium, Firefox and WebKit; it does not certify Safari or assistive technology.

Anchored popups stay inside their component subtree. Avoid transformed, filtered, clipped or contained ancestors that change fixed positioning, and stacking contexts underneath other overlays. Modal Dialog, AlertDialog, Sheet and Drawer use the native dialog top layer. Mobile virtual keyboards and pinch zoom require device testing.

Select and MultiSelect use finite rendered option lists. VirtualList is a separate fixed-row utility and does not provide listbox semantics. Keep asynchronous selection reconciliation in your app. Manual NVDA/Firefox, VoiceOver/Safari and physical touch checks remain mandatory before a stable release.