Mediator with dynamic responsibility chains.
The postgres client/server binary protocol, implemented in TypeScript
@wire service
isomorphic node/browser Websocket network adapter for Automerge Repo
Utility library emit test data through @wire adapters in Lightning web component tests
No description provided.
An implementation of WHATWG EventTarget interface.
Fire events the same way the user does
A minimal event emitter.
Protocol definition for generic messages.
Simple event emitter
WebSocket protocol handler with pluggable I/O
Creates a Promise that waits for a single event
Type-safe implementation of EventEmitter for browser and Node.js
i18next-http-middleware is a middleware to be used with Node.js web frameworks like express or Fastify and also for Deno.
Core LWC engine APIs.
The Phoenix LiveView JavaScript client.
Wire command types and result types for Prisma Next MongoDB support
Promisify an event by waiting for it to be emitted
Returns an object with on-event callback props curried with provided args.
A library to create a trace of your node app per Google's Trace Event format.
Event emitter
No description provided.
A type-safe marriage of `EventTarget` and `EventEmitter`.
Wires extension gem for integration with icalendar events.
YARD plugin for documenting programs using the wires event routing framework for Ruby.
Light control and button event observers for wired Buzz™ controllers in Ruby on Linux
Wires extension gem for firing and receiving events between Ruby processes with UDP multicasts.
Structure Rails apps with use cases, auto-registered dependencies, and Result objects. Features convention-based wiring, domain events with async subscribers, undo/rollback, ActiveRecord integration, and generators for scaffolds, use cases, and deps.
RJS is a great Ruby DSL to write javascript. However, it's so tempting to write RJS directly in the views, and soon the views contain substantial controller knowledge (e.g. link_to_remote, link_to, etc) KRJS attempts to solve that problem by allowing dynamic inclusion of AJAX calls on HTML elements. When a controller defines a method (based on naming convention) that handles a client-side event, the rendering engine will do the wiring automatically - when the event happens, an AJAX call will be made to the controller's method which would ideally reply with RJS and update portions of the document.
RJS is a great Ruby DSL to write javascript. However, it's so tempting to write RJS directly in the views, and soon the views contain substantial controller knowledge (e.g. link_to_remote, link_to, etc) KRJS attempts to solve that problem by allowing dynamic inclusion of AJAX calls on HTML elements. When a controller defines a method (based on naming convention) that handles a client-side event, the rendering engine will do the wiring automatically - when the event happens, an AJAX call will be made to the controller's method which would ideally reply with RJS and update portions of the document.
A pure-Ruby, zero-dependency implementation of the Vercel AI SDK "Data Stream Protocol" (UI Message Stream Protocol) — the Server-Sent-Events wire format that drives the AI SDK's useChat / useCompletion / useObject frontend hooks. The protocol is language-agnostic by design, but Ruby had no implementation; ai_stream lets a Rails/Rack backend stream text, reasoning, tool calls, sources, files, and custom data parts to a Vercel-AI-SDK frontend with the exact frames it expects. Provider-agnostic: it composes with ruby_llm, ruby-openai, or any token source instead of competing with them.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.