On this page
  1. Supported versions
  2. What "available" means
  3. Validate your adoption
  4. Public cache composition qualification
  5. Reviewed package handoffs

Compatibility and support

The runtimes, frameworks and infrastructure versions Playstack packages target, and how to validate an adoption.

Playstack packages share one release version. The ranges below summarize compatibility targets, not evidence that every version/provider combination has been tested. Check the installed package's peer requirements and adapter-specific qualification notes before choosing a deployment stack.

Supported versions

SurfaceSupported
Node.js20, 22 and 24; new server projects should start on 22 or newer
NestJS bindings (nest-*)Nest 10 and 11
React bindings (*-react)React 18.2 and 19
Next.js bindings (*-next)Next 14.1 through 16; Cache Components need Next 16
Chakra compositionsChakra UI 3 with Emotion 11, for React DOM
Managed Prisma schema fragmentsPrisma 6.7 through 7
BullMQ queue adapterBullMQ 5.16 through 6
ESLint pluginESLint 9 and 10

Provider SDKs (Stripe, Resend, Cloudflare, push transports and others) keep their own peer ranges, listed on each integration page. A tool's own engine requirement, such as the Node version an ESLint major needs, applies alongside the Playstack range.

What "available" means

  • Available means an implementation is present in this documentation snapshot, not that registry publication or production qualification is complete. Check preview access before installing.
  • Preview means an initial composition ships with explicit limitations, typically a UI composition or a new adapter.
  • Planned means a capability has a name and a direction but no published package yet.

The status page lists every package and adapter with its current label.

Validate your adoption

Playstack packages ship the runtime code, in-memory test doubles and adapter conformance helpers you need to prove a composition in your own application. Before cutover:

  • Run the persistence conformance helper from each package's testing entry point against a disposable copy of your real database, so transaction handles, locking and rollback are exercised where they will run.
  • Keep the required adapters and registration checks on the same physical transaction as the domain calls, not merely the same transaction label.
  • Exercise provider integrations against a sandbox account. Package tests use transport doubles; your deployment's egress, DNS and TLS behavior is yours to verify.
  • Never point a mutating conformance suite at production data.

If something in this table does not match what you run, send feedback or ask on the pricing access list; compatibility gaps are prioritized ahead of new features.

Public cache composition qualification

The maintainer command npm run consumers:public-session in a Playstack checkout builds and installs an isolated package closure, checks declarations, builds Next and uses Chromium with a disposable Redis server. It exercises identical public HTML for anonymous/authenticated requests, client-side identity restoration, private no-store session endpoints, current server authorization and scoped tag/path invalidation. The repository runner is not shipped with the packages.

Its identity/account persistence is in-memory, not a qualification of an application database, production pool or native device coordinator. Run your own browser/database/provider journeys and deployed cache checks before cutover. Keep personalized responses private/no-store and product freshness/route policy explicit; a framework build or cache-adapter unit test alone does not establish those boundaries.

Reviewed package handoffs

Use a coherent fixed package train and a distinct prerelease version for a new reviewed consumer handoff. Record the source commit, exact dependency closure, archive hashes and lockfile together. Managed registry releases are immutable: changed bytes require a new committed version, not replacement of an old release.

Local Yalc iteration can replace contents under the same version label. Record each package's yalcSig and reviewed source for that local snapshot; the version alone cannot identify its bytes. playstack version --json identifies the CLI's build, not every installed package. Local signatures do not prove managed-registry publication or application acceptance. Select and prepare the next coordinated prerelease before publishing a new versioned handoff; automatic version changes are not part of installing or updating an application.

Go

Playstack Pro tag
OriginsPricingBlogChangelogStatus

© 2026 Playstack. All rights reserved.

With OSS

By

Commune Software