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

state-monitor

v1.0.0

Published

state-monitor ---

Downloads

2

Readme

state-monitor

Caveman approach to state monitoring. Doesn't use proxies & does not modify the objects/values in any way. It's just a periodic diff of values returned by provided resolver function.

In short

const monitor = stateMonitor(resolverFunction, refreshRateInMilliseconds)
monitor.on('change', changeHandler) // changeHandler receives structural difference info returned from 'deep-diff' npm module
// to stop
monitor.emit(‘stop’)

Note: in the usage example below you can see the usage of describeDiff helper function for human friendly change logs

Usage example

import stateMonitor from 'state-monitor'

let a = {
  name: 'my object',
  description: 'it\'s an object!',
  details: {
    it: 'has',
    an: 'array',
    with: ['a', 'few', 'elements']
  }
}

const mon = stateMonitor(() => a, 10) // check for difference every 10 milliseconds
mon.on('change', stateMonitor.describeDiff) // helper function for logging changes

a = {
  name: 'updated object',
  description: 'it\'s an object!',
  details: {
    it: 'has',
    an: 'array',
    with: ['a', 'few', 'more', 'elements', { than: 'before' }]
  }
}

// this should output something like:

/* change
EDITED 'name': my object -> updated object
EDITED 'details.with.2': elements -> more
ALTERED at index: 3
NEW: undefined -> elements
ALTERED at index: 4
NEW: undefined -> {"than":"before"}
*/

// stop monitoring
monitor.emit(‘stop’)

Libraries used

  • immutablejs for taking state "snapshots"
  • deep-diff for diffing snapshots
  • eventemitter2 to emit changes