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

@bthn/codemode-local-executor

v0.1.1

Published

Local vm2-based executor for @cloudflare/codemode — runs LLM-generated TypeScript in an isolated sandbox

Downloads

149

Readme

@bthn/codemode-local-executor

Local vm2-based executor for @cloudflare/codemode.

@cloudflare/codemode lets LLMs write executable TypeScript instead of making individual tool calls. It ships with DynamicWorkerExecutor which runs code inside a Cloudflare Worker — this package provides a drop-in replacement that runs the same code locally using Node.js vm2, so you can use codemode in any Node environment without a Workers deployment.

Installation

npm install @bthn/codemode-local-executor @cloudflare/codemode agents ai zod

Usage

Replace DynamicWorkerExecutor with NodeVMExecutor and everything else stays the same:

import { createCodeTool } from "@cloudflare/codemode/ai";
import { NodeVMExecutor } from "@bthn/codemode-local-executor";
import { streamText, tool } from "ai";
import { z } from "zod";

const tools = {
  getWeather: tool({
    description: "Get weather for a location",
    inputSchema: z.object({ location: z.string() }),
    execute: async ({ location }) => `Weather in ${location}: 72°F, sunny`,
  }),
  sendEmail: tool({
    description: "Send an email",
    inputSchema: z.object({
      to: z.string(),
      subject: z.string(),
      body: z.string(),
    }),
    execute: async ({ to, subject, body }) => `Email sent to ${to}`,
  }),
};

const executor = new NodeVMExecutor({
  env: {
    SOME_API_KEY: process.env.SOME_API_KEY ?? "",
  },
});

const codemode = createCodeTool({ tools, executor });

const result = streamText({
  model,
  system: "You are a helpful assistant.",
  messages,
  tools: { codemode },
});

Constructor options

new NodeVMExecutor(options?: NodeVMExecutorOptions)

| Option | Type | Default | Description | |--------|------|---------|-------------| | env | Record<string, string> | {} | Environment variables exposed inside the sandbox as process.env.* | | compiler | 'typescript' \| 'coffeescript' \| 'javascript' | 'typescript' | Compiler used to transpile the LLM-generated code before execution | | allowEval | boolean | false | Whether to allow eval() inside the sandbox | | allowWasm | boolean | false | Whether to allow WebAssembly inside the sandbox | | logCode | boolean | true | Log the generated code to stdout before executing (useful for debugging) |

How it works

  1. createCodeTool generates TypeScript type definitions from your tools and builds a description the LLM can read.
  2. The LLM writes an async arrow function that calls codemode.toolName(args).
  3. NodeVMExecutor receives the code string and spins up a fresh NodeVM instance, injects the tool functions as codemode.*, and runs the snippet.
  4. The result (or error) is returned as ExecuteResult — the executor never throws.

Security

vm2 provides V8-level isolation. The sandbox:

  • Cannot access process.env beyond what you explicitly pass in env
  • Cannot use eval or WebAssembly by default
  • Console output is intercepted and returned in logs, not forwarded to host stdout

Note: vm2 is a best-effort sandbox. Do not use this to run untrusted code in production without additional hardening.

License

MIT