Granularity
⌘K
v0.41.0

Roadmap

No dates. With a single maintainer they do not hold, and a missed date costs more trust than a missing one. What follows is what has to happen, and in what order.

In flight

No package has an open Unreleased section at the pinned tag v0.41.0. That does not mean work has stopped: the section appears when a change is written but not yet released.

Released

The latest releases across the family. Full logs are one link away from each.

All changelogs

What has to exist by 1.0

No date is set, and this portal will not invent one. The conditions, however, are written down in the project specification:

  1. A migration guide with a map of API changes and a codemod for renames — written before the release, not after it.Migration
  2. A version support policy: how long a major is supported and what «supported» means in practice.Versioning
  3. Versioned documentation: the current tree frozen under an archive prefix, with canonical links to the live pages.Versioning
  4. A since field on every component and a deprecated marker with a replacement — both filled from the first day rather than reconstructed afterwards.Components

Until that exists the version stays in the 0.x line, and breaking changes live in the changelogs — with the reason spelled out rather than a line saying «breaking».

Not planned

The most useful section: it answers once what otherwise gets asked in every thread.

RTL support
Components are laid out with physical directions, and moving to logical properties changes how every one of them looks. That is a visual breaking change and belongs to a major, not to a patch.Accessibility
Splitting the core into sub-packages
Most edges of the dependency graph cross the boundaries of the catalogue groups, so the split would produce packages depending on each other in a ring — and the granularity it promises already exists per subpath.Architecture
Vue 2
The package declares Vue 3.5 as a peer dependency and is built on the composition API and <script setup> throughout. Supporting Vue 2 would mean a second library, not a compatibility flag.Installation

Under discussion

Proposals and voting live in the repository discussions. A «next» section will appear here when decisions are made, and not before.

Discussions on GitHub