HEX
Server: Apache/2.4.41 (Ubuntu)
System: Linux ip-172-31-42-149 5.15.0-1084-aws #91~20.04.1-Ubuntu SMP Fri May 2 07:00:04 UTC 2025 aarch64
User: ubuntu (1000)
PHP: 7.4.33
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
Upload Files
File: /var/www/vhost/disk-apps/pwa.sports-crowd.com/node_modules/minipass-fetch/README.md
# minipass-fetch

An implementation of window.fetch in Node.js using Minipass streams

This is a fork (or more precisely, a reimplementation) of
[node-fetch](http://npm.im/node-fetch).  All streams have been replaced
with [minipass streams](http://npm.im/minipass).

The goal of this module is to stay in sync with the API presented by
`node-fetch`, with the exception of the streaming interface provided.

## Why

Minipass streams are faster and more deterministic in their timing contract
than node-core streams, making them a better fit for many server-side use
cases.

## API

See [node-fetch](http://npm.im/node-fetch)

Differences from `node-fetch` (and, by extension, from the WhatWG Fetch
specification):

- Returns [minipass](http://npm.im/minipass) streams instead of node-core
  streams.
- Supports the full set of [TLS Options that may be provided to
  `https.request()`](https://nodejs.org/api/https.html#https_https_request_options_callback)
  when making `https` requests.