The Poyo project CLI, client runtime, and C# server core: route management, build glue, OpenAPI-to-TypeScript codegen, the usePage server-data accessor, and the registry-backed server framework.
The most powerful and lightweight API that allows you to develop your original Haxball(www.haxball.com) host, client, and standalone applications both on node.js and browser environments and also includes every possible hack and functionality that you can
Earth binding for Molen worldgen: terrain-semantics adapter, OSM label mapping, and lon/lat region atlas (kernel) with terrain tile renderers (client)
Auth-agnostic CMS runtime for React projects. It provides page models, a transport-driven client, a React provider, hooks, and a registry renderer.
ChainRender client SDK — headless, AST-first core: compile, grade, construct, describe, validate, and the machine-readable vocabulary. The foundation the visual builder, MCP server, and AI assistant sit on.
React client for the owizzo Dynamic Engine: renders server-described forms and tables with Ozora components.
Chat Conversation target, node definitions, renderers, and details surface
Authup's hosted login, consent, registration, password recovery and device pages, as a server-rendered Vue bundle.
Shared transactional-email building blocks (feature 047). Pure, React-free render/* + directives/* + tree/* + schema/* + defaults/* are imported by the backend to render email-client-safe HTML and plain text; the React components/* + config.ts power the a
Host-injected PDF worker client and browser rendering runtime
Vue 3 + TypeScript HTML-to-PDF component and composable with selectable text, Canvas rendering, smart pagination, headers, footers and watermarks. Nuxt 3/4 SSR-safe imports; browser-side PDF generation.
Render-independent scientific service clients for astronomy, Earth observation and planetary data.
The BetterCMS adapter for Astro — a `bettercms()` integration, a `bettercms:client` virtual module, typed content loaders, draft preview, and native .astro rendering components.
Client-side rendering support for pdfn - enables Recharts and other client components in PDFs
React components for the Lew Design System: the markup of @lew-ds/lds's templates as JSX, server-rendered with every slot in the HTML. Stateless components are server components; only the five stateful ones are client components.
configuring once, rendering both client and server.
A reserved, intentionally empty slot in the OwlMeans white-label stack. It holds the place of a platform-neutral client layer — the tier between the shared white-label contract and a rendering target such as the browser — but today its entry point (`src/i
Browser SDK for Grant authorization - React hooks and components for permission-based UI rendering
Docking layout kit: split-tree engine with invertible operations, and the React components that render and drive it (zero cordis)
Drive a running AtomCut editor from Claude Code, Claude Desktop, Cursor or any MCP client — every editor verb as a tool, renders as images, the AtomCut skill as resources.
Headless React pair for stapel-listings: a typed client over the draft twin, the composer that turns a category schema into a submittable listing, and the owner's dashboard. Two independent axes are rendered as two — lifecycle `status` decides visibility
Net Forge game engine client: a typed declarative game API and a three.js WebGPU/WebGL2 renderer for multiplayer browser games.
Interface for XM Plugins to communicate with the environment they're rendered in
Client SDK for the AccountGroove Content API: render a tenant's published blog on their own Astro/Next site with their own markup, classes and components.
The Konneal publisher-site contract: engine API types, the SSE ask client, and the answer-contract renderers (citation chips, typed unit blocks, formulas, the in-context document pane) Ships the konneal CLI (ask, search, keys) for humans and operators.
Zero-framework render adapter for @nifrajs/web - auto-escaping tagged-template HTML, ~0 KB client JS, interactivity via @nifrajs/web/islands.
Client-side HTML-to-PDF rendering using pure JS
A minimalist template engine for DOM generation and manipulation, working for both client-side and server-side rendering
Slot registry pure core: typed ordinary Slots and reusable Component Factories, derived props, Store seats, and renderer installation
The pure half of the AirPrompter agent SDK: the protocol (types, trust chain, canonical JSON, arm assignment and the ramp walk), rendering, output checks, golden sets, the judge, bundle reading, telemetry row schemas, the control-plane client, and the por
MCP server for rendering DGMO diagrams — SVG/PNG output, browser preview, HTML reports, and 50+ chart types. Works with Claude Desktop, Claude Code, and any MCP client.
The cueloop review UI: projection renderer, keyboard grammar, review rail
The client for the ebitex Content Delivery API: typed endpoints, React rendering, sitemaps, live preview and locale addressing, so a site does not maintain its own.
Customy browser client: session, sign-in, MFA, passkeys, active organization, capabilities and account linking over same-origin HttpOnly cookies, with React, native and native React bindings and the brand-studio screen renderer (studio, studio/react) as s
Framework-agnostic Client Compose client: island registry, screen requests and render planning.
Renders nested React components with asynchronous cached loading; useful for GraphQL clients and server side rendering.
Loads the PayPal JS SDK with your client id and currency, renders PayPal Buttons for a fixed order total, captures payment on approval, and dispatches paymentCompleted when the order is captured successfully.
React renderer for MDX components — implements the @blogmcp/mdx-schema contract alongside @blogmcp/mdx-render-vue. Server-Component-first with client islands (Tooltip, AudioPlayer).
The plugin author's kit: snapRail manifest vocabulary, the renderer seed whitelist, tsdown presets for installable host + client faces, release signing, and the final-format packer
Reeve CRM operator contact UI (DEV-18032): ContactCard and CustomerThread, the cross-channel customer conversation (web chat, SMS, email, phone calls with duration and summary), rendered from an injected client against the contact-interactions read contra
Carbon codama renderer for Codama IDL
Client-Side Page Rendering and Execution Framework
DSH client plugin: reverses the conversation reading layout — the composer pins to the TOP of an active conversation (centered on a new one) and the transcript plus turn navigator render newest-first, so replies appear right under the composer.