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 🙏

© 2026 – Pkg Stats / Ryan Hefner

findhit-remote-evented

v0.0.1

Published

javascript remote evented driven with engine.io built on top of findhit-evented

Readme

Remote Evented test-badge

javascript remote evented driven with engine.io built on top of findhit-evented

Instalation


	npm install findhit-remote-evented --save

Usage


// We need an already stablished engine.io socket connection!
// so i will suppose that you already have one
var socket;

var RemoteEvented = require('findhit-remote-evented');

var Call = RemoteEvented.extend({

  // you can specify methods as `findhit-class`
  initialize: function ( my, cool, params ) {
    // ...
  },

  ring: function () {
    // ...
    this.fire('ring');
  },

  // You can bind events directly from extend as `findhit-evented`
  $on: {
    ring: function () {
      // ...
    },
  },

  // And now from remote party.
  $onRemote: {

    answer: function ( e ) {
      this.stopRing();
    },

  },

});

// We could extend it to a new class and setup it with a specific socket.
// In this case we will setup directly on current class `.setup( namespace, socket )`
Call.setup( 'VideoCall', socket );

// When you create an instance, another party will create one also
var bruno = new Call();

// You can bind or fire events as `findhit-evented`
bruno.fire('ring');
bruno.on('ring ring-stopped', function () {
  // ...
});
bruno.once('answered', function () {
  // ...
});

// And now from remote party
bruno.fireOnRemote( 'ring' );
bruno.onRemote( 'ring ring-stopped', function () {
  // ...
});
bruno.onceRemote('answered', function () {
  // ...
});

// Thats it, take a look at `test` and `example` folders for more cases.
// You don't see them? Pull Request them :)