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

chainfetch

v1.2.2

Published

A simple, chainable wrapper around node-fetch!

Readme

Chainfetch

Super simple HTTP requests using node-fetch and a chainable interface

Getting Started

First off, you need to install the module! To do so,

npm i chainfetch node-fetch

# Or if you are using yarn

yarn add chainfetch node-fetch

And then you're ready to roll! Or...chain.

Usage

The following examples assume you are in the context of an async function. All return functions return a promise for you to use.

const fetch = require('chainfetch');

const res = await fetch.get('https://example.com').toText();

For posting data, you can do something similar to this

const fetch = require('chainfetch');

const res = await fetch.post('https://example.com').query({ isSimple: true }).query('isAmazing', true).send({ string: 'chainfetch is simple and amazing!' });

Are you a TypeScript user

We got you covered! We have rich typings which should work in all cases (if not, feel free to submit an issue ❤️)

import chainfetch from 'chainfetch';
// Or
import { get } from 'chainfetch';
// Or
import * as chainfetch from 'chainfetch';

// Works
chainfetch.get();

// If you want to create your own custom class for custom handling
const myCustomClass = new chainfetch('HTTP METHOD', 'URL');
myCustomClass.get();

Meaning of toJSON, toText and toBuffer

In chainfetch, there are 4 functions which can determine how the response should be parsed. You can access the body by using res.body.

By default, we try to JSON.parse the body if the response provides the Content-Type header and it includes application/json.

| Function | What it returns | |:-------------------:|:-------------------------------------------------------------------------------------------------:| | toBuffer | Does no processing on the body, and returns it as a buffer | | toJSON | Attempts to parse the response body as a JSON object, otherwise it returns the stringified Buffer | | toText and toString | Both of these functions take the response body and turn it into a string |