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

bloody-observable

v1.0.0

Published

Observable `Object`

Downloads

4

Readme

observable

browser support

https://travis-ci.org/bloodyowl/observable

install

$ npm install bloody-observable

require

var observable = require("bloody-observable")

api

observable.extend(options) > subclass

creates an observable subclass.

options.getDefaults

function that returns the default value for data, will be merged with the data. default getDefaults returns an empty object.

observable.create([data={}]) > o

creates a new observable instance. optionally takes a data argument (which, if set, must be an object). if not set, data is a new empty object.

o.get(key)

returns the value for key.

o.set({key: value, key2: value2 …})

sets value as value for key.

o.remove(key)

removes the value for key

o.toString()

returns the JSON string of the observable data.

o.valueOf()

returns the observable data.

o.on(type, listener)

listens the the type event and attaches listener to it.

o.off([type[, listener]])

stops listening :

  • if no argument is set : all events
  • if type is set : all type events
  • if type and listener are set : the listener for this type

o.emit(type[, data…])

fires synchronously the given type event, passing the data… arguments to the listeners.

o.dispatch(cb)

creates a dispatches that, for each change in the current call-stack, notifies cb(changes) with an object containing all new changes.

o.stopDispatch([cb])

stops dispatching to cb if set, otherwise removes all dispatches.

events

  • change : when any change occurs
  • add : when the change is an addition
  • remove : when the change is an deletion

NOTE : changes are fired by the .set and .remove methods.

example

var observable = require("bloody-observable")
var status = observable
  .extend({
    getDefaults : function(){
      return {
        status : null,
        label : "yo"
      }
    }
  })
  .create({
    status : 1
  })
status.on("change", function(changes){
  ui.update({
    status : changes.value
  })
})
status.dispatch(function(){

})
request.post("connect/", data)
  .then(function(xhr){
    status.set("status", JSON.parse(xhr.responseText).status)
  })
  .catch(function(){
    status.set("status", 0)
  })