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

fdx

v1.0.0

Published

Full-duplex commands through a websocket connection.

Downloads

16

Readme

fdx-cmd

Full-duplex commands through a websocket connection. Basically, it's an RPC where both sides can send commands to the other one.

Usage

conn.on(command, cb): define the callback which will answer to a command. The signature of the callback is: function(data, send) where data is the received data and send is the callback to call with the data to send as an answer.

conn.emit(command, data, cb): send a command to the connection with data. cb is the function which will get called when the command gets answered. It takes one argument: the data received in the response.

conn.close(): closes the connection when no more answers are expected.

I would recommend having register and login commands which give unique IDs to slaves.

TODO

  • [ ] Proper error handling, not just console.log
  • [ ] Timeout on response callbacks, because if no response is received, it can't close the ws connection
  • [ ] Add pubsub
  • [ ] Add a function which handles a ws server, adding connections to a client obj, give id to each connection