bindings/streams library

Streams Standard

https://streams.spec.whatwg.org/

Classes

ByteLengthQueuingStrategy
Experimental: This is an experimental technologyCheck the Browser compatibility table carefully before using this in production. The interface of the Streams API provides a built-in byte length queuing strategy that can be used when constructing streams.
CountQueuingStrategy
Experimental: This is an experimental technologyCheck the Browser compatibility table carefully before using this in production. The interface of the Streams API provides a built-in chunk counting queuing strategy that can be used when constructing streams.
GenericTransformStream
QueuingStrategy
QueuingStrategyInit
ReadableByteStreamController
Experimental: This is an experimental technologyCheck the Browser compatibility table carefully before using this in production. The interface of the Streams API represents a controller allowing control of a ReadableStream's state and internal queue. Byte stream controllers are for byte streams.
ReadableStream
The interface of the Streams API represents a readable stream of byte data. The Fetch API offers a concrete instance of a through the body property of a Response object.
ReadableStreamBYOBReader
Experimental: This is an experimental technologyCheck the Browser compatibility table carefully before using this in production. The interface of the Streams API represents a BYOB ("bring your own buffer") reader that can be used to read stream data supplied by the developer (e.g. a custom ReadableStream() constructor).
ReadableStreamBYOBRequest
Experimental: This is an experimental technologyCheck the Browser compatibility table carefully before using this in production. The interface of the Streams API represents a pull request into a ReadableByteStreamController view. A view, as mentioned below, refers to a typed array representing the destination region to which the associated ReadableByteStreamController controller can write generated data.
ReadableStreamDefaultController
The interface of the Streams API represents a controller allowing control of a ReadableStream's state and internal queue. Default controllers are for streams that are not byte streams.
ReadableStreamDefaultReader
The interface of the Streams API represents a default reader that can be used to read stream data supplied from a network (e.g. a fetch request).
ReadableStreamGenericReader
ReadableStreamGetReaderOptions
ReadableStreamIteratorOptions
ReadableStreamReadResult
ReadableWritablePair
StreamPipeOptions
Transformer
TransformStream
The interface of the Streams API represents a set of transformable data.
TransformStreamDefaultController
The interface of the Streams API provides methods to manipulate the associated ReadableStream and WritableStream. When constructing a TransformStream, the is created. It therefore has no constructor. The way to get an instance of is via the callback methods of TransformStream.TransformStream().
UnderlyingSink
UnderlyingSource
WritableStream
Experimental: This is an experimental technologyCheck the Browser compatibility table carefully before using this in production. The interface of the Streams API provides a standard abstraction for writing streaming data to a destination, known as a sink. This object comes with built-in backpressure and queuing.
WritableStreamDefaultController
Experimental: This is an experimental technologyCheck the Browser compatibility table carefully before using this in production. The interface of the Streams API represents a controller allowing control of a WritableStream's state. When constructing a WritableStream, the underlying sink is given a corresponding instance to manipulate.
WritableStreamDefaultWriter
Experimental: This is an experimental technologyCheck the Browser compatibility table carefully before using this in production. The interface of the Streams API is the object returned by WritableStream.getWriter() and once created locks the writer to the WritableStream ensuring that no other streams can write to the underlying sink.