FLUTTER ECOSYSTEM

Zekfad/fetch_client

HTTP 패키지용 기반 가져오기 클라이언트입니다.

fetch_client 프로젝트 이미지
Stars
29
Forks
12
최근 푸시(UTC)
2026. 4. 3.
프로젝트 상태
활성
Yaroslav Vorobev GitHub avatar
GITHUB User

Yaroslav Vorobev ↗

Bachelor of Software Engineering. Full-stack web and Dart/Flutter developer.

@ZeroNaNme & @ClownCoRussian Federation, Ryazan' Region, Skopin
언어Dart

기술 주제

이 저장소가 배포한 패키지

사용 중인 의존성

의존성 목록 7 개
  • fetch_api^2.2.0
  • http^1.5.0
  • build_runner개발 의존성>=2.4.10
  • build_web_compilers개발 의존성>=4.0.10
  • http_client_conformance_tests개발 의존성{"git":{"url":"https://github.com/dart-lang/http","ref":"master","path":"pkgs/http_client_conformance_tests"}}
  • test개발 의존성^1.25.5
  • zekfad_lints개발 의존성^2.3.0

원본 README

아래는 영문 원문 스냅샷입니다. 최신 내용은 GitHub에서 확인하세요.

README 펼치기 / 접기

Fetch Client

pub package package publisher

This package provides package:http client based on Fetch API with WASM support.

It's a drop-in solution for extensions with Manifest V3.

Features

  • WASM-ready internals.
  • Cancel requests.
  • Support data streaming:
    • Get response as Stream.
    • Optionally, send Stream as request body (supported only in Chromium 105+ based browsers).
  • Get access to redirect URL and status.
  • Support non-200 responses (fetch will only fail on network errors).
  • Simulate redirects responses via probe request and artificial location header.

Notes

Large payload

This module maps keepalive to BaseRequest.persistentConnection which is true by default.

Fetch spec says that maximum request size with keepalive flag is 64KiB:

4.5. HTTP-network-or-cache fetch

8.10.5: If the sum of contentLength and inflightKeepaliveBytes is greater than 64 kibibytes, then return a network error.

Source: Fetch. Living Standard — Last Updated 19 June 2023

Therefore if your request is larger than 64KiB (this includes some other data, such as headers) BaseRequest.persistentConnection will be ignored and treated as false.

Request streaming

Request streaming is supported only in Chromium 105+ based browsers and requires the server to use HTTP/2 or HTTP/3.

See MDN compatibility chart and Chrome Developers' blog for more info.