Enables event listeners to send zero-or-one response back to the event dispatcher.
Utilizes matchMedia to performantly return conditional values based on media queries.
An implementation of WHATWG EventTarget interface.
Fire events the same way the user does
A minimal event emitter.
Simple event emitter
Creates a Promise that waits for a single event
Type-safe implementation of EventEmitter for browser and Node.js
Promisify an event by waiting for it to be emitted
Returns an object with on-event callback props curried with provided args.
Event emitter
A library to create a trace of your node app per Google's Trace Event format.
A type-safe marriage of `EventTarget` and `EventEmitter`.
No description provided.
High-priority task queue for Node.js and browsers
A shim for the setImmediate efficient script yielding API
Super light and fast Extensible ES6+ events and EventEmitters for Node and the browser. Easy for any developer level, use the same exact code in node and the browser. No frills, just high speed events!
return the first event in a set of ee/event pairs
Provides a context-saving pub/sub channel to connect diagnostic event publishers and subscribers
Loosely validate an event.
This is an internal package. Please don't use this package directly. The package will do unexpected breaking changes.
An EventTarget Polyfill
A fast, efficient Node.js Worker Thread Pool implementation
TanStack Event Bus is a lightweight event bus for TanStack Devtools.
A small extension to prawn that simplifies embedding JavaScript in your PDF files
Events octiron responds to can be any classes or Hash prototypes. Using transmogrifiers, events can be turned into other kinds of events transparently.
Eventhub provides a clean pattern for projects with a lot of event tracking / handling
Nestor watches file system events and responds by running the tests or specs that match the changed files.
This library is intended to be useful for decoupling your business logic by allowing you to trigger and respond to domain model events.
Turbine is a data application framework for building server-side applications that are event-driven, respond to data in real-time, and scale using cloud-native best practices
Greenletterrs is a console automation framework, similar to the classic utility Expect. You give it a command to execute, and tell it which outputs or events to expect and how to respond to them. Greenletters also includes a set of Cucumber steps which simplify the task of spcifying interactive command-line applications.
Amberletters is a console automation framework, similar to the classic utility Expect. You give it a command to execute, and tell it which outputs or events to expect and how to respond to them.
Framework to automate responses for infrastructure events. Ocular allows to easily create small scripts which are triggered from multiple different event sources and which can then execute scripts commanding all kinds of infrastructure, do remote command execution, execute AWS API calls, modify databases and so on. The goal is that a new script could be written really quickly to automate a previously manual infrastructure maintenance job instead of doing the manual job yet another time. Scripts are written in Ruby with a simple Ocular DSL which allows the script to easily respond to multitude different events.
This gem allows users to create Slack bots that respond to mentions. This gem only supports events-based socket mode bots. The gem allows registering a number of callbacks that will be executed if the registered regular expression matches the mention text.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.