Component registry CLI
npx fabkit add gantt-pmo
Copies a component into your app as source you own, the way shadcn/ui does it. No runtime dependency, no version lock, edit it freely.
MIT · not released yet
Building the templates in this gallery produced a set of parts: charts that know the shape of Fabric app data, loaders that land a SaaS API in Fabric SQL, and the glue for writeback. fabkit is those parts, extracted, documented and published on their own so you can build a Fabric app without starting from a blank Vite project.
npx fabkit add gantt-pmoEach one can be used on its own. The registry is the piece everything else arrives through.
npx fabkit add gantt-pmo
Copies a component into your app as source you own, the way shadcn/ui does it. No runtime dependency, no version lock, edit it freely.
Gantt · burn-up · beeswarm · health matrix · milestone rail
D3 charts built for Fabric app data shapes, each with its own sample fixture so the component renders before your data is wired.
Source API to Fabric SQL, on a schedule
Typed extract-and-land helpers for the SaaS APIs these templates read from, with incremental loads and a shared table convention.
Component to translytical task flow
Emits the User Data Function and the Power BI button binding for a writeback component, so the same action works from a report as well as from the app.
This page exists so you can decide whether to wait for it. It is not a product page.
There is no published package. `npx fabkit` does nothing today.
The repository is not public yet, so there is no code to read and no issues to file.
No date is promised. It opens when the first two templates are stable enough that the shared parts have stopped moving.
It will contain the GitHub link, the registry index, and a short note on what is stable enough to build against. If you want a specific component in the first release, say so in a reply.