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

capable-kit

v0.0.1-alpha.7

Published

Capable is a TypeScript framework for defining a capability once and exposing it through the surfaces your application needs: typed calls, HTTP, CLI, MCP, AI tools, and more.

Downloads

1,263

Readme

Capable

Capable is a TypeScript framework for defining a capability once and exposing it through the surfaces your application needs: typed calls, HTTP, CLI, MCP, AI tools, and more.

Schemas may come from any library that implements both Standard Schema and Standard JSON Schema. This example uses Zod as a provider:

pnpm add capable-kit zod
import { capability, defineApp } from "capable-kit";
import { z } from "zod";

const greet = capability({
  id: "greet",
  input: z.object({ name: z.string() }),
  handler: ({ input }) => ({ message: `Hello, ${input.name}` }),
});

export default defineApp({
  name: "Greeting",
  capabilities: { greet },
});

TypeScript infers the handler's output type. An output schema is optional and adds runtime output validation plus a portable schema for OpenAPI and tool surfaces.

Capable is early alpha software. APIs may change without compatibility layers.

The package provides the cap CLI command. capable remains an alias:

cap dev

Deploy

Capable detects supported build environments such as Vercel and emits their native deployment output:

vercel

To create Vercel's Build Output API locally instead:

cap build --preset vercel
vercel deploy --prebuilt

For a deployment protected by Vercel Authentication, link the local project. Capable reuses the Vercel CLI login to resolve that project's Protection Bypass for Automation:

vercel link
cap cli --app https://your-app.vercel.app hello

An explicit environment variable remains available for CI or unlinked projects:

export VERCEL_AUTOMATION_BYPASS_SECRET="..."
cap cli --app https://your-app.vercel.app hello

Documentation

Documentation matching the installed version ships at:

node_modules/capable-kit/docs/

Coding agents should start with node_modules/capable-kit/docs/README.md, then read the relevant guide before writing Capable code. The package also includes its original TypeScript source under src/ when a guide does not cover a lower-level API detail.

Package contents

The published package includes compiled ESM in dist/, declaration files, the original TypeScript authoring source in src/, and the complete documentation in docs/. User-facing guides are under docs/site/; framework design notes and invariants are under docs/internal/.