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

spr-node

v1.0.10

Published

<!-- * @Author: your name * @Date: 2021-09-04 08:50:04 * @LastEditTime: 2021-09-04 09:24:08 * @LastEditors: Please set LastEditors * @Description: In User Settings Edit * @FilePath: /SPR-node/README.md --> # spr-node

Downloads

2

Readme

spr-node

Make sure specific job can only be run over 1 process among different machines and different process. If some process is killed or stucked, the job will be switched to other process on some machine.

usage

npm install spr-node
import spr from "spr-node"

async function main(){
    //connect to redis first
    //If connect to redis failed, all the job will not be the master
    //InitRedis(host: string, port: number, username: string , password: string , db: number) 
    await spr.InitRedis("127.0.0.1",6379,undefined,"123456",5)

    //add job with unique job name which used in redis
    //the process with same job name will scramble for the master token
    await spr.AddJobName("testjob")
    await spr.AddJobName("testjob2")

    // use function sprJobMgr.IsMaster("jobName") to check whether the process get the master token or not
    // if return true means get the master token
    setInterval(()=>{
        console.log(new Date().toLocaleString(),"testjob is master:",spr.IsMaster("testjob"))
        console.log(new Date().toLocaleString(),"testjob2 is master:",spr.IsMaster("testjob2"))
    },1000)

    // use function sprJobMgr.RemoveJobName("jobName") to remove the job
    // removed job always return false when use sprJobMgr.IsMaster("jobName")
    setTimeout(() => {
        spr.RemoveJobName("testjob2")
    }, 30*1000);
}

main()