async-stream-emitter
Advanced tools
Comparing version 3.0.2 to 3.0.3
{ | ||
"name": "async-stream-emitter", | ||
"version": "3.0.2", | ||
"version": "3.0.3", | ||
"description": "An alternantive to EventEmitter using consumable streams.", | ||
"main": "index.js", | ||
"scripts": { | ||
"build": "gulp browserify; gulp minify", | ||
"test": "./node_modules/mocha/bin/_mocha --reporter spec --timeout 10000 --slow 10000" | ||
@@ -28,3 +29,16 @@ }, | ||
"devDependencies": { | ||
"mocha": "^5.2.0" | ||
"@babel/core": "^7.2.2", | ||
"@babel/preset-env": "^7.2.3", | ||
"babel-plugin-minify-dead-code-elimination": "^0.5.0", | ||
"browserify": "^16.2.3", | ||
"gulp": "^4.0.0", | ||
"gulp-babel": "^8.0.0", | ||
"gulp-cli": "^2.0.1", | ||
"gulp-convert-newline": "^0.0.3", | ||
"gulp-insert": "^0.5.0", | ||
"gulp-rename": "^1.4.0", | ||
"gulp-uglify": "^3.0.1", | ||
"mocha": "^5.2.0", | ||
"uglify-es": "^3.3.9", | ||
"vinyl-source-stream": "^2.0.0" | ||
}, | ||
@@ -31,0 +45,0 @@ "dependencies": { |
# async-stream-emitter | ||
EventEmitter using ConsumableStream. | ||
## Methods: | ||
## Main methods: | ||
@@ -10,2 +10,6 @@ - emit(eventName, data) | ||
- closeAllListeners() | ||
- killListener(eventName) | ||
- killAllListeners() | ||
- getListenerBackpressure(eventName) | ||
- getAllListenersBackpressure() | ||
@@ -43,7 +47,1 @@ ## Usage examples | ||
``` | ||
Note that unlike with `EventEmitter`, you cannot get the count for the number of active listeners at any given time. | ||
This is intentional as it encourages code to be written in a more declarative style and lowers the risk of memory leaks. | ||
If you want to track listeners, you should do it yourself. | ||
The new ECMAScript `Symbol` type should make tracking object references easier: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
34004
8
690
14
46
4
1