Compatibility and upgrades

Flexkit’s framework quickstarts cover Next.js, Astro, and TanStack Start. Each application needs its framework adapter, React integration, Studio packages, extension styles, and a server-capable deployment.

Package availability

The npm registry currently identifies Studio, Desk, Asset Manager, and Explorer as 0.0.31, AI as 0.0.3, and the CLI as 0.0.10 (checked September 9, 2026).

The source version of Studio includes tools/skills exports and expanded handler and form-field contracts that are absent from npm Studio 0.0.31. The corresponding extension guides require a build containing those APIs. Installing 0.0.31 alone does not enable them; use the published release that introduces them once available. Do not work around missing exports with private source imports.

Record your release set

Keep the installed framework, React, Studio, extension, and CLI versions in your lockfile and release notes. A repository checkout version is not proof that the same package was published or deployed to your project.

Upgrade workflow

1. Review package release notes and exported type changes.
2. Upgrade in a development application with a separate test project.
3. Build the client and server routes together.
4. Verify login, deep links, data reads/writes, scoped fields, and installed extensions.
5. Check custom fields/tools against the installed public types.
6. Deploy the required schema and application changes in the intended order.

If a documented export is absent, inspect the installed package version and entry point before using private source imports as a workaround. Report a reproducible mismatch through support.

Locally validated framework builds

The shared tutorial configuration builds with Next.js 16.3.1, Astro 7.1.6 with React integration 6.0.2 and a Node adapter, and TanStack Start/Router 1.132.0 with Vite 7.1.7. These build checks use React 19.2.7 and the npm package set listed above. Authentication, schema deployment, and saved-data verification additionally require a live project.

CLI configuration loading

The tutorial separates flexkit.config.ts (schema and project configuration) from flexkit.studio.tsx (browser extensions). Keep that separation when using CLI 0.0.10: loading the AI extension through the CLI configuration can fail in its bundler with an os.platform error. The schema-only configuration remains the CLI’s default input; the application imports the Studio configuration.