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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@barelyhuman/minrpc

v0.1.3

Published

A `node:http` middleware for working with a JSON RPC style worker/daemon.

Downloads

9

Readme

minrpc

A node:http middleware for working with a JSON RPC style worker/daemon.

Warning: This isn't spec compliant with either versions of JSON RPC and follows no existing standard. Do not use it as a drop in replacement for any json rpc compliant libraries

Installation

$ npm install @barelyhuman/minrpc

Usage

Setup

Here's a simple example of how to set this up. Post that, you can open the browser to check if the methods got registered by calling on localhost:8000/_methods or by sending a POST request with the following body

{
	"method": "_methods"
}
// in ESM
import http from 'node:http'
import { createRPCHandler } from 'minrpc'

// in CJS
const http = require('http')
const { createRPCHandler } = require('minrpc')

const methods = {
	greeting: ({ name }) => {
		return {
			greet: `Hello, ${name}`,
		}
	},
}

const server = http.createServer(createRPCHandler(methods))

server.on('clientError', (err, socket) => {
	socket.end('HTTP/1.1 400 Bad Request\r\n\r\n')
})

server.listen(8000)

Client

There's no complicated logic involved in the first place, so you can just go ahead and send the following body as a POST request and the server should invoke the requested method accordingly.

// client
fetch('http://localhost:8000', {
	method: 'POST',
	body: JSON.stringify({ method: 'greet', params: { name: 'reaper' } }),
})

// server method
const methods = {
	greet: ({ name }) => {
		return {
			greeting: `Hello, ${name}`,
		}
	},
}

Standards

As mentioned above, there is no spec, it's based on a simple concept that you maintain consistency on both sides, you send and receive JSON serializable data

License

MIT © Reaper