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

robserve

v0.0.2

Published

Recursive object Observer

Downloads

7

Readme

Observe

Recursive Object Observer

This helps and reports back for any changes that may happen to an object, reports back the path and the value it has changed into.

This is a coffee script atm (as it's only first draft)

#testing

npm test

#how it works

parson = {name: "Tom", age: 18}

new Observe( person , function (changes, original){
  console.log(changes);
} )



person.name = "Ben";   // {value: "Ben", path: name}
person.age = 20;   // {value: 20, path: 'age'}

This should also work for recursive, and future ancestors which are added into the object.

person.children = [{name:"Joe"} , {name: "Kim"} , {name:"Tom"} ]
person.children[1].name = 'ana'; //{value: "ana", path: 'children[1].name'}

This object is especially useful when binding (one way or two-way) to listen for changes taking advantage of the native Object.observe(obj, callback) aka O.o in a recursive mode, therefore performance should be optimal.

Raise a ticket if you would like to contribute.

#What is the original parameter?

This is the default changes, which the native Object.observe uses, if you would rather use the native so be it :), this has a more details information of what has happened to a particular object, however it may be tricky when working with deep objects.