npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@fuaran-ui/renderer-server

v0.6.0

Published

Server-HTML renderer for the Fuaran UI typed Node tree — a pure-string renderer (no React, no DOM) that walks a tree and emits the reference fuaran-* class vocabulary for a first paint + crawlable, no-JavaScript page. The TypeScript twin of Fuaran.UI.Rend

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ajwillshireajwillshire

Keywords

fuaranuiaissrserver-renderinghtmlhydration

Readme

@fuaran-ui/renderer-server

Server-HTML renderer for the Fuaran UI typed Node tree — the TypeScript twin of the F# Fuaran.UI.Renderer.Server tier.

A pure-string renderer — no React, no DOM. It walks a typed tree and emits a body-fragment HTML string carrying the reference fuaran-* class vocabulary, so a non-React Node/edge server can render Fuaran chrome end-to-end for a fast first paint, a crawlable / no-JavaScript page, and an isomorphic-hydration handoff to @fuaran-ui/renderer on the client. The emitted class + node-id vocabulary is parity-locked to both the React client renderer and the F# reference renderer (see test/parity.test.tsx).

Install

npm install @fuaran-ui/renderer-server

@fuaran-ui/schema and @fuaran-ui/renderer are peer dependencies (the latter only for its React-free /sanitize subpath + the packaged reference CSS). react / react-dom are not required at runtime.

Server semantics

Mirroring the F# SSR precedent — render the tree inert, never blank:

  • Interactivity renders inert. A Button is a real <button>, dead until hydration; no event handlers are emitted.
  • A Link is a real, sanitised <a href> — the crawlable, no-JavaScript navigation path.
  • Bindings resolve server-side. Static bindings resolve to their value; Query / Filter / Selection / … resolve from host-supplied sources or fall back to the loading slot / em-dash placeholder.
  • Client-library visualisations render a deterministic placeholder (Chart / Map), never a blank; Table / Grid render structural HTML.
  • Custom renders the inert labelled placeholder the client emits when no renderer is registered.

Usage

import { renderToHtml } from '@fuaran-ui/renderer-server';
import { decodeNode } from '@fuaran-ui/ops';

const decoded = decodeNode(wireJson);
if (!decoded.ok) throw new Error('bad tree');

const bodyFragment = renderToHtml(decoded.value, {
  sources: { queryResults: { totalRevenue: 42 } },
});

// The host owns the document shell + the <link> to the packaged reference CSS:
const page = `<!doctype html><html><head>
  <link rel="stylesheet" href="/fuaran.css">
</head><body><div id="app">${bodyFragment}</div></body></html>`;

Serve the packaged reference stylesheet from @fuaran-ui/renderer/css (the same artefact the client renderer ships), so the server-rendered fragment and the hydrated client render byte-for-byte identical chrome.

Hydration

Because the emitted class names + data-fuaran-node-id attributes match what @fuaran-ui/renderer produces, a server-rendered fragment can be handed to the client renderer's hydrate / hydrateEmbedded entry points (@fuaran-ui/renderer) — the React reconciler attaches in place rather than re-rendering.

Parity

The package carries a render-parity corpus (the rendering analogue of the wire-format corpus). Over the whole node fixture set it asserts the server renderer emits the same fuaran-* class set and data-fuaran-node-id set as the React client renderer, and that every emitted class is in the F# reference renderer's vocabulary. A drift in either direction is a build failure. The StyleObservation /class shapes are declared stable in STABILITY.md.

Apache-2.0.