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

@grund/fetch

v0.0.85

Published

The purpose of this package is twofolded:

Downloads

82

Readme

@grund/fetch

The purpose of this package is twofolded:

  1. Create a common interface for other grund packages to use.
  2. Intercept and throw enhanced errors (from @grund/errors)

Error intercepting

Using the fetch API can be a bit tricky and hard to understand - especially in the context of errors. So we created this wrapper around the fetch function which acts in exactly the same way as a normal fetch does - but throws a set of enhanced errors (from @grund/errors). These errors are the following:

  • ConnectionError - If the native fetch function throws an error and the user is not connected to the internet (using the package is-online).
  • ServerUnavailableError - If the native fetch function throws an error and the user is online, indicating that the server is unavailable in some way.
  • BadRequestError - The fetch got a result on the request, but the status code was 400.
  • AuthenticationError - The status was 401.
  • ForbiddenError - The status was 403.
  • UrlNotFoundError - The status was 404.

401 status

The http error with code 401 has the name Unauthorized which essentially means the same as the name for 403 - Forbidden.

Quick recap:

  • authentication - Find out if you are who you say you are.
  • authorization - I know who you are, but are you allowed to do what you want do to?

According to https://stackoverflow.com/questions/3297048/403-forbidden-vs-401-unauthorized-http-responses, the name Unauthorized is a but unfortunate since what it means in practise in that you aren't authenticated. This is why this package throws an AuthenticationError when it receives the code 401.

Native fetch

fetch is built into all modern web browsers, but not in NodeJS. So when we want to use this package in a node environment we need to tell it to use a specific fetch instance.

To fix this the package exposes setNativeFetch. So in you initiation module in your application, make sure to set your native fetch instance with this function. Examples:

// NodeJS

import fetch from 'node-fetch';

import { setNativeFetch } from '@grund/fetch';

setNativeFetch(fetch);
// Browser

import { setNativeFetch } from '@grund/fetch';

setNativeFetch(window.fetch);