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

heroku-legacy

v0.1.4

Published

Heroku legacy API client for NodeJS

Downloads

20

Readme

node-heroku-api

Port of heroku-api gem to NodeJS.

Installation

$ npm install heroku-legacy

Usage

The API is exactly the same, with the following differences:

  • All the methods take a callback of the following form: function (err, body) where err is one of the error defined in src/errors.coffee if any, or null otherwise and body is the JSON response.
  • All the methods are camelCased.
  • When using the username/password constructor, the object should be used in the callback, and not as the return value.

Here is a short example (in CoffeeScript).

With username/password:

HerokuApi = require 'heroku-legacy'
new HerokuApi username: '[email protected]', password: 'password', (err, api) ->
  return handleError(err) unless err == null
  api.getApps (err, apps) ->
    return handleError unless err == null
    console.log apps

With API key:

HerokuApi = require 'heroku-legacy'
api = new HerokuApi apiKey: 'my-api-key'
api.getApps (err, apps) ->
  return handleError(err) unless err == null
  console.log apps