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

@broberg/fleet-client

v0.1.0

Published

Typed client for the broberg fleet HTTP API (buddy + cardmem). One import instead of hand-rolling fetch + Bearer + payload — typed end-to-end from @broberg/fleet-contracts.

Readme

@broberg/fleet-client

Typed client for the broberg fleet HTTP API (buddy + cardmem). One import instead of hand-rolling fetch + Bearer + payload in every repo — typed end-to-end from @broberg/fleet-contracts, with request bodies validated before send (you literally can't get the shape wrong).

Part of F072 — @broberg/fleet-client (see docs/features/F72-fleet-client.md).

Usage

import { createFleetClient } from '@broberg/fleet-client';

const fleet = createFleetClient({
  buddyBaseUrl: process.env.BUDDY_URL ?? 'http://localhost:4123',
  buddyKey: process.env.BUDDY_SERVER_TOKEN,        // omit on localhost-open edges
  cardmemBaseUrl: 'https://services.cardmem.com',  // for board endpoints
  cardmemKey: process.env.CARDMEM_DAEMON_KEY,
});

await fleet.dispatchIntercom({ targetSession: 'cardmem', message: 'pick up F070.2' });
await fleet.provisionTerminal({ name: 'buddy', repoName: 'buddy' });
await fleet.notifyMobile({ message: 'shipped F072.1', severity: 'info' });
const digest = await fleet.boardDigest();
await fleet.submitIdea({ project_slug: 'buddy', text: 'an idea from a service' });

Methods

| Method | Endpoint | Served by | |---|---|---| | dispatchIntercom | POST /api/intercom/dispatch | buddy (needs F072.2) | | provisionTerminal | POST /api/terminal/provision | buddy (F069) | | notifyMobile | POST /api/notify | buddy | | boardDigest | GET /api/board/digest | cardmem | | submitIdea | POST /api/board/idea | cardmem |

Routing (which base URL + key) is chosen automatically from FLEET_ENDPOINTS[name].server. The reachability ladder (local daemon vs F067 cloud-relay for a specific edge) is F072.4 — this client v1 takes explicit base URLs.

Errors

  • Invalid request → throws (zod) before any network call.
  • Non-2xx → throws FleetError (.status, .body).

Test

bun test