Reactive UI construction with simplicity and minimal magic
Transform JSX into stream-dom function calls
erre plugin to stream DOM events
React package for working with the DOM.
Create a stream that emits events from multiple other streams
Node.js Streams, a user-land copy of the stream library from Node.js
construct pipes of streams of events
Check if something is a Node.js stream
Get a stream as a string, Buffer, ArrayBuffer or array
Streaming utilities for AI assistants
tar-stream is a streaming tar parser and generator and nothing else. It operates purely using streams which means you can easily extract/parse tarballs without ever hitting the file system.
A writable stream that writes to the console
Call a callback when a readable/writable/duplex stream has completed or failed.
destroy a stream if possible
Toggle the CLI cursor
Get and validate the raw body of a readable stream.
A CSS-inspired language to select, sequence, and compose DOM events.
A tiny, zero-dependency yet spec-compliant asynchronous iterator polyfill/ponyfill for ReadableStreams.
Streaming data for JavaScript
A micro-library of stream components for building custom JSON and JSONC processing pipelines with a minimal memory footprint — parse, filter, and transform JSON far larger than available memory with a SAX-inspired token API, on Node.js or Web Streams.
Read stream input and render them to web page.
A streaming way to send data to a Node.js Worker Thread
A stream that emits multiple other streams one after another.
minimal implementation of a PassThrough stream
Take full control of the DOM with Turbo Streams
Take full control of the DOM with Turbo Streams
A “minion” for Turbo-Frames and Streams. This custom element transitions elements as they enter or leave the DOM.
Streams Lenex v3 swim data without building a DOM.
Scrapetor is a Ruby HTML parsing + scraping toolkit. The parser is a native C arena DOM with structural indexes built at parse time and NEON SIMD scanners in the SAX hot loop. A streaming extraction engine compiles the schema DSL into a single forward pass — no DOM materialised, one Ruby boundary crossing per document. On builds where libcurl is available, Scrapetor::Fetcher adds an HTTP/2-capable fetch layer with per-thread connection cache, shared DNS + TLS session pool, in-process gzip / deflate / brotli / zstd decoding, iconv charset transcoding, retry + exponential backoff, ETag / Last-Modified disk cache with bulk revalidation, per-host throttle, cookie jar, basic + bearer auth, proxy, and three bulk concurrency models (parallel_fetch / multi_fetch / streaming multi_each). Scrapetor::Session ties the cookie / auth / throttle / retry policies together. Also ships robots.txt + sitemap.xml parsers, a bounded-memory streaming HTML parser, and structured-data extractors (JSON-LD, OpenGraph, Schema.org, Microdata, RDFa, Twitter Cards). The Net::HTTP-based Scrapetor.fetch is preserved as the no-libcurl fallback.
Auto-syncs records in client-side JS (through a Model DSL) from changes (updates/destroy) in the backend Rails server through ActionCable. Also supports streaming newly created records to client-side JS. Supports lost connection restreaming for both new records (create), and record-changes (updates/destroy). Auto-updates DOM elements mapped to a record attribute, from changes (updates/destroy).
Ikura is a minimal Turbo Stream implementation built from scratch using Ruby Wasm and Ruby's built-in TCPServer — no Rails, no frontend framework, no external runtime dependencies. Click anywhere on the gunkan-maki sushi in the browser to place ikura (salmon roe); click events run in Ruby via WebAssembly and DOM updates arrive as Turbo Streams.
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.