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

remote-event-emitter

v1.2.0

Published

Deliver events remotely over Unix sockets or TCP connections using standard EventEmitter

Downloads

9

Readme

remote-event-emitter

Build Status Coverage Status Built with GNU Make Required Node.js version

Deliver Node's EventEmitter events over Unix sockets or TCP connections 🚀

About

This module allows forwarding events (including JSON-serialisable arguments to the events) to another process, with the receiving end behaving as if the events were emitted locally. You can use this for IPC communications where one-directional messaging is needed (ie. one process sends events and another process receives them).

The events are delivered as follows:

  1. The consumer (process which wants to receive events) creates a Unix socket or TCP connection and start listening for connections
  2. The provider (process which wants to send events) connects to this socket and starts emitting events locally just like any other EventEmitter instance - via emitter.emit('event', ...args)
  3. The consumer emits a connection event every time someone connects to the socket. This event will receive a single argument, a source, which basically mirrors the event emitter from the provider side (it will emit the events the provider emits in the other process)

Installation

Install this package on both ends and use either the Consumer or Producer class.

npm install --save remote-event-emitter

Usage

Consumer

import { Consumer } from 'remote-event-emitter'

const consumer = new Consumer()
// Bind to a socket
await consumer.listen({ address: '/tmp/my-fancy.sock' })
// Or, bind to a TCP port 12345
await consumer.listen({ address: 12345 })

// Handle for incoming connections
consumer.on('connection', source => {
  // The events emitted on source will match the events emitted
  // in the provider process
  source.on('hello', string, flag => {
    console.log(string)   // -> "world"
    console.log(flag)   // true
  })

  source.once('close', () => {
    console.log('Client disconnected!')
  })
})

// When you no longer want to accept new connections from providers
// This will close the socket.
await consumer.close()

Provider

import { Provider } from 'remote-event-emitter'

// The socket must exist, otherwise an error will be thrown
const provider = new Provider({ address: '/tmp/my-fancy.sock' })

provider.emit('hello', 'world', true)

// Always close the connection when you are done sending events
provider.end()

Reference implementations

See mocha-reporter-remote for a reference implementation on the provider and atom-ide-mocha for the consumer side.

License

See the LICENSE file for information.