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 🙏

© 2025 – Pkg Stats / Ryan Hefner

global-fetch

v0.2.2

Published

Promise-based HTTP client built on top of the global fetch API

Readme

global-fetch

Promise-based HTTP client built on top of the global fetch API.

Installing

yarn add global-fetch

# or via npm
npm install --save global-fetch

Examples

import http, { get, post } from 'global-fetch';

(async () => {
  const query = { userId: 1 };
  try {
    await get('http://jsonplaceholder.typicode.com/users', { query });
  } catch (e) {}

  // or all requests with the same server url
  const request = http('http://jsonplaceholder.typicode.com');
  await request.get('/users');
  await request.post('/post', {
    json: { title: 'foo', body: 'bar', userId: 1 }
  });
})();

By default, GlobalFetch resolves the response data as JSON. If any other formats you want to yield, do it like below.

// Resolve response type as text
await get('./index.html', { responseType: 'text' });

// If response type is falsy value like `null`,
// response will be resolved as original data
await get('./index.html', { responseType: null });
// request as query string when method is GET or HEAD
const query = { user_id: 1 };
await get('/users', { query }); // /users?user_id=1

// post JSON data
const json = { name: 'jiraiyame', age: 27 };
await post('/users', { json });

// post form data
const form = document.querySelector('form');
await post('/users', {
  body: new FormData(form),
});

// post data via url encoded request
const form = { foo: 1, bar: [1, 2, 3] };
await post('/users', { form });

Interface

class GlobalFetch

Constructor

constructor(baseUrl: string, config?: RequestInit);

setBaseUrl(url)

  • url <string> the API host of the resource

setHeader(name, value)

  • name <string> header field name
  • value <any> header field value

setHeaders(headers)

  • headers <Object> custom header fields

setToken(auth)

  • auth <string> the credentials of the auth
  • auth: { token, type }
    • type <string> the authentication scheme. Defaults to Bearer
    • token <string> the credentials of the auth

setResponseType(responseType)

  • responseType <string | null> the response data type will respond. Defaults to json

get(url[, options])

post(url[, options])

put(url[, options])

patch(url[, options])

del(url[, options])

head(url[, options])

options(url[, options])

License

MIT @ jiraiyame