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

@belgie/render

v0.39.0

Published

Self-contained inline React widget rendering for Belgie run_code tools.

Readme

@belgie/render

@belgie/render returns a render request from agent run_code Scripts. BelgieRuntimeSession (and the Pydantic AI / LangChain toolsets) complete that request on a Belgie-owned renderer side-channel and return one self-contained HTML document. Model-visible Scripts stay workspace-restricted: they do not receive host /etc//proc, allow_sys, or allow_ffi, even when inline rendering is available. The renderer uses workspace-scoped read/write/FFI and limited allow_sys for Vite native loaders — not host path grants.

import { render } from "npm:@belgie/render";

function Widget() {
  return <main>Hello from Belgie</main>;
}

export default function run() {
  return render({
    widget: <Widget />,
    plugins: [],
  });
}

The source must be a single inline TSX module. Package imports are supported. Relative imports are unsupported for the browser widget graph; server plugins may import workspace modules, resolved like Deno from the inline module URL (__deno_python_inline__.tsx in the Environment workspace).

plugins run only during the server-side Vite build on the privileged renderer. Script-side plugins expressions still evaluate under workspace-only permissions and are discarded; the privileged rebuild from source evaluates the plugin expression again. Plugin factories, hooks, and their imports therefore run with the renderer's broader permissions. Treat plugins as reviewed application code and use plugins: [] for untrusted agents. Prefer pure factories or relative workspace plugin modules when construction must succeed in the restricted Script. Both plugins and widget must appear in a statically analyzable render(...) options object (inline literal, variable binding, or static object spread). Computed option keys, opaque spreads, and post-declaration mutation are unsupported and throw instead of shipping unsafe code to the browser. The browser mounts the extracted widget expression and does not re-execute run(), so side effects inside run() stay server-only. Widget expressions may only reference module-level bindings.

Hosts that manage their own Runtime (without BelgieRuntimeSession) should call buildFromSource from @belgie/render/host on a worker with workspace FFI/sys grants; importing that entry from a restricted Script would reintroduce Vite's native grants into the model-visible session.