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

romis

v2.0.1

Published

Redis with promises

Downloads

14

Readme

romis

Build Status

node_redis but with promises. This exposes the exact same API as node_redis, but all the redis commands don't take callbacks and instead return promises.

Installation

npm install --save romis

Usage

var romis = require('romis'),
var Promise = require('bluebird');
var client = romis.createClient();
var log = console.log.bind(console);
var error = console.error.bind(console);

// Execute all promises
Promise.all([
    client.set("string key","string val"),
    client.hset("hash key","hastest 1", "some value"),
    client.hset(["hash key", "hashtest 2", "some other value"]),
    client.hkeys("hash key")
]).then(function(results){
    return results.pop(); // Return keys inside `hash key`
})
.then(log) // Log resulting keys
.catch(error); // Catch any errors that occured in the chain

Transitioning from node_redis to Promises

To help you move from node_redis callbacks to romisPromises, both romis and node_redis work well in parallel. You can keep your existing code base unchanged and write new code using Promises.

Using romis.fromRedis

Keep your legacy code and re-use your exisitng client instance with the fromRedis function.

// keep your legacy code unchanged
var redis = require('redis');
var client= redis.createClient();

client.hset('hash key','some field', 'some value', function(err,result){
  // do whatever
});

// re-use the redis client with romis.fromRedis
var romis = require('romis');
var romisClient = romis.fromRedis(client);
romisClient.hset('hash key','some field', 'some value')
.then(function(result){
  // hello, Promises!
})
.catch(error) {
  // handle error
}

Using the _redis property

The object returned by romis' createClient or fromRedis exposes the original node-redis object in a property called _redis. You can access this property should you need to use traditional, callback-based functions for backwards compatibility.

var romis = require('romis'),
var romisClient = romis.createClient();

// call an old-style, callback-based method
romisClient._redis.hset('hash key','some value', function(err,result){
  //
});