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

nsqjs-streams

v0.2.3

Published

Wraps NSQ Reader and Writer clients in NodeJS streams.

Downloads

19

Readme

nsqjs-streams Build Status

Wraps an nsqjs Reader and Writer client in NodeJS streams.

Usage

Reader(topic, channel, options)

The arguments maps directly to the ones of an nsqjs.Reader client. The full options list is available at the nsqjs npm page.

The Reader stream is operating in object mode, hence calling read() will return the whole message body as a Buffer.

Reader Example

The example pipes the incoming message body to stdout.

var nsqStreams = require("nsqjs-streams"),
    readerStream = new nsqStreams.Reader("topic", "channel", {
        lookupdHTTPAddresses: [ "localhost:4161" ]
    };

readerStream.pipe(process.stdout);

Writer(nsqdHost, nsqdPort, options, getters)

The arguments, nsqdHost, nsqdPortand options maps directly to the nsqjs Writer client arguments. Additionally the writer allows you to specify custom getter functions or properties to get topic and message from an object. The getters is always passed as the last argument to a writer, if options is omitted then getters can be specified in it's place.

If getters is omitted the stream will default to interleaved mode, meaning that the topic and message is assumed to be interleaved in the stream.

Getter functions and/or properties must be specified for both topic and message. This requires the each object written to the stream to contain the data necessary to extract topic and message.

Writer Example

Each stream writes an identical message to NSQ.

var nsqStreams = require("nsqjs-streams"),
    interleaved = nsqStreams.Writer("localhost", 4150),
    properties = nsqStreams.Writer("localhost", 4150, {
        topic: "topic",
        message: "message"
    }),
    functions = nsqStreams.Writer("localhost", 4150, {
        topic: function (data) { return data.topic; },
        message: function (data) { return data.message; }
    });

interleaved.write("topic");
interleaved.write("message");

properties.write({ topic: "topic", message: "message" });

functions.write({ topic: "topic", message: "message" });