Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
@stardazed/streams-fetch-adapter
Advanced tools
Patch fetch and Response to work with custom stream implementations
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⭐️.
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.
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
© 2018-Present by Arthur Langereis - @zenmumbler
MIT
FAQs
Patch fetch and Response to work with custom stream implementations
We found that @stardazed/streams-fetch-adapter demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.