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 🙏

© 2025 – Pkg Stats / Ryan Hefner

node-twitter-bot

v0.1.0

Published

Node Twitter Bot

Downloads

5

Readme

Node Twitter Bot

Join the chat at https://gitter.im/nikolenkoanton92/node-twitter-bot

This version is Unstable, You can use for fun.

Installation

The easiest way to install node-twitter-bot is with npm

npm install node-twitter-bot

Alternately, download the source.

git clone https://github.com/nikolenkoanton92/node-twitter-bot.git

Features

  • follow users by tweet
  • follow user by specified user
  • unfollow users

Usage

You will also need to create an app account on https://dev.twitter.com/apps

  • Sign in with your Twitter account
  • Create a new app account
  • Modify the settings for that app account to allow read & write
  • Generate a new OAuth token with those permissions

Following these steps will create 4 tokens that you will need to place in the configuration file discussed below.

consumerKey , consumerSecret , accessToken , accessTokenSecret are your API keys that you received from creating your app account.

var  NodeTwitterBot = require('node-twitter-bot');

var nodeTwitterBot = new NodeTwitterBot({
  consumerKey : 'Your Consumer Key',
  consumerSecret : 'Your consumer Secret',
  accessToken : 'Your access Token',
  accessTokenSecret : 'Your access Token Secret'
});

API

This API should work exactly the same in node. Open an issue if this is not the case.

nodeTwitterBot.followByTweets(phrase,[options])

Start following people by phrase in tweet.

If options is specified, then the default options(shown bellow) will be overridden.

{
  result_type: String, // Specifies what type of search results you would prefer to receive. By default : popular. You can change to recent, popular, mixed.
  count: Number, // The number of tweets to return per page, up to a maximum of 100. Defaults to 15.
}

nodeTwitterBot.followByUser(user,[options])

Start following peoply by 'user name'(should be String) in tweet.

if options is specified, the the default options(show bellow) will be overridden.

{
  count: Number, // Maximum of 5,000 per distinct request. Defaults to 15.
  file : {
    save : true, // if you would like save followers to file add true, by default it is false.
    fileName:  'file name of the file' // set filename of file
  }
}

nodeTwitterBot.unfollowAll(user,[options])

Start unfollowing people.

user can be any of the following:

  • the ID of the user for whom to return results for.
  • the screen name of the user for whom to return results for.