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

hrpc

v4.3.0

Published

**Append only API definition and code generation.**

Downloads

5,454

Readme

HRPC

Append only API definition and code generation.

Features

  • Define request/response interfaces with optional streaming.
  • Auto-generate rpc code to disk.
  • Supports send-only and duplex commands.
  • Enforces schema consistency across versions.

Installation

npm install hrpc

Usage

Define Your Schema

Place your Hyperschema and HRPC definitions in the appropriate directories.

const HRPCBuilder = require('hrpc')
const Hyperschema = require('hyperschema')
const path = require('path')

const SCHEMA_DIR = path.join(__dirname, 'spec', 'hyperschema')
const HRPC_DIR = path.join(__dirname, 'spec', 'hrpc')

// register schema
const schema = Hyperschema.from(SCHEMA_DIR)
const schemaNs = schema.namespace('example')

schemaNs.register({
  name: 'command-request',
  fields: [{ name: 'foo', type: 'uint' }]
})

schemaNs.register({
  name: 'command-response',
  fields: [{ name: 'bar', type: 'string' }]
})
Hyperschema.toDisk(schema)

// Load and build interface
const builder = HRPCBuilder.from(SCHEMA_DIR, HRPC_DIR)
const ns = builder.namespace('example')

// Register commands
ns.register({
  name: 'command',
  request: { name: '@example/command-request', stream: false },
  response: { name: '@example/command-response', stream: false }
})

// Save interface to disk
HRPCBuilder.toDisk(builder)

Use the Generated RPC

const { PassThrough } = require('bare-stream')
const HRPC = require('./spec/hrpc') // generated rpc
const stream = new PassThrough()
const rpc = new HRPC(stream)

async function main() {
  rpc.onCommand((data) => {
    return { bar: `${data.foo + 1}` }
  })

  const res = await rpc.command({ foo: 1 })
  console.log(res) // => { bar: 2 }
}

main()

Example for duplex command:

/*
ns.register({
  name: 'command',
  request: {
    name: '@example/command-request',
    stream: true
  },
  response: {
    name: '@example/command-response',
    stream: true
  }
})
*/

rpc.onCommand((stream) => {
  stream.on('data', (data) => {
    console.log('Received:', data)
  })
  stream.write({ response: 'pong' })
})

const duplex = rpc.command()
duplex.write({ request: 'ping' })
duplex.on('data', (data) => {
  console.log('Reply:', data)
})

Send-Only Commands

You can also define commands that only send data without waiting for a reply:

ns.register({
  name: 'command',
  request: { name: '@example/command-request', send: true }
})

Error Handling and Schema Consistency

Redefining an already-registered command with different schemas or stream types will throw an exception:

// First, command is declared as an async call with return value
ns.register({
  name: 'command',
  request: { name: '@example/command-request', stream: false },
  response: { name: '@example/command-response', stream: false }
})

// This throws because the schema has been altered
ns.register({
  name: 'command',
  request: { name: '@example/command-request', stream: true },
  response: { name: '@example/command-response', stream: false }
})