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

@agent-wasm/core

v0.4.0

Published

Node.js in your browser. Just like that.

Readme

@agent-wasm/core

Node.js in your browser. Just like that.

The core runtime behind agent-wasm: a browser-native Node.js environment with an in-memory filesystem, a real npm package manager (downloaded + ESM→CJS transformed via esbuild-wasm), HTTP servers intercepted through a service worker, and dev servers for Vite and Next.js.

npm install @agent-wasm/core
import { createContainer } from "@agent-wasm/core";

const container = createContainer();
container.vfs.writeFileSync("/index.js", "console.log('hello from the browser')");
await container.run("node index.js");

What's in the box

  • VirtualFS — in-memory filesystem, exposed to code as require('fs').
  • Runtime / createRuntime / WorkerRuntime / SandboxRuntime — the JS execution engine with require(), ESM→CJS transforms, and 43 built-in module shims (fs, path, http, net, stream, crypto, child_process, …).
  • PackageManager — installs real npm packages, served via /_npm/.
  • ViteDevServer / NextDevServer — React + HMR, Next Pages + App Router.
  • electron shim + setElectronHost / launchElectronApp — emulate the Electron main process (app, BrowserWindow, ipcMain) and run modern (contextIsolation + preload) Electron apps from source; each BrowserWindow renders as a host-supplied iframe with postMessage IPC. See examples/electron-demo.*.
  • createContainer / ContainerInstance — orchestration: vfs, workspace, git, terminal sessions.
  • ServerBridge — service-worker network interception for in-VFS servers.
  • network — Tailscale-backed networking namespace.

Subpaths

| Import | Purpose | | --- | --- | | @agent-wasm/core | the runtime API above | | @agent-wasm/core/internal | internal helpers (OXC linter, Fly/Infisical, auth shims) | | @agent-wasm/core/vite | almostnodePlugin() — serve the service worker in dev | | @agent-wasm/core/next | getServiceWorkerContent() / getServiceWorkerPath() |

License

MIT