Core packages
The runtime, React bindings, framework adapters and tools used to build BitaKit apps.
Start with the minimal app, then choose the capabilities you need. For ready-made app features, see Plugins. For authentication, translation and email, see Integrations.
These guides describe the 0.2 API in this checkout. Use matching package versions; the
local package setup lets you try unpublished changes.
All package names below use the @bitakit/ prefix.
Runtime and tooling
These packages support the app and its plugins; they are not all installable app features.
| Package | Responsibility |
|---|---|
core | Framework-independent runtime, Actions and typed service registration |
ui | React bindings and optional standard themed components |
packages | Trusted catalog loading and active package selection through the existing runtime |
discovery | File conventions, package discovery and generated app composition |
cli | Scaffolding, inspection, migration and plugin package builds |
create-app | Frontend project generator |
Framework adapters
BitaKit sits on top of your framework through one adapter. The adapter runs discovery with the build, mounts the generated provider and renders plugin pages from one catch-all route.
| Adapter | Framework | Status |
|---|---|---|
next | Next.js App Router | Supported |
tanstack | TanStack Start and Router | Experimental |
Framework ownership
Choose the integration matching the router that manages your BitaKit surface. The integration uses the application's router through peer dependencies; installing a second router does not switch it automatically. App-owned routes remain native framework routes.
Runtime management
The Plugin manager handles loaded feature definitions. The Package manager adds trusted catalog loading and selection. Their guides describe the APIs and current limits.
To learn the underlying conventions, follow Build your first feature. The To-do walkthrough combines them in runnable code.