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

localcast

v2.0.1

Published

A shared event emitter that works across multiple processes on the same machine, including the browser!

Downloads

29

Readme

localcast

A shared event emitter that works across multiple processes on the same machine, including the browser!

npm install localcast

Usage

First save the example below in file called example.js.

var localcast = require('localcast')
var cast = localcast()

cast.on('hello', function (data) {
  console.log('hello', data)
})

cast.emit('hello', 'world')

Then try running the example in a terminal.

# in one terminal
$ node example.js

Running the above should print out hello world and keep the process running.

Then try running opening a new terminal and run the example again.

# in a new terminal
$ node example.js

Both the new and old terminal should print out hello world.

Now try browserifying the example

browserify example.js > bundle.js
echo '<html><body><script src="bundle.js"></script></body></html>' > example.html

Open example.html in a browser. Now both the browser and the two previous terminals should print out hello world!

API

var cast = localcast([name])

Create a new localcast event emitter.

Optionally you can give it a name if you are running multiple and want them to avoid clashing.

cast.on('localcast', peer)

Whenever you are connected to another localcast instance a special localcast event is emitted with an object describing the other instance.

cast.on('localcast', function (peer) {
  console.log('we are connected to another instance', peer)
})

If the other peer is a browser the peer looks like this

{
  type: 'browser',
  localhost: urlOfWebsite
}

If the other peer is a node process it looks like this

{
  type: 'node',
  pid: pid
}

License

MIT