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

@wringer/http

v0.1.2

Published

The http driver for wringer: requests against a target, read-only unless granted

Readme

The http driver for wringer: it sends requests to a target's app and keeps each response as evidence.

Install

bun add @wringer/core @wringer/http

The package runs on Bun 1.3 or newer.

Usage

Add the driver to the registry, then give each target its config:

import { createWringer, local } from '@wringer/core';
import { http } from '@wringer/http';

export const registry = createWringer({ name: 'shop' })
  .use(http({ timeoutMs: 10_000 }))
  .target('prod', {
    mode: 'attach',
    access: 'read-only',
    host: local(),
    endpoints: () => ({ web: 'https://shop.example' }),
    drivers: { http: () => ({ readOnly: { allow: [{ method: 'POST', path: '/api/search' }] } }) },
  })
  .build();

An action calls ctx.drivers.http.request({ method, path, headers, json }). The CLI adds http request --path /api/cart, which takes the JSON body as --body, because the CLI's --json picks the output. It also adds the doctor check http.reachable. A JSON body on a GET or HEAD request fails with a usage error before the driver sends it.

http() takes timeoutMs, 30 seconds by default, and transport, a function of a URL and its RequestInit that returns a Response. The driver sends each request through transport, which is fetch unless the repo passes its own.

Target config

| Field | Default | Meaning | | ------------ | ------- | ----------------------------------------------------------- | | endpoint | web | The run endpoint whose URL the paths join. | | baseURL | none | A URL to use in place of the endpoint. | | healthPath | / | The path the doctor checks; a 5xx answer fails the check. | | readOnly | none | allow: the method and path globs a read-only target runs. |

GET, HEAD and OPTIONS are reads. A read-only target refuses any other method with exit code 3 and the target's hint, unless readOnly.allow lists that method and path. The driver never follows a redirect: it returns the 3xx response, so a granted request never reaches a path the target did not grant.