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

twitterer.js

v0.0.6

Published

A Twitter API wrapper

Readme

twitterer.js

A light Twitter API wrapper that makes use of native promises. Works for both the User and Application only workflows.

Instalation

$ npm i twitterer.js

Usage

Application:

const { Application } = require('twitterer.js')
const app = new Application({
  consumerKey: '-',
  consumerSecret: '-',
  accessToken: '-' // Optional
})

As Twitter does not expire access tokens, you can provide one at instance creation. If you do so, the application won't have to go through the extra authentication step. Likewise, if you provide the access token, there is no need to provide the first 2 keys.

After creation, you may use the helper methods get, post and delete to hit the endpoints exposed by the Twitter API.

app.get('search/tweets', { params: { q: 'stuff' } }).then(console.log)

User:

const { User } = require('twitterer.js')
const user = new User({
  consumerKey: '-',
  consumerSecret: '-',
  accessToken: '-',
  accessTokenSecret: '-'
})

In this case, all keys are required.

user.get('account/settings').then(console.log)

Making requests

We have used Axios as our HTTP client, so the request API is directly inherited from it. You can specify any of the configuration fields offered by Axios, however, some of them, such as the Authorization header, will be overwritten.

Stream API

The User class offers access to the stream endpoints as follows:

user.stream('statuses/filter', { params: { track: 'stuff' } }).then(stream => {
  stream.on('tweet', console.log)
})

This hasn't been tested much and is subject to changes.

Contributing

This a very early build of this package, so issues/PRs are most welcome.