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

mp-command

v0.2.0

Published

Command line utility for Message Ports

Downloads

1

Readme

mp

The mp command line utility is like curl or ncat for Message Ports (and ZeroMQ connections in general). It's a convenient way to experiment with different kinds of inter-process messaging patterns without having to write any code.

Here's an example of request/reply messaging:

First we open a reply socket on port 2000

$ mp reply 2000
- started reply socket on port 2000
- waiting for request

Lines beginning with a - are log messages from the system. Now let's open another terminal and start a request socket connected to the same port.

$ mp request 2000
- started request socket on port 2000
<

When you see a < that means that mp is waiting for you to type a message that will transmitted to the other end of the connection. Type anything and press enter.

$ mp request 2000
- started reply socket on port 2000
< sup?
- request sent
- waiting for reply

Now switch back to the reply terminal and you should see

$ mp reply 2000
- started reply socket on port 2000
- waiting for request
- request received:
> sup?
<

Type a response and switch back to the other terminal

$ mp request 2000
- started reply socket on port 2000
> sup?
- message sent, waiting for response
- reply received:
> nm, u?
<