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

renderify

v0.6.0

Published

Official Renderify SDK facade

Readme

renderify

Node CI npm license

Official Renderify SDK entry package.

renderify is the recommended top-level package for application developers. It provides:

  • A batteries-included app factory (createRenderify / startRenderify)
  • One-shot helpers (renderPromptOnce, renderPlanOnce)
  • Re-exports from @renderify/core
  • Provider/runtime helpers from @renderify/llm and @renderify/runtime

Install

pnpm add renderify
# or
npm i renderify

Quick Start

import { startRenderify } from "renderify";

const { app } = await startRenderify({
  llmProvider: "openai",
  llmProviderOptions: {
    apiKey: process.env.RENDERIFY_LLM_API_KEY,
  },
});

const result = await app.renderPrompt("build a KPI dashboard");
console.log(result.html);

await app.stop();

Renderer-only (BYO LLM/Backend)

You do not need to use the built-in LLM providers. A common integration is to generate RuntimePlan externally and only use renderify for execution/rendering:

import { renderPlanInBrowser, renderPlanOnce } from "renderify";

const plan = {
  specVersion: "runtime-plan/v1",
  id: "renderer_only",
  version: 1,
  root: {
    type: "element",
    tag: "section",
    children: [{ type: "text", value: "Hello from external plan" }],
  },
  capabilities: { domWrite: true },
};

// Browser mount
await renderPlanInBrowser(plan, { target: "#app" });

// Optional one-shot execution in app orchestration flow
const result = await renderPlanOnce(plan);
console.log(result.html);

Renderer-only TSX + Dependency Package (JSPM)

renderPlanInBrowser defaults to auto-pin-latest, so bare imports work out of the box:

import { renderPlanInBrowser } from "renderify";

const tsxPlan = {
  specVersion: "runtime-plan/v1",
  id: "renderer_only_tsx_datefns",
  version: 1,
  capabilities: { domWrite: true },
  root: {
    type: "element",
    tag: "div",
    children: [{ type: "text", value: "Loading..." }],
  },
  source: {
    language: "tsx",
    runtime: "renderify",
    code: `
      import { format } from "date-fns/format";

      export default function App() {
        return <section>Today: {format(new Date(), "yyyy-MM-dd")}</section>;
      }
    `,
  },
};

await renderPlanInBrowser(tsxPlan, { target: "#app" });

For production determinism, prefer manifest-only (explicit pinned versions) and disable auto-pin:

const pinnedPlan = {
  ...tsxPlan,
  moduleManifest: {
    "date-fns/format": {
      resolvedUrl: "https://ga.jspm.io/npm:[email protected]/format.js",
      version: "4.1.0",
    },
  },
};

await renderPlanInBrowser(pinnedPlan, {
  target: "#app",
  autoPinLatestModuleManifest: false,
});

Auto-pin-latest workflow (renderPlanInBrowser default):

  1. Write bare imports for DX, for example import { format } from "date-fns/format".
  2. On first run, Renderify resolves the bare specifier via JSPM latest metadata.
  3. Renderify immediately pins and injects the exact resolved URL/version into moduleManifest, then executes with pinned resolution.

Use manifest-only in production (autoPinLatestModuleManifest: false) when you want fully pre-pinned, reviewable dependency mappings.

One-shot Prompt Rendering

import { renderPromptOnce } from "renderify";

const result = await renderPromptOnce("build a todo list", {
  llmProvider: "openai",
  llmProviderOptions: {
    apiKey: process.env.RENDERIFY_LLM_API_KEY,
  },
});

console.log(result.plan);
console.log(result.html);

Main Exports

  • createRenderify(options)
  • startRenderify(options)
  • renderPromptOnce(prompt, options)
  • renderPlanOnce(plan, options)
  • renderPlanInBrowser(plan, options)
  • LLM registry/provider exports (createLLMInterpreter, LLMProviderRegistry, ...)
  • Full @renderify/core API surface

Notes

  • Default browser embedding behavior is auto-pin-latest for bare source imports; use manifest-only for production-grade deterministic deployments.
  • Node.js >=22 is required.
  • For advanced split-package usage, you can still import @renderify/core, @renderify/runtime, @renderify/security, @renderify/llm, and @renderify/ir directly.