A streaming Twitter Stream API client with extended exposure of the underlaying protocol events. It does also fully adhere to Twitters different reconnect rules.

$ npm install twitter-stream-api

Connect to the Twitter stream API and listen for messages containing the word "javascript".

var TwitterStream = require('twitter-stream-api'),
    fs = require('fs');

var keys = {
    consumer_key : "your_consumer_key",
    consumer_secret : "your_consumer_secret",
    token : "your_access_token_key",
    token_secret : "your_access_token_secret"
};

var Twitter = new TwitterStream(keys, false);
Twitter.stream('statuses/filter', {
    track: 'javascript'
});

Twitter.pipe(fs.createWriteStream('tweets.json'));

Create a new Twitter Stream API instance.

var Twitter = new TwitterStream(keys, [objectMode, options]);

Takes an Object containing your Twitter API keys and access tokens. The Object are as follow:

{
    consumer_key : "your_consumer_key",
    consumer_secret : "your_consumer_secret",
    token : "your_access_token_key",
    token_secret : "your_access_token_secret"
}

Twitter API keys and tokens can be generated here.

Boolean value for controlling if the stream should emit Objects or not. Default value is true which set the stream to emit Objects. If a non-object stream is wanted, set the value to false.

An Object containing misc configuration. The following values can be provided:

• gzip - Boolean value for enabling / disabling gzip on the connection against Twitter.
• pool - Sets pool configuration on the underlaying request.js object.

Please refere to request.js for further documentation on these cunfiguration options.

The Twitter Stream API instance have the following API:

Opens a connection to a given stream endpoint.

The following values can be provided:

• statuses/filter API Doc
• statuses/sample API Doc
• statuses/firehose API Doc
• user API Doc
• site API Doc

Object holding optional Twitter Stream API endpoint parameters. The Twitter Stream API endpoints can take a set of given parameters which can be found in the API documentation for each endpoint.

Example:

The statuses/filter endpoint can take a track parameter for tracking tweets on keywords. The same endpoint can also take a stall_warnings parameter to include stall warnings in the Twitter stream.

To track the keyword javascript and include stall warnings, do as follow:

Twitter.stream('statuses/filter', {
    track: 'javascript',
    stall_warnings: true
});

Do note that the track and follow parameters can take both a comma separated list of values or an Array of values.

Twitter.stream('statuses/filter', {
    track: 'javascript,rust'
});

is the same as:

Twitter.stream('statuses/filter', {
    track: ['javascript','rust']
});

Closes the connection against the Twitter Stream API.

Under the hood this client use request to connect to the Twitter Stream API. Request have several tools for debugging its connection(s). This method provide access to the underlaying request object so one can plug in a debugger to request.

The underlaying request object are available as the first argument on the callback.

Example using request-debug:

var Twitter = new TwitterStream(keys);

Twitter.debug(function (reqObj) {
    require('request-debug')(reqObj, function (type, data, req) {
        console.log(type, data, req);
    });
});

twitter-stream-api expose a rich set of events making it possible to monitor and take action upon what is going on under the hood.

Emitted when a successfull connection to the Twitter Stream API are established.

Twitter.on('connection success', function (uri) {
    console.log('connection success', uri);
});

Emitted when a the connection to the Twitter Stream API are taken down / closed.

Twitter.on('connection aborted', function () {
    console.log('connection aborted');
});

Emitted when the connection to the Twitter Stream API have TCP/IP level network errors. This error event are normally emitted if there are network level errors during the connection process.

Twitter.on('connection error network', function (error) {
    console.log('connection error network', error);
});

When this event is emitted a linear reconnect will start. The reconnect will attempt a reconnect after 250 milliseconds and increase the reconnect attempts linearly up to 16 seconds.

Emitted when the connection to the Twitter Stream API have been flagged as stall. A stall connection is a connection which have not received any new data or keep alive messages from the Twitter Stream API during a period of 90 seconds.

This error event are normally emitted when a connection have been established but there has been a drop in it after a while.

Twitter.on('connection error stall', function () {
    console.log('connection error stall');
});

When this event is emitted a linear reconnect will start. The reconnect will attempt a reconnect after 250 milliseconds and increase the reconnect attempts linearly up to 16 seconds.

Emitted when the connection to the Twitter Stream API return an HTTP error code.

This error event are normally emitted if there are HTTP errors during the connection process.

Twitter.on('connection error http', function (httpStatusCode) {
    console.log('connection error http', httpStatusCode);
});

When this event is emitted a exponentially reconnect will start. The reconnect will attempt a reconnect after 5 seconds and increase the reconnect attempts exponentially up to 320 seconds.

Emitted when the connection to the Twitter Stream API are being rate limited. Twitter does only allow one connection for each application to its Stream API.Multiple connections or to rappid reconnects will cause a rate limiting to happen.

Twitter.on('connection rate limit', function (httpStatusCode) {
    console.log('connection rate limit', httpStatusCode);
});

When this event is emitted a exponentially reconnect will start. The reconnect will attempt a reconnect after 1 minute and double the reconnect attempts exponentially.

Emitted when the connection to the Twitter Stream API throw an unexpected error which are not within the errors defined by the Twitter Stream API documentation.

Twitter.on('connection error unknown', function (error) {
    console.log('connection error unknown', error);
    Twitter.close();
});

When this event is emitted the client will, if it can, keep the connection to the Twitter Stream API and not attemt to reconnect. Closing the connection and handling a possilbe reconnect must be handled by the consumer of the client.

Emitted when a Tweet ocur in the stream.

Twitter.on('data', function (obj) {
    console.log('data', obj);
});

Emitted when the client receive a keep alive message from the Twitter Stream API. The Twitter Stream API sends a keep alive message every 30 second if no messages have been sendt to ensure that the connection are kept open. This keep alive messages are mostly being used under the hood to detect stalled connections and other connection issues.

Twitter.on('data keep-alive', function () {
    console.log('data keep-alive');
});

Emitted if the client received an message from the Twitter Stream API which the client could not parse into an object or handle in some other way.

Twitter.on('data error', function (error) {
    console.log('data error', error);
});

The MIT License (MIT)

Copyright (c) 2015 - Trygve Lie - [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.