expose .on and .emit after initialization

[yoshuawuyts]

not recommending to do things dynamically, but being able to pass around an instance is neat.

[yoshuawuyts]

Removes the need for a large up-front object of requirements

[yoshuawuyts]

possibly leverage the .on('foo:bar:bin:baz', () =>) shiz; or just .on('foo:bar', () =>)

[yoshuawuyts]

const barracks = require('barracks')

const d = barracks()
d.on('courses:get', () => console.log('whoop!')
d.on('courses:post', (ev, data, wait) => wait(['foobar', 'binbaz']))

d('courses:post', {my: 'data'})

[yoshuawuyts]

• remove payload delegation (only direct passing of stuff)
• remove dependance on this
• next should be optional
• waitFor === next

[yoshuawuyts]

could also turn wait into an object with yieldable values. E.g. going the co route

[yoshuawuyts]

Or just make wait return a Promise, so it can be yielded through Babel. Mwhehhhhh

[yoshuawuyts]

Should also be infinitely nestable, like with wayfarer.

[yoshuawuyts]

We should probably leverage mounting semantics as outlined in https://github.com/yoshuawuyts/wayfarer/issues/12, making this the data transport counterpart to wayfarer.

[yoshuawuyts]

Closed in 138aeac