Ecosystem
The core and its companion packages. A companion appears when a component must not live in the core: it pulls a heavy dependency, or it simply is not core material. Every package has its own release cycle and its own page.
- 12
- packages
- 116
- components
- 276
- public subpaths
- 10
- packages with zero runtime dependencies
With components8
The core first, then the companions that carry components of their own.
granularityThe core: everything an interface is assembled from — buttons, fields, tables, overlays. Zero runtime dependencies, and every component is importable by its own subpath.granularity-chartsCharts drawn with the same theme tokens as the rest of the interface, in own SVG. Take it when a chart has to match the interface rather than a charting library.granularity-chronoCalendar, date and time pickers without a date library underneath. Take it when dates are part of the interface and a third-party widget would bring its own visual language.granularity-codeCode on the page: viewing, editing and diff. The viewer and the diff carry no dependencies at all; the editor asks for CodeMirror only if you take the editor.granularity-dashboardA widget grid with drag, resize, breakpoints and saved layout. Take it when the user owns the layout, not the designer.granularity-editorRich text as a design-system field: a TipTap-backed editor with the toolbar and the states of the rest of the form.granularity-forms-schemaForms from a schema: zod or JSON Schema turned into real fields with validation and layout. Take it when the form is data rather than markup.granularity-mediaWorking with media: image cropping, camera capture, code scanning, video playback — the parts an application usually pulls four separate libraries for.
Without components4
A composable, a devtools panel, test factories and an auto-import resolver: they ship no markup.
granularity-datasourceList state behind one composable: sorting, filters, paging, URL sync and race-free fetching. No components — it is the logic that a table and its filter panel share.granularity-devtoolsA Vue DevTools panel: where a prop value came from, what the overlay stack looks like and which design-system rules the application breaks. Development only.granularity-test-kitThe contract tests every package of the family owes, as reusable factories. Useful to whoever writes a companion package, not to the application.unplugin-granularityA resolver for unplugin-vue-components: components auto-import by their own subpath, so what the application never used never reaches the bundle.
Nothing here matches. Try the search for the whole site — ⌘K.
What is shown, and as of when
The composition is taken from the submodule pinned to core tag v1.1.1. Right now every published version matches it.
Why the core is not split into packagesChangelogs of every packageHow a companion package is built — the library guide