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

rackspace-api

v0.0.7

Published

A Node.js module to help you interface the Rackspace Cloud API in your code.

Readme

rackspace-api is a Node.js module to help you interface the Rackspace Cloud API in your code.

How to get it

Clone this repository:

git clone https://github.com/GradysGhost/node-rackspace-api.git ~/node-rackspace-api

Copy the module directory to your destination project:

cp -r ~/node-rackspace-api/rackspace-api ~/your-project/nodemodules

How to use it

It's still in it's infancy right now, so you shouldn't use this in production. All the same, it should work with a standard require:

var rackApi = require("rackspace-api");

Then get yourself an instance.

var api = new rackApi(username, password, authType, authEndpoint);
  • username - Your Rackspace Cloud username
  • password - Depending on the authType value, this should either be your password or API key
  • authType - Either "api" or "password"; defaults to "password"
  • authEndpoint - Either "us" or "uk"; defaults to "us"

This will create a new Api object.

Api

api.authenticate(callback)
  • callback - A callback function taking two arguments:
    • jsonContent - The JSON response from the authentication server containing (see http://docs.rackspace.com/servers/api/v2/cs-devguide/content/auth-response-description.html)
    • serviceObjects - An object containing other objects, each one a code object representing a Rackspace Cloud API service endpoint, as described below

CloudServerOpenStackEndpoint

This object gets created internally when calling Api.authenticate.

  • listServers (callback, params) - Gets a list of servers at this endpoint
    • callback - The function to call when the transaction completes. Accepts one argument, servers, which is a list of servers.
    • params - Parameters as described in http://docs.rackspace.com/servers/api/v2/cs-devguide/content/List_Servers-d1e2078.html
  • listImages (callback, params) - Same as listServers, but with images
  • listFlavors (callback, params) - Same as above.
  • flavorDetails (id, callback) - Retrieves the details of the flavor specified by id. A list of flavor IDs can be retrieved with listFlavors.
  • imageDetails (id, callback) - Retrieves the details of the image specified by id. A list of image IDs can be retrieved with listImages.

There is more to come with this, but as stated above, this is still in very early development.