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

rtm

v1.0.10

Published

Socket.io extension for invoking and emitting with callback

Downloads

3

Readme

rtm

Socket.io extension for invoking and emitting with callback.

Installation

npm install --save rtm

The UMD build is in the dist directory.

Description

Socket.io is a perfect library for what it's made for. We don't want to replace it, in fact, we just add 3 new methods to the socket both on the client and the server: invoke, emitSafe and ping.

invoke(method: string, data?: Object, callback: function(error:Object|null, param1?, ...param2?))

Call a handler on the other side and wait for the callback (usually receiving some data).

emitSafe(event: string, param1, ...param2?: Object, callback: function(error:Object|null))

Just like normal emit, but provided with a callback. The callback is called when the client receives the message.

ping(callback: function(error:Object|null, milliseconds))

Ping the server and get the time it took to send and receive the data.

Usage

Everything is perfectly shown in the examples folder. The client.js script can be run both on the client and the server.

The example below is more advanced because it is supposed to be used for bigger implementations with more than one method. If you don't need to extend you don't have to. You can just use RTMSocket from the rtm package just the same, just pass the handlers to it as a parameter.

'use strict';

const RTMSocket = require('rtm');

// First we extend for all sockets we will need.

class ServerSocket extends RTMSocket {
    constructor(socket) {
        super(socket);

        this._handlers = {
            getTime: (data, callback) => {
                console.log('Client invoked getTime.');
                callback(null, Date.now());
            }
        };
    }

    getClientTime() {
        this.invoke('getTime', null, (error, result) => {
            console.log('Client time result:', error, result);
        });
    }
}

class ClientSocket extends RTMSocket {
    constructor(socket) {
        super(socket);
        
        this._handlers = {
            getTime: (data, callback) => {
                console.log('Server invoked getTime.');
                callback(null, Date.now());
            }
        };
    }

    getServerTime() {
        this.invoke('getTime', null, (error, time) => {
            console.log('Server time result:', error, time);
        });
    }
}

// And now just wrap the client and the server sockets:

// Server code:

const io = require('socket.io');
let socket = io();
socket.listen(80);

socket.on('connection', (socket) => {
    console.log('Connection established.');

    socket = ServerSocket.wrap(socket);

    socket.on('testEvent', (foo, bar) => console.log('Client sends testEvent:', foo, bar));
    socket.once('disconnect_for_good', () => console.log('Connection closed.'));
    
    socket.getClientTime();
    socket.ping((error, time) => console.log('Ping result:', error, time));
    socket.emitSafe('testEvent', 'foo', 'bar', error => console.log('Emitted: testEvent'));
});


// Client code:

const io = require('socket.io-client');
let client = ClientSocket.wrap(io('http://localhost', {reconnectionAttempts: 2}));

client.on('connect', () => {
    client.on('testEvent', (foo, bar) => console.log('Server sends testEvent:', foo, bar));
    client.once('disconnect_for_good', () => console.log('Connection closed.'));
    
    client.getServerTime();
    client.ping((error, time) => console.log('Ping result:', error, time));
    client.emitSafe('testEvent', 'foo', 'bar', error => console.log('Emitted: testEvent'));
});