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

@computesdk/cloudflare

v1.6.13

Published

Cloudflare provider for ComputeSDK - edge code execution using Cloudflare Workers and Durable Objects

Readme

@computesdk/cloudflare

Cloudflare provider for ComputeSDK — execute code in secure, isolated sandboxes on Cloudflare's edge network using the official Cloudflare Sandbox bridge API.

Installation

npm install @computesdk/cloudflare

Setup

Deploy the official Cloudflare Sandbox bridge Worker by following the Cloudflare documentation:

https://developers.cloudflare.com/sandbox/bridge/

Configure the bridge Worker with an API key secret:

npx wrangler secret put SANDBOX_API_KEY

Then configure your application with the deployed bridge URL and the same API key:

CLOUDFLARE_SANDBOX_URL=https://<your-bridge-subdomain>.workers.dev
CLOUDFLARE_SANDBOX_API_KEY=<same value as SANDBOX_API_KEY>

Warm pool support is configured on the bridge Worker. Set WARM_POOL_TARGET to a positive value on the Worker to keep sandboxes warm, for example WARM_POOL_TARGET=10. Leave it at 0 to disable prewarming.

You can also run:

npx @computesdk/cloudflare

to print these setup instructions.

Quick Start

import { cloudflare } from '@computesdk/cloudflare';

const compute = cloudflare({
  sandboxUrl: process.env.CLOUDFLARE_SANDBOX_URL,
  sandboxApiKey: process.env.CLOUDFLARE_SANDBOX_API_KEY,
});

const sandbox = await compute.sandbox.create();

// Execute Python code
const result = await sandbox.runCommand(`python - <<'PY'
import sys
print(f"Python version: {sys.version}")
print("Hello from Cloudflare!")
PY`);

console.log(result.stdout);
await sandbox.destroy();

Usage

Run Commands

Use normal shell commands inside the sandbox:

await sandbox.runCommand('python -c "print(\"Hello Python\")"');
await sandbox.runCommand('node -e "console.log(\"Hello Node.js\")"');

List Files

const result = await sandbox.runCommand('ls -la /workspace/app');
console.log(result.stdout);

File System

// Write and read files
await sandbox.filesystem.writeFile('/workspace/app/config.json', JSON.stringify({ key: 'value' }));
const content = await sandbox.filesystem.readFile('/workspace/app/config.json');

// Create directories
await sandbox.filesystem.mkdir('/workspace/app/data');

// List directory contents
const files = await sandbox.filesystem.readdir('/workspace/app');

// Check existence
const exists = await sandbox.filesystem.exists('/workspace/app/config.json');

// Remove files
await sandbox.filesystem.remove('/workspace/app/temp.txt');

Port Forwarding

// Start a web server in the sandbox
await sandbox.runCommand(`python - <<'PY'
import http.server, socketserver
PORT = 3000
with socketserver.TCPServer(("", PORT), http.server.SimpleHTTPRequestHandler) as httpd:
    httpd.serve_forever()
PY`);

// Get the public URL
const url = await sandbox.getUrl({ port: 3000 });
console.log(`Service available at: ${url}`);

Environment Variables

Pass environment variables to sandbox commands at initialization:

const compute = cloudflare({
  sandboxUrl: process.env.CLOUDFLARE_SANDBOX_URL,
  sandboxApiKey: process.env.CLOUDFLARE_SANDBOX_API_KEY,
  envVars: {
    API_KEY: 'your-api-key',
    DATABASE_URL: 'postgresql://localhost:5432/mydb',
  },
});

Or per-sandbox at creation time:

const sandbox = await compute.sandbox.create({
  envs: { NODE_ENV: 'production' },
});

Configuration

interface CloudflareConfig {
  /** URL of the deployed Cloudflare Sandbox bridge Worker */
  sandboxUrl?: string;
  /** API key that matches the bridge Worker's SANDBOX_API_KEY secret */
  sandboxApiKey?: string;
  /** Deprecated compatibility alias for sandboxApiKey */
  sandboxSecret?: string;
  /** Durable Object binding (direct mode only — see below) */
  sandboxBinding?: any;
  /** Optional WarmPool configuration for direct mode */
  warmPool?: {
    /** Durable Object binding for WarmPool from @cloudflare/sandbox/bridge */
    binding: any;
    /** Number of warm containers to keep ready */
    target?: number;
    /** Pool refresh interval in milliseconds */
    refreshInterval?: number;
    /** Durable Object pool name. Defaults to global-pool. */
    poolName?: string;
  };
  /** Execution timeout in milliseconds */
  timeout?: number;
  /** Environment variables to pass to sandbox commands */
  envVars?: Record<string, string>;
}

Direct Mode

If your code already runs inside a Cloudflare Worker, you can skip the bridge Worker and use the Durable Object binding directly:

import { cloudflare } from '@computesdk/cloudflare';

const compute = cloudflare({
  sandboxBinding: env.Sandbox,
});

This requires configuring the Sandbox Durable Object binding in your wrangler.toml. See the Cloudflare Sandbox docs for setup instructions.

Direct Mode Warm Pool

Warm pool support in direct mode is opt-in. Export the WarmPool Durable Object from @cloudflare/sandbox/bridge, bind it in Wrangler, then pass it via warmPool.binding:

import { cloudflare } from '@computesdk/cloudflare';
import { Sandbox } from '@cloudflare/sandbox';
import { WarmPool } from '@cloudflare/sandbox/bridge';

export { Sandbox, WarmPool };

const compute = cloudflare({
  sandboxBinding: env.Sandbox,
  warmPool: {
    binding: env.WarmPool,
    target: 10,
    refreshInterval: 10_000,
  },
});

When warmPool is configured, ComputeSDK asks the official bridge WarmPool for an assigned container ID and then opens the sandbox through sandboxBinding. getById uses a non-allocating pool lookup and returns null when the logical sandbox ID has no existing assignment.

Error Handling

try {
  const result = await sandbox.runCommand('invalid python syntax');
} catch (error) {
  if (error.message.includes('Syntax error')) {
    console.log('Code has syntax errors');
  } else {
    console.log('Execution failed:', error.message);
  }
}

Limitations

  • Resource limits apply based on your Cloudflare plan
  • Some system calls may be restricted in the container environment
  • In remote bridge mode, filesystem paths must resolve within /workspace
  • Listing all sandboxes is not supported — use getById to reconnect to a specific sandbox ID. Remote bridge getById returns a handle without allocating or verifying the sandbox until the first operation.

License

MIT