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

listenner

v1.1.1

Published

a library to listen on a port wait event from client

Downloads

5

Readme

listenner Logo

Lead Maintainer: xzmagic

server

var listenner = require('../index.js').Listenner;

var listen = new listenner(3000);

listen.on('dataChanged', function(client) {
    client.write('OK nofify event recved!');
});

client

var Notify = require('../index.js').Notify;

var notify = new Notify({
    'hostname': '127.0.0.1',
    'port': 3000
});

var data = {
    'event': 'dataChanged'
}

notify.send(data, 'get');

##output: ###server

 recv from [::ffff:127.0.0.1:19475]  method =GET
 call function with   dataChanged

###client

Status: 200
Headers: {"date":"Wed, 26 Jul 2017 13:55:16 GMT","connection":"close","transfer-encoding":"chunked"}
recv rsp =  OK nofify event recved!

<<<<<<< HEAD

Pull

###subscribe message from a Push node point to point ,if you have multi Pull node call ext() with Pull let Pull upgrade to a broadcast Pull node, ###then multi Pull node can receive message from a Push node;

var listenner = require('listenner');
var Pull = listenner.Pull;
var eventPull = new Pull();
eventPull.ext();
eventPull.connect('127.0.0.1', config.dbchange.zmqPort);
eventPull.on('message', function (message) {
console.log("recv  zmq message " + message);
if (message == "dataChanged")
    this_.freshMe();
});

Push

###push message to Pull node point to point, if you have multi Pull node call ext() with Push let Push upgrade to a broadcast Push node, ###then you can use Push node push message to all pull nodes

var Listenner = require('listenner').Listenner;
var Push = require('listenner').Push;
var config = require('./config.js');

var dbListenner = new Listenner(config.dbchange.httpPort);
var eventPush = new Push();
eventPush.ext();
eventPush.bind(config.dbchange.zmqPort);

dbListenner.on('dataChanged', function (client) {
    client.write('OK nofify event recved!');
    eventPush.sendMessage("dataChanged");
});

=======

3daf636322e3c8ec5122f053b7c9d91dd20b7099