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

@jsontpc/http

v0.1.1

Published

HTTP transport for @jsontpc/core — uses native Node.js http and fetch

Readme

@jsontpc/http

HTTP transport for @jsontpc/core — uses the native Node.js http module and the global fetch API (Node 18+).


Installation

pnpm add @jsontpc/http @jsontpc/core

HttpServerTransport

Creates and manages a node:http server. On every POST to the configured path it reads the body, dispatches through @jsontpc/core, and writes the JSON response with Content-Type: application/json.

Constructor

new HttpServerTransport(options?: HttpServerTransportOptions)

| Option | Type | Default | Description | |--------|------|---------|-------------| | path | string | '/' | URL path to accept requests on | | maxMessageSize | number | 1_048_576 (1 MiB) | Max request body in bytes; 413 if exceeded |

Usage

import { JsonRpcServer } from '@jsontpc/core';
import { HttpServerTransport } from '@jsontpc/http';

const server = new JsonRpcServer(router);
const transport = new HttpServerTransport({ path: '/rpc' });
transport.attach(server);
await transport.listen(3000);

HTTP response codes

| Scenario | Status | |----------|--------| | Normal response | 200 application/json | | Notification / all-notification batch | 204 No Content | | Body exceeds maxMessageSize | 413 | | Wrong HTTP method (not POST) | 405 | | Wrong path | 404 |


HttpClientTransport

Uses the global fetch API. POSTs the serialized request and returns the response body text. HTTP transport is stateless — no connect() or close() needed.

Constructor

new HttpClientTransport(url: string, options?: HttpClientTransportOptions)

| Option | Type | Default | Description | |--------|------|---------|-------------| | headers | Record<string, string> | {} | Extra headers added to every request |

Usage

import { createClient } from '@jsontpc/core';
import { HttpClientTransport } from '@jsontpc/http';

const client = createClient<typeof router>(
  new HttpClientTransport('http://localhost:3000/rpc')
);

const result = await client.add({ a: 1, b: 2 }); // 3

Notifications

Send a notification by omitting the id field. The server responds with 204 and HttpClientTransport.send() returns ''.

await fetch('http://localhost:3000/rpc', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ jsonrpc: '2.0', method: 'logEvent', params: { name: 'ping' } }),
});
// → 204 No Content

See docs/ARCHITECTURE.md §5.3 for the full design.