@kazee-ds/init

Prepared, unpublished version 0.1.19 pins React/Vue 0.12.0, styles 0.13.1 and consumer lint 0.6.0. These versions have no published npm artifacts yet; generated installation output targets them for review, while public npm metadata and consumer MCP pins remain on the last verified release until publication. See release status.

The pinned styles 0.13.1 bundle tokens 0.8.0 unchanged, and fix the Tabs pill/secondary active-indicator color, center enclosed Tabs actions/extras on the tab labels, and keep a selected chip ToggleButton readable on hover/press. Published styles 0.11.0 / tokens 0.7.0 added the AA --ds-color-text-secondary text role, which remains unchanged. Preview-first setup for an existing standalone React or Vue application. Preserve the application's framework, package manager and configuration. Earlier CLI releases targeted private GitLab.

After publication is verified, from an existing application preview with npm exec --yes --package=@kazee-ds/[email protected] -- kazee-init; append --apply after reviewing the plan.

From the design-system checkout, run:

node packages/init/bin/kazee-init.mjs --dir /absolute/path/to/application
node packages/init/bin/kazee-init.mjs --dir /absolute/path/to/application --apply

Supply --framework react|vue or --package-manager npm|pnpm|yarn when detection is ambiguous or unavailable. Explicit choices do not override conflicting lockfiles. Yarn means Classic only; modern Yarn requires the manual guide.

Init adds missing exact Kazee dependencies, merges a public npm scope mapping, appends a framework-specific managed section to AGENTS.md, and generates kazee-setup.md. It preserves unrelated configuration and rejects conflicting versions, registry mappings, edited managed content, workspaces, Next, and Nuxt.

Preview never writes files. Apply preflights all four files and attempts to restore changes after ordinary write failures. Multi-file writes are not crash-atomic. Symlinked and hardlinked write targets are rejected.

Public installs need no read credentials. Init neither creates auth entries nor prints existing credentials; unrelated registry settings are preserved. No installation, network requests, source edits, lockfile updates, Git operations, or CI changes occur inside init.

Follow the generated guide to install dependencies, import CSS once, merge the lint config, and run application checks. ESLint 10 and appropriate parsers remain the application's responsibility. Bundled versions are not a latest-version query.

See docs/consumer-init.md in the repository for verification and limitations.