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

@vibly-ai/coordinator-http-contract

v0.1.2

Published

Single source of truth for the Vibly Coordinator HTTP and SSE contract, consumed by `@vibly-ai/client` and `vibly-console`.

Readme

@vibly-ai/coordinator-http-contract

Single source of truth for the Vibly Coordinator HTTP and SSE contract, consumed by @vibly-ai/client and vibly-console.

The contract is derived from vibly-coordinator at build time:

vibly-coordinator (Fastify routes with @fastify/swagger)
        |  pnpm --filter vibly-coordinator dump:openapi
        v
@vibly-ai/coordinator-http-contract/openapi.json
        |  pnpm --filter @vibly-ai/coordinator-http-contract gen
        v
src/generated/types.ts        <- openapi-typescript output
src/client.ts / src/sse.ts    <- thin transport-agnostic wrappers

What this package exposes

  • openapi.json — committed artifact, regenerated from coordinator routes; CI gates drift.
  • src/generated/types.ts — generated paths and components for openapi-fetch typing.
  • src/client.tscreateCoordinatorClient({ baseUrl, fetch, headers }) with envelope unwrap and CoordinatorApiError.
  • src/sse.ts — typed SSE helpers for both project and global streams.

Version policy surface

This package now includes typed support for coordinator compatibility policy and daemon operations:

  • GET /version-policy for minimum and recommended client versions.
  • POST /agents/{id}/heartbeat for daemon heartbeat and upgrade phase reporting.
  • Typed UPGRADE_REQUIRED error envelopes surfaced through CoordinatorApiError.
  • SSE helpers aligned with the live coordinator routes: projectEventStreamUrl() -> /projects/:projectId/stream globalEventStreamUrl() -> /streams/events

Consumers are expected to attach these headers on protected requests:

  • X-Vibly-Client-Package
  • X-Vibly-Client-Version
  • X-Vibly-Contract-Version
  • X-Vibly-Protocol-Version

What this package does not contain

  • Fastify, React, Commander, or any UI, CLI, or server framework.
  • Authentication policy or transport choices. Those live in consumers.
  • Consumer-specific retry, timeout, idempotency, or process-management logic.

Consumers

  • @vibly-ai/client — Node CLI and daemon; adds authorization, retries, idempotency, version headers, and upgrade logic.
  • vibly-console — Web UI; chooses direct vs proxy URL building and uses its own data-fetching layer on top.

Both must consume only this package's exported types and client helpers. Handwritten path strings are not allowed.

Development

pnpm gen
pnpm lint
pnpm build