Upgrade guide

How versions work

Alea follows semantic versioning. Before 1.0, a minor version (0.1 to 0.2) may change an API and says so here; a patch version never does. From 1.0 on, changes that need your attention come only in a new major version, with this page updated first. Deprecated props keep working for one major version and warn in development.

The three packages share one version number and move together: @alea/ui, @alea/motion and @alea/tokens. Alea Pro pins the exact version of @alea/ui it was built against, so update all of them in one go.

Updating the packages

1. 1

   See what changed

   The changelog lists every release; the entries that need attention are marked and repeated on this page.

   npm outdated @alea/ui @alea/motion @alea/tokens @alea/pro

2. 2

   Update together

   One command for the free packages; add @alea/pro if you have it. Same version for all.

   npm install @alea/ui@latest @alea/motion@latest @alea/tokens@latest

3. 3

   Run your checks

   Type errors point at the props that changed. Nothing changes silently: a removed prop is a compile error, not a different look.

   npx tsc --noEmit

Sources copied with the CLI

Components added with the CLI are your files: an update never touches them. To take a new version of a component, add it again; the CLI writes the new source next to yours as <name>.new.tsx when the file has changed since it was copied, so you can compare and merge with your own edits.

npx @alea/cli add button --update

Changes by version

Full list of changes: Changelog