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 🙏

© 2024 – Pkg Stats / Ryan Hefner

json-fetcher

v1.0.8

Published

This is a micro-library for making http requests for JSON payloads. It wraps `fetch` with sensible defaults.

Downloads

18

Readme

JSON Fetch

This is a micro-library for making http requests for JSON payloads. It wraps fetch with sensible defaults.

You can use it in the browser or in node.

const JsonFetcher = require('json-fetcher').JsonFetcher;

const requestManager = new JsonFetcher();

// simple get request
requestManager.get('http://yourapi.co/api/stuff')
  .then(docs => console.log(docs));

// with query string
requestManager.get('...', {
  query: {foo: 'bar'}
})

// will serialize query string for you and put it in url. handles nested objects great


// you can send body payloads too
requestManager.post('...', {
  body: { foo: { bar: 'baz' } }
});

Configuration

Sometimes you want to make tons of requests with some of the same headers. If you want to do that, just use our config method

requestManager.config({
  headers: {
    Authorization: 'xxxxxx'
  }
});

The object you pass to config gets merged with our defaults.

Why?

Lots of libraries ship with nice http interfaces. But when you're working outside of a library your options get worse. There's Axios, which is awesome, but its quite a bit bigger and build on top of the XMLHttpRequest. This is built on fetch. One important note is that the library is BYOF (bring your own fetch). If you use it in node, you need to have fetch defined globally. There are several packages that do this.

Why use this instead of just fetch

This sets up reasonable headers for working with JSON, parses your HTTP bodies into JSON, parses the response into JSON, serializes your query string... stuff you don't want to do over and over again.

It also gives you space to be able to set up defaults and remember them. Let's say you're working with two APIs and need to remember two sets of auth headers. You can just make two instances of JsonFetcher.