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

fetch-this

v0.4.0

Published

Make requests based on stored configuration

Readme

fetch-this

Make requests based on stored configuration

:construction: This lib is under development. Expect breaking changes until 1.0.

This tool allows you to express fetch requests as a json. Some use cases:

  • avoid repeating yourself by looping into a collection of "fetches to be performed"
  • make requests to endpoints that you will only know at runtime
  • hide fetch details from code, loading it's details at runtime

Install

npm install fetch-this

Usage

Let's assume:

$ curl http://localhost:9876/test
{"nested":{"some":{"values":[11,13,17]}}}

So, we can do:

import {
  fetchThis,
  getResult,
} from 'fetch-this'

// `fetchThis()` returns a fetch()` response promise, you can just use it as you wish
const fetchConfig = {
  url: 'http://localhost/test',
}
const response = await fetchThis(fetchConfig, payload)

// or you can use `getResult()` for a promise to the value you really want
const result = 'nested.some.values[2]'
const value = await getResult(response, result)

console.log(value) // 17

Roadmap

  • [x] accept a config object to perform a GET request
  • [x] add getResult() that maps a response promise to a single value inside it
  • [ ] add createFetch, same API as fetch, returns a fetch-this config
  • [ ] add query params to the config, like { query: { a: 'b' } }
  • [ ] add method to the config, like { method: POST } (GET by default)
  • [ ] add form params to the config, like { form: { a: 'b' } }
  • [ ] add headers to the config, like headers: { 'X-Forwarded-For': 'proxy1' }