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

change-treadmill

v0.1.0

Published

A zero-allocation change detection library for plain javascript objects.

Downloads

3

Readme

The Treadmill

A zero-allocation change detection library for plain javascript objects.

Usage

"use strict";
var Treadmill = require('change-treadmill');

Treadmill.start();

var test = {
	foo: 'bar'
}

Treadmill.observe(test);

Treadmill.changes.each(function(change){
	console.log(change.obj, change.field, change.lastValue, change.getter())
});

test.baz = 'new prop'
test.foo = 'changed prop'

Treadmill.unObserve(test);
Treadmill.pause();
{foo: 'bar'}  size  1 2
{foo: 'bar'}  baz  undefined 'new prop'
{foo: 'bar', baz: 'new prop'} foo 'bar' 'changed prop'

But won't this be slow?

Nope, care has been taken to make sure that the only time this allocates is when it needs to monitor a new property. So it is GC Stable, this is; it does not cause any memory pressure while it runs. On a modern desktop in a modern VM this will use well less than 1% cpu even with hundreds of watched properties. But be aware that because it uses a runloop, change notifications are not instant, but certainly should be within 100ms of the change. 100ms response is about what is needed for a user to feel that something was 'instant'.