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

@pashoo2/redis-pipeline-commander

v0.0.1

Published

Auto distribution between Redis nodes and merging a queries to pipelines. Transactions support

Readme

RedisPipelineCommander

 

With webpack-like just use* import PipeCommander from “RedisPipelineCommander”*.

With native code use import PipeCommander from “./node_modules/RedisPipelineCommander/index.js” or <script src=“./node_modules/RedisPipelineCommander/index.js”>

!Use it with nodejs and redis

 

For the first you need to do like:

import PipeCommander from 'RedisPipelineCommander';

const optionsPipelineCommander = {
    redisNodesSettings, //host and port of a redis nodes
    ioRedisOptions, //specified by the ioredis library    
    options : optionsPipelineCommander //especially for the PipelineCommander library
};
const redisClient = new PipeCommander(optionsPipelineCommander);

where:

  • redisNodesSettings {object[]} - settings for redis nodes, created with ioredis library. Like
new Redis(redisNodesSettings[i],....)
  • ioRedisOptions {object} - settings for ioredis lib
new Redis(redisNodesSettings[i],ioRedisOptions )
  • options {object} - options used by this lib

    • options.timeInterval {number} - ms, defie time interval to send a pipeline to the node

    • option.maxQueueLength {number} - max queries limit. If more, then send all queries from the queue to a redis node

 

If you use a LUA scripts you need to load them before any other command:

//list with lua scripts to load
const luaScripts = []; //[scriptName1, scriptBody1....scriptNameN, scriptBodyN]
//load lua script to the redis cache
redisClient.start //after the redis has started
        .then(function(redisClient){
            "use strict";
            for( let i = 0, len = luaScripts.length; i < len; i++ ) { //for each script that was defined
                redisClient.scriptLoad(luaScripts[i], luaScripts[++i]) //load it to the redis
                    .then(function(res){
                        if ( res !== true ) { //if an error
                            _log("Can't load script called " + luaScripts[i]);    
                        }    
                    });
            }    
        });

 

To execute a redis command just call it:

redisClient[commandName](keyDb, commandArg1....).then(result=>{}).catch(err=>{})

For LUA (can be applied only for a one key):

redisClient.scriptExec(”scriptName”, keyDb, [scriptArg1, .., scriptArgN ]).then(..).catch(..)

If you deal with a transaction (all commands of the transaction must be applied only for a one key):

redisClient.multi(dbKey, [command1...commandN]).then(results=>{...}), where

  • commandN - [ “redisCommandName”, redisCommandArgument1...redisCommandArgumentN]

    • results[ command1Result ....commandNResult ]