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

dweb-drpc

v1.0.0

Published

Simple RPC with Protobuf services.

Downloads

2

Readme

drpc

Simple RPC with Protobuf Services

npm install drpc-dweb

Usage

First define an RPC service

message Echo {
  required string value = 1;
}

service Example {
  rpc Echo (Echo) returns (Echo) {}
}

Then compile it using the drpc compiler

npm install -g drpc-dweb
drpc services.proto --rpc=rpc.js --messages=rpc-messages.js
npm install --save drpc-runtime # make sure to add this to your package.json

That's it!

The above produces two files, rpc.js and rpc-messages.js. Now you can run an RPC server and client like so:

const MyRPC = require('./rpc')

// a server
const server = MyRPC.createServer(function (client) {
  client.example.onRequest({
    async echo ({ value }) {
      return { value: 'echo: ' + value }
    }
  })
})

await server.listen('/tmp/test.sock')

// a client
const client = MyRPC.connect('/tmp/test.sock')

const { value } = await client.example.echo({ value: 'hello world!'})
console.log(value) // 'echo: hello world'

The client object in the server and that's returned from connect implements the same API so you can handle requests in both the server and client, depending on your needs!

To destroy a client do:

client.destroy()

And to close a server and all open connections do:

await server.close()

If your request handler throws an error it is forward to the client using the following schema

message RPCError {
  required string message = 1;
  optional string code = 2;
  optional int32 errno = 3;
  optional string details = 4;
}

And if your rpc method does not return a value you can use the Void type in the definition.

License

MIT