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

opifex.twitter

v0.0.2

Published

Grabs a Twitter stream and feeds it to AMQP

Downloads

5

Readme

Opifex.Twitter

Opifex.Twitter generates a stream of messages to AMQP from Twitter Streams.

Installation

npm install opifex
npm install opifex.twitter

Usage

First generate a config file of the name ~/.twitter.coffee of the form:

module.exports =
	consumer_key: "XXXXXXXXXXXXXXXXXXX",
	consumer_secret: "XXXXXXXXXXXXXXXXXXX",
	access_token_key: "XXXXXXXXXXXXXXXXXXX",
	access_token_secret: "XXXXXXXXXXXXXXXXXXX"

This will be read in whenever you start up the client. It looks in the home directory of whatever user is running the process, so you can secure your Oauth credentials.

Then from the command line run:

opifex 'amqp://guest:guest@localhost:5672//twitter-cmd/#/twit/twitter-out/tweet' twitter

Once it is running as specified on the above command, it will listen on a twitter-cmd exchange for any messages in the twit queue. It will then direct all of its output to an twitter-out exchange with a routing key of tweet. Feel free to change any of the resource paths as fits your application.

To start the connection to Twitter issue a message of the form:

[ "connect", "statuses/sample" ]

or

[ "connect", "statuses/firehose" ]

And opifex will start forwarding the tweets to you twitter-out exchange with a routing key or tweet.