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

twitint

v0.0.4

Published

A fault tolerant app that listens to filtered tweets via the twitter streaming api and processes them according to a custom lambda function. The lambda function may be synchronous or asynchronous.

Downloads

12

Readme

twitint

A fault tolerant app that listens to filtered tweets via the twitter streaming api and processes them according to a custom lambda function. The lambda function may be synchronous or asynchronous.

Build Status Coverage Status Known Vulnerabilities

Installation

npm install twitter-lite
npm install twitint

Usage

Starting A New Listener

const Client = require('twitter-lite')
const Listener = require('twitint')


const client_primary = new Client({
  consumer_key: 'consumer_key',
  consumer_secret: 'consumer_secret',
  access_token_key: 'access_token_key',
  access_token_secret: 'access_token_secret'
})

const client_secondary = new Client({
  consumer_key: 'consumer_key',
  consumer_secret: 'consumer_secret',
  access_token_key: 'access_token_key',
  access_token_secret: 'access_token_secret'
})

// instantiate a new Listener using 2 clients with the secondary client acting as a fallback
const listener = new Listener([client_primary, client_secondary])

// starting a stream of tweets filtered by tracking terms
listener.stream('statuses/filter', { track: 'javascript, nodejs, maldives, twitter, and, so, on' }, tweet => {
  // do stuff with tweets as they come
  console.log(tweet.id)
})

// the app emits a listening event when the active client has started streaming
listener.on('listening', message => {
  console.log(message)
})

// the app emits an error only when all reconnect attempts have failed, thereby suspending all listeners
listener.on('error', err => {
  console.log(err)
})

// the app warns of errors in processing individual tweets and emits a warning whenever the active client connection is interrupted
listener.on('warning', message => {
  console.log(message)
})

Updating an Existing Listener

This library allows you to apply updates to the initial listener without severing the connection between your app and twitter. It does this by starting a connection with the updated parameters using the fallback client and only then terminating the primary client. The application shouldn't theoretically lose any data between the switchover since one client remains open while the other is connecting.

// update an existing listener
listener.update('statuses/filter', { track: 'new terms, like, bubble gum, facebook, instagram, #10YearChallenge' }, tweet => {
  // do new stuff with tweets
  console.log(tweet.user)
})

Additional Events

// the retrying event is emitted when attempting to reconnect
listener.on('retrying', message => {
  console.log(message)
})

// the updating event is emitted when attempting to update an existing listener
listener.on('updating', message => {
  console.log(message)
})