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

@ai-matrx/code-runtime

v0.4.88

Published

The AI Matrx in-frame code runtime: compiles stored multi-file TSX (Applets, kind components, tool and emit renderers, code blocks) against one documented import scope, with named stand-ins for anything unresolved, the one source-gate list, and a compile

Readme

@ai-matrx/code-runtime

Compile stored TSX — one file or many — into a React component, against one documented import scope, with a visible, reported stand-in for anything the scope cannot supply.

import { compile, gate } from "@ai-matrx/code-runtime";

const files = {
  "App.tsx": `import { Form } from "./Form"; export default () => <Form />;`,
  "Form.tsx": `import { Button } from "@ai-matrx/design-system/controls";
               export const Form = () => <Button>Save</Button>;`,
};
if (gate(files).some((f) => f.severity === "refuse")) throw new Error("refused");
const r = compile(files, "App.tsx", { entries: ["react", "@ai-matrx/design-system/controls"], shadowDangerousGlobals: true });
if (r.ok) render(<r.Component />); else show(r.error.message);
  • Scope: listScopeEntries() is the whole registry. Package-owned entries work anywhere (Next.js, Vite). Host-owned ones (Markdown, kind-kit, copy buttons, Applet parts, heavy libraries) are supplied once: provideScopeModules({ "@/components/MarkdownStream": () => mod }). Async entries (recharts) need await prepareScope(spec) or compileAsync. A documented library a body imports always enters its scope; await prepareSource(code) / prepareGraph(graph) (or poll pendingEntriesFor(code)) before a synchronous compile so it is loaded.
  • Sandbox split: the parent runs @ai-matrx/code-runtime/transform (transformFiles) and posts the JSON graph; the frame runs @ai-matrx/code-runtime/execute (executeGraph), no Babel.
  • Gate: @ai-matrx/code-runtime/gate is pure (servers, write paths). The lists ship as @ai-matrx/code-runtime/gate-lists.json.
  • Kinds: inject kindComponentCompiler() into @ai-matrx/content-ir/react's createDbKindComponentCache({ compile }).

Not a security boundary: the dangerous-global stubs shadow bare identifiers only. Isolation is the sandbox frame.