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

stweam

v1.0.15

Published

Streams the public Twitter stream.

Downloads

61

Readme

stweam

build status coverage status npm version npm downloads dependency status devDependency status

Streams the public Twitter stream.

Note that the output is the "raw" Twitter stream, so you'll need to process it appropriately. Processing was deliberately left out of this module, so that you can choose your poison(s) via npm.

Requirements

  • Node.js version 0.11.x (for the harmony flag which exposes generators)
  • Keys obtained from dev.twitter.com after setting up a new app

Installation

$ npm install stweam --save

Example

// => example.js

var Stweam = require('stweam');
var stream = require('stream');
var dest = new stream.PassThrough();

var stweam = new Stweam({
  consumerKey: 'consumerKey',
  consumerSecret: 'consumerSecret',
  token: 'token',
  tokenSecret: 'tokenSecret'
});

// Optionally hook into log messages...
stweam.on('info', function(msg){
  // Do something with msg.
});

// ... or warn messages.
stweam.on('warn', function(msg){
  // Do something with msg.
});

// stweam is a Stream.
stweam.pipe(dest);

stweam
  .language('fr')
  .track('beaker')
  .follow('12345')
  .start();

To run:

$ node --harmony example.js

Also, check out chirp to see Stweam in action.

API

var stweam = new Stweam(opts)

Initialise a new Stweam with the given opts.

opts should contain:

  • consumerKey
  • consumerSecret
  • token
  • tokenSecret

stweam.track(keywords)

Set the phrases that will determine what is delivered on the stream.

See: track.

stweam.language(language)

Set the Tweet language, defaults to en.

See: language.

stweam.follow(userids)

Set the users whose Tweets will be delivered on the stream.

See: follow.

stweam.start()

Start the app.

Events

Note: I like Bunyan's opinions on log levels :)

stweam.on('info', function(msg){})

Provides detail about regular operation, rather than spamming stdout.

stweam.on('warn', function(msg){})

Might want to take a closer look at this one.

Tests

To run:

$ npm run test:spec

To generate a coverage report:

$ npm run test:cov

Credits