Versions

Package matrix, peer requirements, and how Velkin lines upgrade together.

Overview

Velkin packages on the same line share one version number. Today that line is 0.1.0. Install one wrapper package for your framework — @velkin/ui (and Lit) come along as dependencies. Release notes live on the Changelog.

Package matrix

Package	Role	License	Line
`@velkin/ui`	MIT Lit custom elements (source of truth)	MIT	`0.1.0`
`@velkin/react`	Typed React wrappers for MIT core	MIT	`0.1.0`
`@velkin/vue`	Typed Vue wrappers for MIT core	MIT	`0.1.0`
`@velkin/ui-pro`	Pro Lit components (data table, date picker, …)	Commercial	`0.1.0`
`@velkin/react-pro`	Typed React wrappers for Pro	Commercial	`0.1.0`
`@velkin/vue-pro`	Typed Vue wrappers for Pro	Commercial	`0.1.0`
`@velkin/mcp`	MCP CLI + agent tooling (`velkin-mcp`)	MIT	`0.1.0`
`@velkin/license`	License client helpers for Pro	Commercial	`0.1.0`
`create-velkin-app`	App scaffolder (`npx create-velkin-app`)	MIT	`0.1.0`

Prefer matching versions across MIT and Pro packages in one app. Mixed lines can pull duplicate Lit copies or mismatched wrappers.

Peer requirements

Stack	Requirement
Node.js	18+
React	18 or 19 (App Router needs "use client" for onVu*)
Vue	3.x
Lit	3.x (pulled in by @velkin/ui)
Next.js	App Router + webpack via defineVelkin from @velkin/react/next

Upgrade policy

Patch / minor — additive APIs and fixes. Public props, events, and slots stay compatible within a major.
Major — may rename or remove public surface. Check Changelog and use MCP diff_component_migration before regenerating UI.
Do not invent deprecated aliases — the component docs and MCP are the source of truth after an upgrade.

How to upgrade

npm install @velkin/react@0.1.0
# or @velkin/vue / @velkin/ui — then reinstall so lockfile settles
npm install

After bumping, run your app and ask MCP diff_component_migration for any component you touch. See Migration for playbooks from other libraries and for Velkin-to-Velkin upgrades.

Next steps

Changelog — release history
Migration — coming from another UI kit or upgrading Velkin
MCP servers — diff_component_migration
Roadmap — what is shipping next

Package matrix

Package	Role	License	Line
`@velkin/ui`	MIT Lit custom elements (source of truth)	MIT	`0.1.0`
`@velkin/react`	Typed React wrappers for MIT core	MIT	`0.1.0`
`@velkin/vue`	Typed Vue wrappers for MIT core	MIT	`0.1.0`
`@velkin/ui-pro`	Pro Lit components (data table, date picker, …)	Commercial	`0.1.0`
`@velkin/react-pro`	Typed React wrappers for Pro	Commercial	`0.1.0`
`@velkin/vue-pro`	Typed Vue wrappers for Pro	Commercial	`0.1.0`
`@velkin/mcp`	MCP CLI + agent tooling (`velkin-mcp`)	MIT	`0.1.0`
`@velkin/license`	License client helpers for Pro	Commercial	`0.1.0`
`create-velkin-app`	App scaffolder (`npx create-velkin-app`)	MIT	`0.1.0`

Prefer matching versions across MIT and Pro packages in one app. Mixed lines can pull duplicate Lit copies or mismatched wrappers.

Stack

Requirement

Node.js

18+

React

18 or 19 (App Router needs "use client" for onVu*)

Vue

3.x

Lit

3.x (pulled in by @velkin/ui)

Next.js

App Router + webpack via defineVelkin from @velkin/react/next

Upgrade policy

Patch / minor — additive APIs and fixes. Public props, events, and slots stay compatible within a major.
Major — may rename or remove public surface. Check Changelog and use MCP diff_component_migration before regenerating UI.
Do not invent deprecated aliases — the component docs and MCP are the source of truth after an upgrade.

How to upgrade

npm install @velkin/react@0.1.0
# or @velkin/vue / @velkin/ui — then reinstall so lockfile settles
npm install

After bumping, run your app and ask MCP diff_component_migration for any component you touch. See Migration for playbooks from other libraries and for Velkin-to-Velkin upgrades.