Core package for the Strongly Typed Events projects. This project adds events to your projecs. Because events can have multiple flavours, we've created multiple packages.
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 | 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 | A simpler version of the ste-event-event. No sender, just an argument. |
ste-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 is maintained by Kees C. Bakker.
FAQs
Core files for the Strongly Typed Events project.
The npm package ste-core receives a total of 7,594 weekly downloads. As such, ste-core popularity was classified as popular.
We found that ste-core demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
