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

@synap-core/pod-client

v0.1.0

Published

Shared pod lifecycle client — create, poll, delete managed pods via Control Plane. React hook subpath under /react.

Readme

@synap-core/pod-client

Shared pod lifecycle client — create, poll, delete managed pods via the Synap Control Plane.

Scope: this package owns the pod row's lifecycle only. It does NOT own auth (see @synap-core/auth), IS provisioning (see @synap-core/intelligence-connect), or pod classification (see @synap-core/platform-flow).

Why separate

  • platform-flow = pure classification (Node-safe, no fetch)
  • auth = session + pod handshake (credentials)
  • intelligence-connect = IS provisioning (tier-2, on existing pod)
  • pod-client = CP lifecycle management (this package)

Usage

import {
  createAndStartManagedPod,
  fetchPodStatus,
  pollPodStatus,
  deletePod,
  type PodClientConfig,
} from "@synap-core/pod-client";

const config: PodClientConfig = {
  cpBaseUrl: "https://api.synap.live",
  getBearerToken: async () => sessionStore.get("cp-token"),
};

// From a user-initiated confirm dialog:
const { podId } = await createAndStartManagedPod(config);

// Show a loader that polls until terminal:
const final = await pollPodStatus(config, podId, {
  onUpdate: (s) => console.log(s.phase, s.statusMessage),
});

React hosts use the hook subpath:

import { usePodStatus } from "@synap-core/pod-client/react";

const { status, isPolling, error, cancel } = usePodStatus(config, podId, {
  onReady: (s) => router.push(`/pod/${s.id}`),
});

Cancel semantics

CP returns 409 Conflict on DELETE /pods/:id when the pod is in an active provisioning state (pending, creating_server, configuring_dns, waiting_dns, deploying_services, waiting_health, syncing_intelligence, sending_invitation).

UI callers should:

  • Disable the cancel button during those states (tooltip: "wait ~30s")
  • Enable it when status.phase === 'pending' or status.phase === 'errored'
  • On confirmed delete, call deletePod(config, podId) and handle the { success: false, status: 409 } case gracefully (user cancelled right as the first step started).

Phase derivation

phase is derived client-side on every fetch. Callers should switch on phase not status — the CP status enum is owned by CP and will grow.