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-browser-sandbox

v0.1.3

Published

Build Vite-style project files in the browser and get a Blob URL for iframe loading

Readme

ai-browser-sandbox

Preview AI-generated code in the browser. Pass in-memory project files (e.g. from an AI that generated React or Vanilla HTML/JS), get a Blob URL to load in an <iframe>—no server, no Node, no local build. Built for quickly rendering and iterating on generated Vite-style projects.

  • In-memory: files is Record<path, content>. Dependencies and HTML come from your project (package.json, index.html).
  • Browser-only: Uses esbuild-wasm; runs entirely in the client.

Install

npm install ai-browser-sandbox

Usage

When you have project files as strings (e.g. from an AI or editor), pass them to buildSandbox and show the result in an iframe:

import { buildSandbox } from "ai-browser-sandbox";

// e.g. files from AI-generated project
const { url, error } = await buildSandbox({
  files: {
    "package.json":
      '{"dependencies":{"react":"^18.0.0","react-dom":"^18.0.0"}}',
    "index.html":
      '<!DOCTYPE html><html><body><div id="root"></div></body></html>',
    "src/main.tsx":
      "import React from 'react'; import { createRoot } from 'react-dom/client'; import App from './App'; createRoot(document.getElementById('root')).render(<App />);",
    "src/App.tsx":
      "import React from 'react'; export default function App() { return <h1>Hello</h1>; }",
  },
  framework: "react",
});

if (error) {
  console.error(error); // human-readable message
  return;
}
document.querySelector("iframe").src = url;
  • Result: { url: string, error?: string }. On failure, error is set with a human-readable message; url is empty. No throwing.
  • Import map: Built from your package.json (dependencies + devDependencies). All listed packages are loaded from esm.sh at runtime.
  • HTML: Your index.html is used as the page template (when present). The bundle (or inline script) is injected where the module script was.

Supported frameworks

  • react — Entry: src/main.jsx, src/main.tsx, main.jsx, etc. Uses your index.html and package.json.
  • vanilla — Entry: index.html only. Optional <script type="module" src="..."> for an external JS file, or inline script only (single HTML file, no JS file).

Running the example

From the repo root:

npm run example

Open http://localhost:3000/. Choose Framework (React or Vanilla), select your project folder or individual files, then click Build. Only source files (.js, .jsx, .ts, .tsx, .html, .json, .css) are used; node_modules, .git, dist, etc. are ignored.

Requirements

  • Runs in the browser only (no Node).
  • Uses esbuild-wasm for bundling. The first build loads the WASM binary from a CDN (unpkg).

Adding frameworks

Implement the FrameworkAdapter interface and add an adapter under src/frameworks/adapters/, then register it in src/frameworks/registry.ts. See src/frameworks/adapters/react.ts and vanilla.ts for examples.

Contributing

See CONTRIBUTING.md for development setup and how to contribute.

Author

Built by Saurabh.

License

MIT