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

venthub-client

v2.0.3

Published

A VentHub client for NodeJS and the modern browser

Downloads

2

Readme

vent

A VentHub client for NodeJS and for the modern browser

Installation

npm i -S venthub-worker should do the trick.

Note: This package uses ws, and can benefit from its optional deps.

Usage (NodeJS)

import Vent from 'venthub-worker';

// This will be called on every action recieved from the VentHub
function actionHandler(action) {
    console.log(JSON.stringify(action, null, 2); // pretty print the action
}

let vent = new Vent('venthub.server.io:3000', actionHandler);
vent.start(); // connect to VentHub @ venthub.server.io:3000

vent.dispatch({type: 'FOO'}) // dispatch this action to the VentHub (this WILL trigger the action handler)
.then(() => vent.dispatch({type: 'BAR'}))
.then(::vent.stop); // disconnect the Vent (notice the self-bind syntax, very experimental)

Vent as an EventEmitter

Creating a Vent with no handler will cause it to emit every action as an event of its type, with its payload as the event data.

Usage for the Modern Browser

Note: This package has no external deps, but does require native support for WebSockets, Promises, Arrow functions and Classes.

import Vent from 'venthub-client/browser';

// This will be called on every action recieved from the VentHub
function actionHandler(action) {
    console.log(JSON.stringify(action, null, 2); // pretty print the action
}

let vent = new Vent('venthub.server.io:3000', actionHandler);
vent.start(); // connect to VentHub @ venthub.server.io:3000

vent.dispatch({type: 'FOO'}) // dispatch this action to the VentHub (this WILL trigger the action handler)
.then(() => vent.dispatch({type: 'BAR'}))
.then(::vent.stop); // disconnect the Vent (notice the self-bind syntax, very experimental)

A basic implicit link

This version of Vent might not have fancy events, but it does provide a simple one-liner to hook, say, a redux store to a VentHub.

import React from 'react';
import {render as renderToDOM} from 'react-dom';
import { Provider } from 'react-redux';
import Vent from 'venthub-client/browser';
import store from './store/store';
import App from './components/main-page';

Vent.openLink('venthub.server.io:5000/', ::store.dispatch); // That's it! :)

renderToDOM(
    <Provider store={store}>
        <App />
    </Provider>,
    document.getElementById('react-container')
);