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

@plurnk/plurnk-schemes-http

v0.19.9

Published

http(s):// URI scheme handler for the plurnk agent runtime — fetch + streaming response body.

Readme

plurnk-schemes-http

http(s):// URI scheme handler for the plurnk agent runtime. The first greenfield @plurnk/plurnk-schemes-* sibling — authored entirely against the DB-free capability contract (@plurnk/plurnk-schemes SchemeCtx), importing zero plurnk-service internals.

What it does

Lets the model treat any web URL as an addressable, streamable resource:

| Op | Behavior | |---|---| | READ(http(s)://host/path) | fetch the URL; stream the response body into the body channel as it arrives. A streaming read — returns 102 Processing, the subscription accumulates, the model reads the entry on a later turn. | | SEND[200](http(s)://…) | Request with a body (POST); response streams back the same way. | | SEND[499](http(s)://…) | Cancel an in-flight request (abort the fetch). | | SEND[410](http(s)://…) | Delete the cached response entry. |

Response status + headers land in the header channel; the body in body (the default).

Channels

  • body — response payload (default channel).
  • headerHTTP <status> <statusText> line + response headers.

Design

  • Streaming via the capability subscriptions lifecycle (opennotifyChunkclose). open() returns the run+teardown-composed AbortSignal; a SubscriptionHandle is registered so the engine routes SEND[499] cancellation to the in-flight fetch.
  • No runtime dependenciesfetch, AbortController, TextDecoder, ReadableStream are Node ≥25 built-ins.
  • DB-free — reaches the substrate only through ctx capabilities (subscriptions, entries), never a raw DB handle (plurnk-schemes SPEC §5). This is what the keystone capability ctx made possible.

Install

npm i @plurnk/plurnk-schemes-http && plurnk start

Plugin discovery registers it at boot (package.json#plurnk.kind === "scheme").

Tests

test:lint (tsc) + test:unit (conformant SchemeCtx stub + mock fetch).