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

affordant

v0.2.0

Published

Affordance-first hypermedia (HATEOAS) client. Zero-dependency core: read the actions the server offers, gate your UI on them, follow them.

Readme

affordant

Affordance-first hypermedia (HATEOAS) client. Stop re-implementing your authorization rules in the frontend — let the actions the server offers drive your UI.

Your frontend never builds a URL, never picks an HTTP verb, never duplicates an authorization rule. It asks three questions:

  1. What is the server offering me?can(resource, rel)
  2. Where / how?actionFor(resource, rel)
  3. Do it.follow(action, init)

If the backend stops offering an action (not authorized, wrong state, feature off), the button disappears — no frontend deploy.

Zero-dependency core. Runs anywhere fetch exists: browsers, Node ≥ 18, Deno, Bun, edge workers. No hooks, no stores, no framework adapter.

Install

npm install affordant

Usage

import { can, actionFor, follow, type HateoasResource } from 'affordant'

type Order = { id: string; total: number; status: string }
const order: HateoasResource<Order> = await fetch('/orders/8f3a2c').then(r => r.json())

if (can(order, 'cancel')) {
  await follow(actionFor(order, 'cancel')!, {
    token: () => localStorage.getItem('token'), // lazy getter, read at request time
    body: { reason: 'changed my mind' },        // JSON-encoded per the action's `accepts`
  })
}

The core is plain functions over plain data — works the same in React, Vue, Svelte, or vanilla.

API

| Export | Description | |---|---| | HateoasResource<T> | T & { _self?: HateoasAction; _actions: Record<string, HateoasAction> } | | HateoasAction | { href: string; method: HateoasMethod; accepts?: string } | | can(resource, rel) | true iff the server currently offers rel. Null-safe. | | actionFor(resource, rel) | The action descriptor, or null. Null-safe. | | follow(action, init?) | Vanilla fetch invocation. init: body, token (string or lazy getter), headers, signal, fetch (injectable). Returns the raw Response. |

The wire-contract types are re-exported from @affordant/contract.

Server side

Any backend that emits the _self / _actions envelope works. To build it ergonomically in Node, see @affordant/server — the server-side mirror of this client.

License

MIT