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

redindex

v0.1.0

Published

An indexed object store on Node.js and Redis

Downloads

6

Readme

redindex

An indexed object store on Node.js and Redis.

Example

We need to store message objects in Redis, where each message has properties to, id and time. Later, we need to retrieve a bunch of messages, given a recipient (to property) and a time duration.

Creating an index

Let's define an index totime on message objects.

var redindex = require("redindex");

var messages = redindex('messages', {
	indexes: {
		totime: function (msg, emit) {
			emit(msg.to, msg.time);
		}
	}
});

This is similar to CouchDB Views. Each index is defined by a function. When a message object is added to Redis, the index function is called with the inserted object. The function may calculate and emit index values.

Two kinds of index values can be emitted: strings (for performing equality comparisons) and numbers (for range comparisons and sorting). Each call to emit() may pass one or both these values - to emit a number without emitting a string, pass null as the string value.

Note: index functions must emit the same set of values when called with identical objects.

Adding data

messages.put({id: 'msg01', to: 'room1', time: 10});

Querying

messages.get({by: 'totime', str: 'room1', num: {gt: 10}}, function(err, res) {
	...
});

The get function takes a Query Object as its first parameter, and a callback as its second. The Query Object supports the following properties:

  • by: The name of the index to use.
  • str: A string value (for filtering)
  • num: A single numeric value or a comparison object (with properties lt, lte, gt, gte and eq as in MongoDB)
  • rev: If true, reverses the sort order (by default it is in increasing order of the numeric index)
  • limit, offset: Integers, used for pagination like the SQL limit clause
  • full: If true, returns the full objects (by default it returns only the ID's)

Retrieving with ID

messages.get('msg02');

Deleting objects

messages.del('msg03');

Roadmap

  • Easier querying functions: messages.totime('room1', {gt: 12})