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

@afterquery/compute

v0.4.0

Published

TypeScript SDK for the AfterQuery compute API — isolated sandboxes for AI agent pipelines

Readme

AfterQuery Compute TypeScript SDK

Node.js 18+ client for the AfterQuery Compute API.

import { Compute, GpuCreateError } from '@afterquery/compute'

const compute = new Compute({ apiKey: '...' })

try {
  const sandbox = await compute.create(
    {
      image: 'us-docker.pkg.dev/example/project/image:tag',
      resources: { gpu: { type: 'l4', count: 1 } },
    },
    { idempotencyKey: 'job-42-attempt-1' },
  )
} catch (error) {
  if (error instanceof GpuCreateError) {
    // Preserve these values when reconciling an ambiguous create outcome.
    console.error(error.idempotencyKey, error.sandboxId)
  }
  throw error
}

GPU creates require a stable idempotency key. If one is not supplied, the SDK generates one and exposes it through GpuCreateError on any create or readiness failure. GPU batch creation is intentionally unsupported.

For an ambiguous failure without a sandbox ID, call cancelGpuCreate(error.idempotencyKey) to request cleanup using the stable key. The SDK retries one transport-ambiguous cancellation request with the same key. Deleted and Failed are immutable terminal history; CleanupPending means cleanup is still converging, so call cancelGpuCreate again until a terminal state is returned. A same-key create retry may also return a terminal handle without starting or waiting for a new sandbox.

See the repository for API setup and the complete SDK surface.