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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@dcl/fetch-component

v1.1.1

Published

Fetch component for core components library

Readme

@dcl/fetch-component

Fetch component for core components library. It wraps the default Node fetch API with retry, timeout and default-options support, and is meant to be used by servers running on the default Node runtime.

Installation

npm install @dcl/fetch-component

Usage

import { createFetchComponent } from '@dcl/fetch-component'

const fetcher = createFetchComponent({
  defaultHeaders: { 'X-Custom': 'value' }
})

const response = await fetcher.fetch('https://api.example.com/data', {
  method: 'GET',
  attempts: 3,
  retryDelay: 100,
  timeout: 5000
})

const data = await response.json()

Features

  • Backed by the default Node fetch API (no cross-fetch/node-fetch dependency)
  • Automatic retries for idempotent requests (GET, HEAD, OPTIONS, PUT, DELETE)
  • Retries both retryable status codes and network-level failures (DNS, connection refused/reset, socket hang up)
  • Configurable retry delay and timeout per request
  • Default headers and default request options shared across calls
  • Type-safe through the shared IFetchComponent type from @dcl/core-commons

Request options

In addition to the standard RequestInit options, fetch accepts:

  • attempts - number of attempts for idempotent requests before giving up
  • retryDelay - milliseconds to wait between retry attempts
  • timeout - milliseconds to wait before aborting the request
  • abortController - an AbortController used to abort the request

Non-retryable status codes (400, 401, 403, 404) and non-idempotent methods are never retried. Network-level failures (a rejected fetch) are retried for idempotent methods up to attempts times; once the retries are exhausted the last network error is re-thrown.

License

Apache-2.0