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

wsabi-client-bacon

v0.2.1

Published

BaconJS powered lightweight client for the hapi websocket layer, wsabi.

Downloads

8

Readme

Wsabi Client Bacon

Build Status

An alternative lightweight client for the hapi websocket layer, wsabi. Heavily based uppon wsabi-client. But is written in pure JavaScript and uses a different Reactive provider baconjs.

Why?

Mostly a matter of preference. I find BaconJs' documentation easier to understand and their API has a lot less complexity. You can read more about this topic here please consider both before choosing.

Wasabi and bacon also go together well aparently.

Differences

There's some minor API differences in the handling of subscribing to live events. That allow you to catch the internal PUT request that occurs on subscribing to a live event. In addition use .onValue rather than .subscribe.

It is also assumed that ws and bluebird are ok to be used as your websocket and promise provider. If there's a problem with this let me know and i'll restore that functionality.

Usage

var Client = require('wsabi-client-bacon');

var client = new Client("wss://localhost:3000");

var channelName = "channel";

client.socket.on("open", function () {
	// Send requests to the server with get, put, post, delete, or request.
	client.get("/api/v1/channels/"+channelName).then(function(res) {
		// Subscribe to a live event
		client.live('channel:'+res.id+':update').then(function(res) {
			res.onValue(function(value){
				console.log('Channel update',value);
			})
		});
	});
});