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

pcats-listener

v1.4.2

Published

Node prototype for the pcats listener.

Downloads

11

Readme

pcats-listener

TCP listener, provides message decoding and encoding using proprietary binary protocol.

Request processor function is injected into server to handle requests: listener.createServer(processor) Processor function will be called with decoded request String and expected to return the response String or response Promise. If no response should be sent, just return nothing or resolve promise with no value.

Also a Client is provided for testing and simulation.

Install:

npm install pcats-listener

Run Server:

var listener = require('pcats-listener');

/**
 * Request processor function is injected into server to handle requests.
 *
 * @param {String} request
 * @returns {Promise} response or {String} response
 */
function processor(request){
    // process the request and return response
    return "Hello " + request;
}

var server = listener.createServer(processor);

server.listen(18888, localhost, function() {
    console.log('server bound');
});

Run Client:

var listener = require('pcats-listener');
var client = listener.createClient();

client.connect(18888, 'localhost', function(err, connection) {
    if(err){
        // handle connection error
        return;
    }

    // 'response' event
    connection.on('response', function(response){
        console.log('got response', response);
        
        // disconnect
        connection.end();
    });

    // 'close' event - emitted if tcp connection was closed before connection.end() was called
    connection.on('close', function() {
        console.log('Sorry connection is lost, exiting...');
    });

    // send request
    connection.request("Hello");

});

also see examples folder for more client implementations

Client Connection API:
  • connection.request(message, [callback]) sends request. connection will emit 'response' event when response is received. The optional callback parameter will be executed when the data is finally written out - this may not be immediately

  • connection.end() request connection to close

  • Event: 'response' emits 'response' event when response is received

  • Event: 'close' emits 'close' event if tcp connection was closed before connection.end() was called