React SDK

The React SDK is the rendered half of the platform. Python ships schema and operations; TypeScript ships UX. Their only seam is the typed contract the composer emits — there is no hand-written API client.

The frontend surface is split by owner:

• @angee/refine — the metadata-free Refine/Hasura data, transport, live, router, and dialect binding.
• @angee/metadata — the angee.resources artifact loader and its Refine projection.
• @angee/ui — the rendered views, chrome, widgets, primitives, and runtime contracts they consume.
• @angee/app — addon composition, providers, routing, registries, and the app shell.

An addon with UI ships a co-located web package (for example @angee/storage) that contributes routes, views, widgets, menus, and translations through defineBaseAddon; the host composes them with createApp.

Start here

• Frontend Guidelines — the rules: one component tree, additive slots, token-first theming, and the server as the authorization boundary.

Across the platform

• The Opinionated Stack — the frontend libraries and the rendered binding, and what each one owns (React 19, Refine, TanStack, Base UI, …).
• Concepts & Glossary — defineAddon, createApp, slots, tokens, the rendered binding.
• End-to-End Testing — how the composed Vite/React SPA is driven against the running backend with Playwright.

The backend that emits the contract this SDK consumes lives under Django framework.