Retired Compat
Legacy TypeScript website content. Shared public website, blog, protocol, guide, and language-neutral docs ownership now lives in
~/src/graphreflyunder D563. This page is retained here only as migration/reference material while the TS API generator still lives inwebsite/.
The old @graphrefly/graphrefly/compat/* runtime model is retired. Framework and host bindings now live in one-way ecosystem packages over @graphrefly/ts.
Current replacements
Section titled “Current replacements”- NestJS structural metadata:
@graphrefly/nestjskeyed ingress/egress boundary nodes plus decorators over existing graph nodes. - NestJS HTTP/native providers:
@graphrefly/nestjs/nativeexplicit D494 provider bundles for interceptor, guard, filter, cron, and lifecycle phases. - NestJS WebSocket/message providers:
@graphrefly/nestjs/websocketsand@graphrefly/nestjs/microservicesfocused D495 provider bundles over the existing D488 bridges. - React/Vue/Solid/Svelte:
@graphrefly/react,@graphrefly/vue,@graphrefly/solid, and@graphrefly/svelte. - Jotai/Nanostores/Zustand-style facades: small store facades from
@graphrefly/ts/adapters.
See the full walkthrough in NestJS Integration.
What stayed retired
Section titled “What stayed retired”Do not use compat/nestjs, GraphReflyModule, GraphReflyGuard, Actor, CqrsGraph, hidden event buses, root @graphrefly/graphrefly imports, container scanning, hidden graph creation, or transport retry/session/reconnect ownership for current work.
Adapter diagnostics are not a callback or logging API. Use host-side diagnostics() snapshots for local bridge state, or wire fromNestDiagnostics(...) explicitly when diagnostics should become sanitized graph DATA.