Mixing in EventEmitter2 about eventemitter2 HOT 6 CLOSED

This is simply an oversight on my part. I'd like it to work more like the native eventemitter, that's the end goal.

from eventemitter2.

Oh, duh. EventEmitter2.call(this); // or w/args, works fine.

from eventemitter2.

Yea but you can not mix it in like in Node:

util.inherits(Agent, EventEmitter);

So if you want to "inherit" the functions of EventEmitter2 on - let's say - Agent you have to call EventEmitter2 with the scope of Agent in Agent's constructor. If you want to mix in Agent into another object you have to do that same thing on the that other object.

util.inherits in Node.js simply copies the prototype of one object to the other. So the constructor setup like EventEmitter2 uses right now doesn't work correctly because the constructor does not get fired.

from eventemitter2.

The .call or .apply that I pointed out allows for what you're trying to do with sys.inherits

from eventemitter2.

Still not working for me.

var EventEmitter2 = require('eventemitter2').EventEmitter2;

function Backend(endpoint, http, ws) {
  EventEmitter2.call(this);

  this.endpoint = http;
  this.http = http;
  this.ws = ws;
}

module.exports = Backend;

var Backend = require('../../src/backend');
var backend = new Backend();
console.log(typeof backend.on);
// -> undefined

Anyway this is a quite common use case, definitely consider to document it at least.

from eventemitter2.

I ran into this too. I was looking to "upgrade" from EventEmitter to EventEmitter2 because of the onAny support but my code uses util.inherits. It's not a problem to refactor my code, but it caught me by surprise as I was expecting a drop-in replacement.

EDIT: On further investigation, the issues I'm seeing may be completely unrelated..

from eventemitter2.