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 🙏

© 2026 – Pkg Stats / Ryan Hefner

corvo-node-client

v1.0.1

Published

A node.js client for CorvoStore.

Readme

Summary

Corvo client is a Node.js client library intended to be used with CorvoStore.

Installation

Installing the NPM module with the Command Line

Install the module with the following command:

$ npm install corvo-node-client

Then, navigate to the following directory:

cd ~/node_modules/corvo-node-client

And then make sure to execute the following command:

$ npm install

Usage Example

require('./node_modules/corvo-node-client');

const client = new CorvoNodeClient();

client.hmset("key1", "field1", "value1", "field2", "value2").then((response) => {
  console.log(response);
});
client.hgetall("key1").then((response) => {
  console.log(response);
});
client.hlen("key1").then((response) => {
  console.log(response);
});
client.hsetnx("key1", "field2", "updated-value").then((response) => {
  console.log(response);
  client.destroyClient();
});

Running the code above in a file, as in the following, will display:

$ node example.js

OK
[ 'field1', 'value1', 'field2', 'value2' ]
2
0

This API is asynchronous, and uses promises to retrieve data from the server. Each CorvoStore command is available as a method on the client object. Every method takes a list of individual arguments matching the possible number of arguments for that command. The methods each return a JS Promise that resolves to the value returned by the server. The return value itself can be accessed inside the .then callback after invoking the method, as shown in the usage example above.

Supported Commands

Corvo client supports the following commands for each data type:

String

  • get
  • set
  • append
  • strlen
  • incr
  • decr

List

  • lpush
  • rpush
  • lindex
  • lrem
  • llen
  • linsert
  • lpop
  • rpop
  • lset

Hash

  • hkeys
  • hvals
  • hstrlen
  • hmset
  • hdel
  • hget
  • hgetall
  • hlen
  • hsetnx
  • hmget
  • hincrby
  • hset

Set

  • sadd
  • scard
  • sismember
  • spop
  • srem
  • smembers
  • sunion
  • sinter
  • sdiff
  • sunionstore
  • sinterstore
  • sdiffstore

Sorted Set

  • zincrby
  • zadd
  • zscore
  • zrem
  • zcard
  • zinterstore
  • zunionstore

It also supports the following commands for CorvoStore keys in general:

  • del
  • touch
  • exists
  • rename
  • renamenx
  • type

These commands are intended to function the same way as the Redis commands that correspond to them. Please see the Redis command reference for full details on how each command operates.