Problems requiring EventEmitter2 in browser #43

Activity

1. sokra commented on Dec 2, 2012

   

   sokra

   on Dec 2, 2012

   Member

   More actions

   It does work for me.

   My testcase (test.js):

   var ee = require("./lib/eventemitter2");
   document.write(ee.toString());
   var test = new ee();
   document.write("<br>");
   document.write(JSON.stringify(test));

   webpack-dev-server test.js
   

   http://localhost:8080

   function EventEmitter(conf) { this._events = {}; this.newListener = false; configure.call(this, conf); }
   {"_events":{},"newListener":false}
   

   ---

   It is exported by the AMD part of the module:

   // ...
     if (typeof define === 'function' && define.amd) {
       define(function() {
         return EventEmitter;
       });
     } else {
       exports.EventEmitter2 = EventEmitter; 
     }
   // ...

   This means it exports {EventEmitter2: function() {/*...*/}} in node.js through the CommonJs part and function() {/*...*/} in the AMD part. This is a bit weird in the library.

   You can import it with var ee2Lib = require("eventemitter2"), EventEmitter2 = ee2Lib.EventEmitter2 || ee2Lib; to support both types of exports.
2. sokra commented on Jan 23, 2013

   

   sokra

   on Jan 23, 2013

   Member

   More actions

   I close this issue, please reopen if you still have an issue...
3. sokra

   closed this as completedon Jan 23, 2013
4. alexander-akait

   added 3 commits that reference this issue on Sep 4, 2026

   fix(html): read a `<script type>` decoded, and trim an inline script

   ...

   622e89f

   fix(html): drop the inline-script trim, keep the decoded type

   ...

   2a65a95

   fix(html): read a <script type> decoded, and trim an inline script (#…

   ...

   f2581d3