observe-event [![NPM version][npm-image]][npm-url] [![Build Status][travis-image]][travis-url] [![Dependency Status][depstat-image]][depstat-url]

> Make Object.observe emit events on every change

Object.observe is finally here and everyone is excited, but simply giving
one callback the observe can make it hard to manage and re-use observations.

This simple Object.observe wrapper will return an event emitter
instead that allows us to specify what type of change we want
and passing the emitter around. If we want to catch all type of
changes, we can do that too.

API

``javascript
eObserve(object[, optAcceptList]) : EventEmitter
`

optAcceptList defines what type of changes to listen to.
If not defined, it defaults to all changes (see below).




$3

The event emitter returned from eObserve(), emits changes
made to the observed object in a channel that is the same
as the type of change.

For instance:
`javascript
eObserve(object).on('update', callback);
`

In addition to all types of changes as defined by the spec, a special channel exists to catch any change:

`javascript
// Will trigger on any change
eObserve(object).on('any', callback);
`

#### Event overview
* any – Triggered for all of the below
* add
* update
* delete
* reconfigure
* setPrototype
* preventExtensions

See the harmony specs
for more information of the different changes

Install

$3

`shell
npm install --save observe-event
`

$3

`shell
bower install --save observe-event
`

$3

Download observe-event.js or
observe-event.min.js from the dist folder
and include in your HTML. See below for more details.

Usage

$3

`
var eObserve = require('observe-event');

var obj = { message: 'Hello World!' };
eObserve(obj).on('update', function (change) {
// => change.object.message = 'Hello, World!'
});

obj.message = 'Hello, World!';
`

See example




$3

`html

`

`javascript

var obj = { message: 'Hello World!' };
eObserve(obj).on('update', function (change) {
// => change.object.message = 'Hello, World!'
});

obj.message = 'Hello, World!';
`

See example.




$3

Not yet tested with AMD

Files observe-event.js and
observe-event.min.js is wrapped
with UMD (Universal Module Definition), so it should
work with AMD as well as directly loading in the browser.

`javascript

require(['observe-event'], function(eObserve) {
var obj = { message: 'Hello World!' };
eObserve(obj).on('update', function (change) {
// => change.object.message = 'Hello, World!'
});

obj.message = 'Hello, World!';
});
``

Changelog

$3

1. Changes from having a single file with UMD in it, to use a build step creating seperate distribution files.
2. No longer have external dependencies (EventEmitter.js).
3. For AMD and Browser you now need to use either observe-event.js or observe-event.min.js.

License

MIT License

[npm-url]: https://npmjs.org/package/observe-event
[npm-image]: http://img.shields.io/npm/v/observe-event.svg?style=flat
[npm-downloads]: http://img.shields.io/npm/dm/observe-event.svg?style=flat

[travis-url]: http://travis-ci.org/mikaelbr/observe-event
[travis-image]: http://img.shields.io/travis/mikaelbr/observe-event.svg?style=flat

[depstat-url]: https://gemnasium.com/mikaelbr/observe-event
[depstat-image]: http://img.shields.io/gemnasium/mikaelbr/observe-event.svg?style=flat