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

@brillout/fetch

v0.2.1

Published

The `@brillout/fetch` package uses: - The browser built-in `window.fetch` if run in the browser. - The NPM package [`node-fetch`](https://github.com/bitinn/node-fetch) if run in Node.js.

Readme

@brillout/fetch

The @brillout/fetch package uses:

  • The browser built-in window.fetch if run in the browser.
  • The NPM package node-fetch if run in Node.js.

@brillout/fetch is designed to work well with bundlers such as Webpack and Parcel.

No polyfill is used in the browser, saving KBs and delay for your users. This is means that IE11 is not supported. (IE11 is the only browser not supporting fetch: https://caniuse.com/#feat=fetch.) With IE11's decline, not supporting IE11 is more and more an option. If you want IE11 support then use another fetch library, see the list of fetch libraries below.

Usage

const fetch = require('@brillout/fetch'); // npm install @brillout/fetch
// import fetch from '@brillout/fetch';

(async () => {
  const response = await fetch('https://brillout-misc.github.io/game-of-thrones/characters/list.json');
  const characters = await response.json();
  console.log(characters);
})();

List of fetch libraries

  • node-fetch - Fetch implementation for Node.js
  • whatwg-fetch - Fetch polyfill for the browser
  • @brillout-fetch - Universal fetch without IE11 support (Based on native window.fetch and node-fetch)
  • fetch-ponyfill - Universal fetch ponyfill with IE11 support (Based on whatwg-fetch and node-fetch)
  • cross-fetch - Universal fetch ponyfill with IE11 support (Based on whatwg-fetch and node-fetch)
  • isomorphic-fetch - Universal fetch polyfill with IE11 support (Based on whatwg-fetch and node-fetch)