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

@internetarchive/fetch-handler

v1.2.0

Published

A custom library for handling API requests

Readme

Build Status codecov

Internet Archive Fetch Handler library

A custom library for handling API requests.

Installation

npm install @internetarchive/fetch-handler

Sample Usage

import { FetchHandler } from '@internetarchive/fetch-handler';

@property({ type: Object }) data: any = null;
@property({ type: String }) error: string = '';
@property({ type: Boolean }) loading: boolean = false;

private fetchHandler: FetchHandler;

this.fetchHandler = new FetchHandler({
  apiBaseUrl: 'https://archive.org',
});


async fetchData() {
  this.loading = true;
  this.error = '';
  try {
    const result =
      await this.fetchHandler.fetchApiPathResponse('/metadata/goody');
    this.data = result;
  } catch (error) {
    this.error = `Error fetching data: ${error}`;
  } finally {
    this.loading = false;
  }
}

See the demo directory for a more detailed example.

Configuring Retry

You can customize how you'd like FetchHandler to retry a request, both globally and per-request.

Basic Usage

There are two included configurations, DefaultRetryConfiguration and NoRetryConfiguration, which can be accessed via FetchRetryConfig.default and FetchRetryConfig.noRetry. .default (the default) will retry twice with exponential backoff delay and .noRetry will not retry.

Example:

import { FetchHandler, FetchRetrier, FetchRetryConfig } from '@internetarchive/fetch-handler';

// setting default: retry twice with exponential backoff delay
const fetchRetrier = new FetchRetrier({
  retryConfig: FetchRetryConfig.default
})

const fetchHandler = new FetchHandler({
  fetchRetrier
})

// use default retry configuration
await fetchHander.fetch('https://foo.com/api')

// specify retry config per-request: will not retry this request
await fetchHandler.fetch('https://foo.com/api', {
  retryConfig: FetchRetryConfig.noRetry
})

Custom Retry Configuration

Fetch retrying can be configured using a RetryConfiguring object. This interface has two methods:

interface RetryConfiguring {
  shouldRetry(
    response: Response | null,
    retryNumber: number,
    error?: unknown,
  ): boolean;

  retryDelay(
    retryNumber: number,
    response?: Response | null,
  ): Milliseconds | null;
}

class MyCustomRetryConfig implements RetryConfiguring {
  shouldRetry(
    response: Response | null,
    retryNumber: number
  ): boolean {
    if (response === null) return false;
    if (retryNumber > 1) return false;
    return response.status !== 404;
  }

  retryDelay(retryNumber: number): Milliseconds | null {
    return 1000;
  }
}

const customRetryConfig = new MyCustomRetryConfig();
// use your custom retry config on a request or globally
await fetchHandler.fetch('https://foo.com/api', {
  retryConfig: customRetryConfig
})

Local Demo with web-dev-server

Add 127.0.0.1 local.archive.org to your /etc/hosts file

npm run start

NOTE The first time you visit the site, the browser will say the site is insecure because it's using a self-signed certificate. Accept the certificate and visit the site and the browser will then accept the certificate in the future. It may always say the site is insecure, but for the purposes of development, it's secure enough.

To run a local development server that serves the basic demo located in demo/index.html

Testing with Web Test Runner

To run the suite of Web Test Runner tests, run

npm run test

To run the tests in watch mode (for <abbr title="test driven development">TDD</abbr>, for example), run

npm run test:watch

Linting with ESLint, Prettier, and Types

To scan the project for linting errors, run

npm run lint

To automatically fix many linting errors, run

npm run format