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

@appport/transport-http

v1.0.1

Published

HTTP AppPort transport.

Readme

@appport/transport-http

The HTTP transport.

import { createHttpTransport } from "@appport/transport-http";

const transport = createHttpTransport({ url: "/appport", sessionId });

One endpoint carries every capability:

  • requests — POST /appport with one envelope in, one envelope out.
  • streams — the same POST, answered as application/x-ndjson: one envelope per line, stream.start through stream.end. Cancelling aborts the request.
  • events — GET /appport/events as Server-Sent Events, each frame carrying one AppPort event envelope.

So a plain HTTP deployment reaches conformance level 3 without a second protocol.

Transport status and application status stay separate: the client reads the envelope, not the status code. Chunk sequence numbers are checked, and an out-of-order chunk fails the stream with STREAM_ERROR.