Gathering detailed insights and metrics for strongly-typed-events
Gathering detailed insights and metrics for strongly-typed-events
Gathering detailed insights and metrics for strongly-typed-events
Gathering detailed insights and metrics for strongly-typed-events
ste-core
Core files for the Strongly Typed Events project.
ste-simple-events
Add the power of Simple Events to your projects. Every event has an argument with its data.
ste-events
Add the power of Events to your projects. They are styled after .Net using a sender and arguments.
sub-events
Lightweight, strongly-typed events, with monitored subscriptions.
Add the power of events to your projects. We even have 3 flavors for you! Each in their own package.
npm install strongly-typed-events
Typescript
Module System
Min. Node Version
Node Version
NPM Version
TypeScript (89.55%)
HTML (5.6%)
JavaScript (4.23%)
PowerShell (0.62%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
139 Stars
747 Commits
14 Forks
7 Watchers
6 Branches
9 Contributors
Updated on Mar 14, 2025
Latest Version
3.0.11
Package Id
strongly-typed-events@3.0.11
Unpacked Size
16.74 kB
Size
4.31 kB
File Count
5
NPM Version
lerna/7.1.4/node@v18.17.0+x64 (win32)
Node Version
18.17.0
Published on
Aug 09, 2023
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Add the power of events to your projects. We even have 3 flavors for you.
This project gives you the following event types:
sender
and an argument
object. If you use typescript, you can implement them using generics.An example says more than a 1000 words. Imagine if you have events like this on your class:
1let clock = new Clock("Smu", 1000); 2 3//log the ticks to the console - this is a signal event 4clock.onTick.subscribe(() => console.log("Tick!")); 5 6//log the sequence parameter to the console - this is a simple event 7clock.onSequenceTick.subscribe(s => console.log(`Sequence: ${s}`)); 8 9//log the name of the clock and the tick argument to the console - this is an event 10clock.onClockTick.subscribe((c, n) => 11 console.log(`${c.name} ticked ${n} times.`) 12);
So let's look at the implementation from a TypeScript perspective. (Do you program NodeJs without typescript? Check this)
1import { SignalDispatcher, SimpleEventDispatcher, EventDispatcher } from "strongly-typed-events"; 2 3class Clock { 4 private _onTick = new SignalDispatcher(); 5 private _onSequenceTick = new SimpleEventDispatcher<number>(); 6 private _onClockTick = new EventDispatcher<Clock, number>(); 7 private _ticks: number = 0; 8 9 constructor(public name: string, timeout: number) { 10 setInterval(() => { 11 this._ticks += 1; 12 this._onTick.dispatch(); 13 this._onSequenceTick.dispatch(this._ticks); 14 this._onClockTick.dispatch(this, this._ticks); 15 }, timeout); 16 } 17 18 public get onTick() { 19 return this._onTick.asEvent(); 20 } 21 22 public get onSequenceTick() { 23 return this._onSequenceTick.asEvent(); 24 } 25 26 public get onClockTick() { 27 return this._onClockTick.asEvent(); 28 } 29}
You can stop events from being propagated.
1let dispatcher = new SignalDispatcher(); 2 3 let a = 0; 4 dispatcher.sub(ev => { 5 a++; 6 if (a > 2) { 7 ev.stopPropagation(); 8 } 9 }); 10 11 let b = 0; 12 dispatcher.sub(() => { b++; }); 13 14 dispatcher.dispatch(); 15 dispatcher.dispatch(); 16 dispatcher.dispatch(); 17 dispatcher.dispatch(); 18 19 // a should be 4, because 4 dispatches are done."); 20 // b should be 2, because events after the 2nd dispatch are stopped." 21
The project is separated into multiple packages, so you only need to include what you need. We have the following packages:
Package | Description |
---|---|
ste-core | Package that contains all the building blocks for the creation of events. The dispatcher implementation is its main hero. |
ste-events or ste-promise-events | Events that are modeled after .Net with a sender and argument . If you use typescript, you can leverage the support for generics and get strongly typed code. |
ste-simple-events or ste-promise-simple-events | A simpler version of the ste-event -event. No sender, just an argument. |
ste-signals or ste-promise-signals | A signal is even simpler, it is just a callback for when you need to be alerted without any scope. |
strongly-typed-events | This package includes everything. |
ste-browser | Helps to host events in the browser. |
This project will help you to add events, event handling en event dispatching to your classes. To get you started, check:
Check the documentation or the examples for more information.
The change history can be found here.
This project is maintained by Kees C. Bakker.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/17 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
20 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More