web-streams-polyfill
Advanced tools
Package description
The web-streams-polyfill package is a polyfill for the Streams API, which provides a standard interface for representing and handling a sequence of data in JavaScript. This polyfill allows developers to use the Streams API in environments where it is not natively supported.
ReadableStream
This feature allows you to create a stream of data that can be read in chunks. The code sample demonstrates how to create a simple ReadableStream that enqueues two chunks of data and then closes the stream.
const readableStream = new ReadableStream({
start(controller) {
controller.enqueue('Hello, ');
controller.enqueue('World!');
controller.close();
}
});
readableStream.getReader().read().then(({ value, done }) => {
if (!done) console.log(value);
});WritableStream
This feature allows you to create a stream where data can be written. The code sample shows how to create a WritableStream and write a chunk of data to it, then close the stream.
const writableStream = new WritableStream({
write(chunk) {
console.log(chunk);
},
close() {
console.log('Stream closed');
}
});
const writer = writableStream.getWriter();
writer.write('Hello, World!').then(() => writer.close());TransformStream
This feature allows you to create a stream that transforms data as it passes through. The code sample demonstrates how to create a TransformStream that converts chunks of text to uppercase and then pipes data from a ReadableStream through it to a WritableStream.
const uppercaseTransform = new TransformStream({
transform(chunk, controller) {
controller.enqueue(chunk.toUpperCase());
}
});
const readable = new ReadableStream({
start(controller) {
controller.enqueue('hello');
controller.enqueue('world');
controller.close();
}
});
const writable = new WritableStream({
write(chunk) {
console.log(chunk);
}
});
readable.pipeThrough(uppercaseTransform).pipeTo(writable);This package is a browserify version of the Node.js core streams module. It provides similar functionality for handling streams of data but is designed to mimic Node.js streams specifically, rather than implementing the Web Streams API.
This package is a mirror of the Streams API from Node.js for use in browsers and other environments. It is similar to web-streams-polyfill but focuses on Node.js compatibility and may have differences in API and behavior compared to the Web Streams API.
While not a direct alternative to web-streams-polyfill, blob-polyfill provides Blob support in browsers that do not natively support the Blob constructor. It can be used in conjunction with streams to handle binary data.
Changelog
Readme
Web Streams, based on the WHATWG spec reference implementation.
This library comes in multiple variants:
web-streams-polyfill: a polyfill that replaces the native stream implementations.
Recommended for use in web apps supporting older browsers through a <script> tag.web-streams-polyfill/es6: a polyfill targeting ES2015+ environments.
Recommended for use in web apps supporting modern browsers through a <script> tag.web-streams-polyfill/es2018: a polyfill targeting ES2018+ environments.web-streams-polyfill/ponyfill: a ponyfill that provides
the stream implementations without replacing any globals.
Recommended for use in legacy Node applications, or in web libraries supporting older browsers.web-streams-polyfill/ponyfill/es6: a ponyfill targeting ES2015+ environments.
Recommended for use in Node 6+ applications, or in web libraries supporting modern browsers.web-streams-polyfill/ponyfill/es2018: a ponyfill targeting ES2018+ environments.
Recommended for use in Node 10+ applications.Each variant also includes TypeScript type definitions, compatible with the DOM type definitions for streams included in TypeScript.
Usage as a polyfill:
<!-- option 1: hosted by unpkg CDN -->
<script src="https://unpkg.com/web-streams-polyfill/dist/polyfill.min.js"></script>
<!-- option 2: self hosted -->
<script src="/path/to/web-streams-polyfill/dist/polyfill.min.js"></script>
<script>
var readable = new ReadableStream();
</script>
Usage as a Node module:
var streams = require("web-streams-polyfill/ponyfill");
var readable = new streams.ReadableStream();
Usage as a ES2015 module:
import { ReadableStream } from "web-streams-polyfill/ponyfill";
const readable = new ReadableStream();
The polyfill and ponyfill variants work in any ES5-compatible environment that has a global Promise.
If you need to support older browsers or Node versions that do not have a native Promise implementation
(check the support table), you must first include a Promise polyfill
(e.g. promise-polyfill).
The polyfill/es6 and ponyfill/es6 variants work in any ES2015-compatible environment.
The polyfill/es2018 and ponyfill/es2018 variants work in any ES2018-compatible environment.
Async iterable support for ReadableStream is available in all variants, but requires an ES2018-compatible environment or a polyfill for Symbol.asyncIterator.
WritableStreamDefaultController.signal is available in all variants, but requires a global AbortController constructor. If necessary, consider using a polyfill such as abortcontroller-polyfill.
Reading with a BYOB reader is available in all variants, but requires ArrayBuffer.prototype.transfer() or structuredClone() to exist in order to correctly transfer the given view's buffer. If not available, then the buffer won't be transferred during the read.
The polyfill implements version 4dc123a (13 Nov 2023) of the streams specification.
The polyfill is tested against the same web platform tests that are used by browsers to test their native implementations. The polyfill aims to pass all tests, although it allows some exceptions for practical reasons:
es2018 variant passes all of the tests.es6 variant passes the same tests as the es2018 variant, except for the test for the prototype of ReadableStream's async iterator.
Retrieving the correct %AsyncIteratorPrototype% requires using an async generator (async function* () {}), which is invalid syntax before ES2018.
Instead, the polyfill creates its own version which is functionally equivalent to the real prototype.es5 variant passes the same tests as the es6 variant, except for various tests about specific characteristics of the constructors, properties and methods.
These test failures do not affect the run-time behavior of the polyfill.
For example:
name property of down-leveled constructors is incorrect.length property of down-leveled constructors and methods with optional arguments is incorrect.The type definitions are compatible with the built-in stream types of TypeScript 3.3.
Thanks to these people for their work on the original polyfill:
FAQs
Web Streams, based on the WHATWG spec reference implementation
The npm package web-streams-polyfill receives a total of 8,691,097 weekly downloads. As such, web-streams-polyfill popularity was classified as popular.
We found that web-streams-polyfill demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISA launched a new project called Vulnrichment to enrich CVEs with details that help prioritize patching and mitigation efforts, as the NVD backlog of unenriched CVEs awaiting analysis surpasses 10,000.
Security News
Socket is joining forces with CISA and other industry leaders at the RSA Conference to sign the Secure by Design pledge, committing to uphold the highest security standards in our products.
Research
The Socket research team breaks down a sampling of malicious packages that download and execute files, among other suspicious behaviors, targeting the popular Discord platform.