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/fly

v1.1.10

Published

Fly.io provider for ComputeSDK - globally distributed sandboxes using Fly Machines

Readme

@computesdk/fly

Fly.io provider for ComputeSDK that enables creating and managing containerized sandboxes on Fly.io infrastructure.

Installation

npm install @computesdk/fly

Configuration

The Fly.io provider requires the following environment variables:

FLY_API_TOKEN=your_fly_api_token
FLY_ORG=your_organization_slug # optional, defaults to 'personal'
FLY_REGION=your_preferred_region # optional, defaults to 'iad'

Usage

Gateway Mode (Recommended)

Use the gateway for zero-config auto-detection:

import { compute } from 'computesdk';

// Auto-detects Fly.io from FLY_API_TOKEN environment variable
const sandbox = await compute.sandbox.create();
console.log(`Created machine: ${sandbox.id}`);

// List all machines
const machines = await compute.sandbox.list();

// Destroy the machine
await sandbox.destroy();

Direct Mode

For direct SDK usage without the gateway:

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

const compute = fly({
  apiToken: 'your_api_token', // optional, uses FLY_API_TOKEN env var
  appName: 'my-app',          // optional, defaults to 'computesdk'
  org: 'my-org',             // optional, defaults to 'personal'
  region: 'iad'              // optional, defaults to 'iad'
});

// Create a machine (not an app)
const sandbox = await compute.sandbox.create({ runtime: 'node' });
console.log(`Created machine: ${sandbox.id}`);

// List all machines in the app
const machines = await compute.sandbox.list();

// Destroy the machine (app remains)
await sandbox.destroy();

Currently Implemented

Machine Operations

  • create() - Creates a new Fly.io machine in the specified app
  • getById() - Retrieves a specific machine by ID
  • list() - Lists all machines in the configured app
  • destroy() - Destroys a machine (preserves the app)

Supported Runtimes

  • node - Uses node:alpine image with HTTP server
  • python - Uses python:alpine image with HTTP server
  • default - Uses docker.io/traefik/whoami image

Configuration Options

  • apiToken - Fly.io API authentication token
  • appName - Fly.io app name (defaults to 'computesdk')
  • org - Organization slug (defaults to 'personal')
  • region - Deployment region (defaults to 'iad')
  • apiHostname - API endpoint (defaults to 'https://api.machines.dev')

Architecture

App vs Machine Management

  • App: Persistent infrastructure created once per appName
  • Machine: Ephemeral compute resources created/destroyed per sandbox
  • The app is created automatically if it doesn't exist
  • Multiple machines can exist within a single app
  • Destroying a machine preserves the app for future use

Machine Configuration

  • CPU: 1 shared core
  • Memory: 256MB
  • Network: Automatic private IP assignment
  • Lifecycle: Machines include init commands to stay running

Notes

  • All operations use the Fly.io Machines REST API
  • Apps are created automatically if they don't exist
  • Only machines are destroyed, apps persist for reuse
  • Machine names are auto-generated with timestamps for uniqueness
  • Environment variables take precedence over config options