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

redis-scripto2

v0.2.2

Published

Redis Lua Script Manager for NodeJS

Downloads

772

Readme

node-redis-scripto2

This is a fork of redis-scripto with updated dependencies for modern Node.js. The API is identical, so if you currently use redis-scripto, you can migrate to redis-scripto2 without making any changes in your code except for the package name.

Node.js CI

Intelligent Redis Lua Script Manager for NodeJS

  • Lua Scripting on Redis (2.6+) is a killer feature
  • But using them with NodeJs is painful
  • We've to maintain lua script in JavaScript as string or load them via the filesystem manually
  • If we are looking at network performance, we've to manually invoke script load and evasha manually

Scripto manages lua scripts for you

  • You can place lua script in a directory
  • Just tell the dirname to scripto, it will take care of lua scripts
    var Scripto = require('redis-scripto2');
    var scriptManager = new Scripto(redisClient);
    scriptManager.loadFromDir('/path/to/lua/scripts');

    var keys    = ['keyOne', 'keyTwo'];
    var values  = [10, 20];
    scriptManager.run('your-script', keys, values, function(err, result) {

    });

Scripto is intelligent

  • By default scripto tries to load scripts into redis (via script load)
  • While scripts are loading, if a script invoked with .run() it will use eval and send the plaintext lua script to redis
  • After scripts loaded, if a script invoked with .run() it will use evalsha and does not send plaintext lua script
  • If the connection to redis dropped, it will remove shas and try again to load scripts once it back online

You've the control with Scripto

  • if you need to send the plaintext lua script always. use .eval() method
    scriptManager.eval('your-script', keys, values, function(err, result) {

    });
  • If you just need to load a single script, see following example
    var scriptManager = new Scripto(redisClient);
    scriptManager.loadFromFile('script-one', '/path/to/the/file');
    scriptManager.run('script-one', [], [], function(err, result) {

    });
  • If you need to load scripts just using JavaScript (without loading from the filesystem), see following example.
    var scripts = {
        'script-one': 'return 1000'
    };

    var scriptManager = new Scripto(redisClient);
    scriptManager.load(scripts);
    scriptManager.run('script-one', [], [], function(err, result) {

    });