- Notifications
You must be signed in to change notification settings - Fork174
Node's event emitter for all engines.
License
browserify/events
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Node's event emitter for all engines.
This implements the Node.jsevents
module for environments that do not have it, like browsers.
events
currently matches theNode.js 11.13.0 API.
Note that theevents
module uses ES5 features. If you need to support very old browsers like IE8, use a shim likees5-shim
. You need both the shim and the sham versions ofes5-shim
.
This module is maintained, but only by very few people. If you'd like to help, let us know in theMaintainer Needed issue!
You usually do not have to installevents
yourself! If your code runs in Node.js,events
is built in. If your code runs in the browser, bundlers likebrowserify orwebpack also include theevents
module.
But if none of those apply, with npm do:
npm install events
varEventEmitter=require('events')varee=newEventEmitter()ee.on('message',function(text){console.log(text)})ee.emit('message','hello world')
See theNode.js EventEmitter docs.events
currently matches the Node.js 11.13.0 API.
PRs are very welcome! The main way to contribute toevents
is by porting features, bugfixes and tests from Node.js. Ideally, code contributions to this module are copy-pasted from Node.js and transpiled to ES5, rather than reimplemented from scratch. Matching the Node.js code as closely as possible makes maintenance simpler when new changes land in Node.js.This module intends to provide exactly the same API as Node.js, so features that are not available in the coreevents
module will not be accepted. Feature requests should instead be directed atnodejs/node and will be added to this module once they are implemented in Node.js.
If there is a difference in behaviour between Node.js'sevents
module and this module, please open an issue!
About
Node's event emitter for all engines.