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

@americanairlines/fetch-interceptor

v1.0.14

Published

A lean package for intercepting fetch calls in node.

Downloads

76

Readme

Fetch Interceptor

Written in Typescript

Fetch Interceptor is a small Typescript package that allows for the interception of requests made via Node-Fetch.

Usage

To install

$ npm i @americanairlines/fetch-interceptor

Create your interceptor

const interceptor = require("@americanairlines/fetch-interceptor");

function beforeFetch(requestInfo) {
  let { requestId, method, url, params, headers, body } = requestInfo;
  console.log("RequestId " + requestId);
  console.log("Request Type " + method);
  console.log("Request Url " + url);
  console.log("Request Params " + params);
  console.log("Request Headers " + headers);
  console.log("Request Body" + body);
}

function afterFetch(requestInfo) {
  let { requestId, method, url, params, headers, body } = requestInfo;
  console.log("RequestId " + requestId);
  console.log("Request Type " + method);
  console.log("Request Url " + url);
  console.log("Request Params " + params);
  console.log("Request Headers " + headers);
  console.log("Request Body" + body);
}

module.exports.default = interceptor(beforeController, afterController);

Using the interceptor. It's important to import and use the interceptor you created in the same way you would use fetch. @americanairlines/fetch-interceptor just intercepts fetch. It accepts all the same arguments as node-fetch.

const fetch = require("../path/to/interceptor");

async function foo() {
  let bar = await fetch("https://some-site.com");
}

foo();

API

requestInfo

This is the logging object with the request info that the handler functions have access to.

Note

This package was designed to work with @americanairlines/controller-interceptor. Using this package in combination with @americanairlines/controller-interceptor provides the ability to trace connections between services with a TraceId. This TraceId does not have to be generated by @americanairlines/controller-interceptor. The requestId argument can be any string.

RequestInfo = {
  requestId: string; // The trace Id of the request
  method: string; // The http method of the request
  url: string; // The url that the request was made to
  params: Object; // The params passed to the request
  headers: Object; // The header object of the incoming/outgoing request
  body: Body; // The body of the incoming/outgoing request
}

beforeFetch/afterFetch

These functions are not passed the actual body or headers objects, just copies of them. You are not able to mutate these fields in the handler functions.

Author

Chandler Barlow

Collaborators

Steven Paulino

License

MIT