Results for effect-wide-event

Wide event logging for Effect — one rich structured event per request

Ponyfill of the experimental `React.useEffectEvent` hook

The missing standard library for TypeScript, for writing production-grade software.

No description provided.

A wide-character aware text alignment function for use on the console or with fixed width fonts.

High-priority task queue for Node.js and browsers

A React helper hook for scheduling a layout effect with a fallback to a regular effect for environments where layout effects should not be used (such as server-side rendering).

A wrapper package that uses `useInsertionEffect` or a fallback for it

High-priority task queue for Node.js and browsers

Unified interfaces for common platform-specific services

Create components whose prop changes map to a global side effect

It's react's useEffect hook, except using deep comparison on the inputs, not reference equality

Platform specific implementations for the Node.js runtime

Create components whose prop changes map to a global side effect

A React hook that uses useEffect() on the server and useLayoutEffect() in the browser

Functional programming in TypeScript

Effectful AWS Lambda handler

Experimental modules for the Effect ecosystem

Core logic for the checkbox widget implemented as a state machine

An easy to use, extensible pretty-printer for rendering documents for the terminal

ESLint rule to warn against unnecessary React useEffect hooks.

OpenTelemetry integration for Effect

A Quick description of the component

A set of helpers for testing Effects with vitest

Mingle 3.3 introduced a new Events API in the form of an "Atom feed":http://www.thoughtworks-studios.com/mingle/3.3/help/mingle_api_events.html. The Mingle team and ThoughtWorks Studios are big believers in the use of Atom for exposing events. Atom is a widely used standard, and this event API style puts the issue of robust event delivery in the hands of the consumer, where it belongs. In fact, we'd argue this is the only feasible means of robust, scalable event delivery, short of spending hundreds of thousands or millions of dollars on enterprise buses and such. Atom-delivered events are cheap, scalable, standards-based, and robust. However, we do accept that asking integrators wishing to consume events to implement polling is not ideal. Writing polling consumers can be tedious. And this tedium gets in the way of writing sweet Mingle integrations. We are addressing this by publishing libraries such as this, which if effective, fully hide the mechanics of event polling from the consumer. The consumer only need worry about the processing of events. Said processing is modeled in the style of 'pipes and filters.'