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

lenze

v1.0.3

Published

cross instance state replication with function invoking

Readme

lenze

cross instance state replication with function invoking

Usage

In thread 1:

var Lenze = require('lenze');

var lenze = Lenze(sourceStateObject, {

    // Optional, defaults to 30
    // How often to poll when there have been recent changes
    minInterval: 30,

    // Optional, defaults to 300
    // How often to poll when there have not been recent changes
    maxInterval: 300,

    // Optional, defaults to 1000
    // How long to poll at minInterval before returning to maxInterval
    dozeInterval: 300,

    // How to send updates
    send: function(data){
        self.postMessage(data);
    },

    // How to receive invocations/connects
    receive: function(callback){
        self.addEventListener('message', function(message){
            callback(message.data);
        });
    }
});

state.x = 10;

state.doSomething = function(x){
    console.log(x);
};

In main thread:

var Lenze = require('../../');

var worker = new Worker("thread1.js");

var lenze = Lenze.replicant(targetStateObject, {

    // How to recieve updates/state
    receive: function(callback){
        worker.addEventListener('message', function(message){
            callback(message.data);
        });
    },

    // How to send invocations/connects
    send: function(data){
        worker.postMessage(data);
    }
});

// Called when the replicant gets state/change for the first time.
lenze.on('ready', function(){

    // This will cause 'dooby' to be logged in the first thread.
    lenze.state.doSomething('dooby');

});

// Called when any state changes within the lenze. (probably often);
lenze.on('change', function(){

    console.log(lenze.state);

});

Notes

  • Instance references (objects/function) are maintained.

This is a very experimental. The code is very messy and not optimised. There are many TODOs floating around my head.