zedkit

Maturity and compatibility

What catalog badges mean, live maturity counts, and per-package Node and peer dependency requirements.

Hand-written shell; counts and the compatibility table are generated on every pnpm docs:generate.

Every catalog need carries a maturity badge. Criteria for planned, alpha, beta, stable, and deprecated are defined once in the catalog README (Maturity) — read that section instead of a copy here.

Breaking changes ship through changesets and semver (0.x today). Check each package CHANGELOG.md before upgrading.

Current catalog counts

StatusCatalog needs
alpha13
beta43

Workspace toolchain

Node >=22, pnpm@9.15.9. UI work expects React 19 and Tailwind CSS v4 (see theme doc).

Package compatibility

Generated from each package package.json on every docs build.

PackageVersionNodePeer dependencies
@zedtech/zedkit-ai0.5.0>=22—
@zedtech/zedkit-core0.1.2>=22—
@zedtech/zedkit-nest0.1.2>=22@fastify/static ^10.1.7; @nestjs/common ^12.2.0; @nestjs/config ^12.0.1; @nestjs/core ^12.2.0; @nestjs/platform-fastify ^12.2.0; @nestjs/swagger ^12.0.4; @nestjs/throttler ^6.7.1; class-transformer ^0.5.1; class-validator ^0.15.1; fastify ^5.12.7; nestjs-pino ^5.3.1; pino ^10.4.0; pino-http ^11.0.0; reflect-metadata ^0.2.2
@zedtech/zedkit-payload-seo0.1.2>=22payload 3.92.0
@zedtech/zedkit-seo0.1.3>=22—
@zedtech/zedkit-server0.1.2>=22—
@zedtech/zedkit-ui0.4.0>=22react 19.3.1; react-dom 19.3.1; tailwindcss 4.3.3

Next steps

On this page