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

node-twatch

v1.1.6

Published

> Monitor specific tweets and post to Slack.

Downloads

19

Readme

node-twatch

Monitor specific tweets and post to Slack.

node-twatch

Install

npm (global)

$ npm install node-twatch -g

clone

$ git clone [email protected]:kokushin/node-twatch.git
$ cd node-twatch
$ npm install

download here

$ unzip node-twatch-master.zip
$ cd node-twatch-master
$ npm install

Usage

Open config.json in a text editor and enter the Twitter API key and Slack's API key.

💡 When npm install node-twatch -g is executed, config.json exists in /usr/local/lib/node_modules/node-twatch.

  • How to get Twitter API key here
  • How to get Slack API key here
{
  "twitter": {
    "consumer_key": "YOUR_CONSUMER_KEY",
    "consumer_secret": "YOUR_CONSUMER_SECRET",
    "access_token_key": "YOUR_ACCESS_TOKEN_KEY",
    "access_token_secret": "YOUR_ACCESS_TOKEN_SECRET"
  },
  "slack": {
    "token": "YOUR_ACCESS_TOKEN_KEY",
    "channel": "YOUR_CHANNEL_NAME"
  }
}

When you enter the following command, Twatch starts monitoring.

💡 Twitter users to monitor must "follow".

npm (global)

$ twatch

clone & download

$ npm run twatch

Press Ctrl + C to stop monitoring.

Options

There is an option to specify the Twitter ID to be monitored and the keyword contained within tweet respectively.

-u, -user

You can specify the ID of the Twitter user to monitor. It is possible to specify more than one with ",".

npm (global)

$ twatch -u user_id1,user_id2

clone & download

$ npm run twatch -- --u user_id1,user_id2

-k, -keyword

You can specify keywords to be included in the tweets to be monitored. Uppercase and lowercase letters are not distinguished. It is possible to specify more than one with ",".

npm (global)

$ twatch -k keyword1,keyword2

clone & download

$ npm run twatch -- --k keyword1,keyword2

-l, -link

Available from v1.1.0

When this option is specified, only tweets containing links are monitored.

npm (global)

$ twatch -l

clone & download

$ npm run twatch -- --l

combine

These options can be used in combination.

npm (global)

$ twatch -u user_id1,user_id2 -k keyword1,keyword2 -l

clone & download

$ npm run twatch -- --u user_id1,user_id2 --k keyword1,keyword2 --l

💡 If you do not specify an option, we will monitor all followers and tweets.

Trouble shooting

Error: Status Code: 401

The API key is not set correctly. You need to check and edit config.json.

Error: Status Code: 420

Since the requests are concentrated, please wait for a while before running.

Contributor

@kokushin

License

Code and documentation copyright 2017 by kokushin. Code released under the MIT License.