npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@stardazed/streams-fetch-adapter

v3.0.0

Published

Patch fetch and Response to work with custom stream implementations

Downloads

11

Readme

@stardazed/streams-fetch-adapter

This package provides helper functions to create adapted versions of a runtime's native fetch function and Response class to work with ReadableStream implementations other than the built-in one.

If the runtime does not support ReadableStream at all, the provided custom implementation will be used to add support for streams to both fetch and Response transparently.

Support is also added to fetch to allow a ReadableStream for the body to send to the server, but unlike the fetch spec describes, it does not send the data incrementally to the server. Instead it reads the entire stream and then sends it as a Blob body. Upload streaming must be implemented by the user-agent and cannot be simulated.

⚠️ Important: this is NOT a polyfill. This package only provides helper functions that can be used to make adapted types for a streams implementation.

👉 If you want a polyfill for the Stardazed streams implementation, use the ⭐️Stardazed streams polyfill⭐️.

Installation

Pick your preferred package provider program:

npm install @stardazed/streams-fetch-adapter
pnpm install @stardazed/streams-fetch-adapter
yarn add @stardazed/streams-fetch-adapter

⚠️ Important: This library requires TypeScript 3.6 or newer due to type changes in the standard library.

Usage

Use this package if you want to adapt fetch and Response to support your custom ReadableStream implementation, this may be for things like mocks or modified versions of built-in streams or for a full replacement, like Stardazed streams.

You only need to adapt the Response class if you want to manually construct a Response with your custom ReadableStream instance as the body. If you just want to use your implementation for a Response returned from fetch you only need to adapt fetch.

import { createAdaptedFetch, createAdaptedResponse } from "@stardazed/streams-fetch-adapter";

class MyReadableStream { /* implements ReadableStream interface */ }

// create adapted types...
const myFetch = createAdaptedFetch(window.fetch, window.ReadableStream, MyReadableStream);
const myResponse = createAdaptedResponse(window.Response, window.ReadableStream, MyReadableStream);

// ...and use them like the built-in versions
myFetch("./some-resource.txt").then(resp => resp.body /* <-- is an instance of MyReadableStream */);
myFetch("some-server.com/upload", { method: "post", body: new MyReadableStream(...) }); // works
const blob = new myResponse(new MyReadableStream(...)).blob(); // works

Copyright

© 2018-Present by Arthur Langereis - @zenmumbler

License

MIT