@metaplex-foundation/umi-http-fetch

An HTTP implementation relying on the fetch API

@metaplex-foundation/umi-http-fetch@1.6.0 was published on 2026-09-17. Its manifest declares 1 runtime dependency and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @metaplex-foundation/umi-http-fetch versions · Permanent reference to 1.6.0

Package specifications

Version1.6.0
License declarationMIT
Published2026-09-17T20:02:03.146Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size18.21 KiB
Published file count21
Package typeNot declared
ES module entrydist/esm/index.mjs
Default entrydist/cjs/index.cjs
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies4
Repository stars244
Repository forks89

Install @metaplex-foundation/umi-http-fetch 1.6.0

npm install @metaplex-foundation/umi-http-fetch@1.6.0
pnpm add @metaplex-foundation/umi-http-fetch@1.6.0
yarn add @metaplex-foundation/umi-http-fetch@1.6.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Evidence and freshness