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

gotti-reqres

v0.1.21

Published

Low level implementation of zeromq dealer and router sockets to make asynchronous req/res calls.

Downloads

4

Readme

Low level and lightweight messaging library that wraps around ZMQ sockets to create an API that is used in Centrum.

Simple request/response servers:

Originally the broker would have been a normal parameter to the Messenger constructor, but now the idea is to put it inside your options if you're using a messenger that needs it. So since both request and response messengers use it, 'brokerURI' must be in the options and will throw an error if you don't provide one. Same thing for the server Ids now. They will be passed in from the options.

  var requestMessengerOptions = {
    id: "requestMessengerServer"
    brokerURI: brokerURI,
    request:
     { timeout: 1000 }  // defaults to 5000 (milliseconds)
  };

  var responseMessengerOptions = {
    id: "responseMessengerServer"
    brokerURI: brokerURI,
    response: true, // still no additional configurations needed so just use a boolean.
  };

create the instances of each server. These should normally live on different processes at the least. each use a zmq dealer socket so they both need the brokerURI for routing purposes. You still need to manually start up a broker instance with the URI passed into response/request for them to work.

  var broker = new Broker(brokerURI, "brokerId");

  var requestServer = new Messenger(requestMessengerOptions);

  var responseServer = new Messenger(responseMessengerOptions);

now when you want to create your request

  // request name, response server id, hook/data

  requestServer.createRequest("foo", "responseMessengerServer")

now called like

  requestServer.requests.foo(10);

it's asynchronous so to get the response either

  const response = await requestServer.requests.foo(10);

Creating the response

"request" parameter in the function is whatever was passed into the foo request function, so 10 in this instance.

The response will process the request * 5 in its handler, and whatever it returns gets sent back to the response server asynchronously

  responseServer.createResponse("foo", function(request) { return request * 5 });

So now when you call....

  await response = requestServer.requests.foo(10);

  console.log(response) //50