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

nice-fetch

v1.1.0

Published

Wrapper function to simplify working with native fetch

Downloads

1

Readme

Nice Fetch

CI status Codecov NPM semantic release

Installation:

npm install nice-fetch

Table of Contents

What is it

A very simple function (330 bytes gzipped ) that simplifies working with the fetch

Motivation

After writing fetch code hundreds of times, I've decided to simplify the fetch function so instead of this:

try {
  const response = await fetch('https://example.com')
  if (response.ok) {
    const data = await response.json()
  } else {
    throw response
  }
} catch (e) {
  console.log(e)
}

I can do this:

import fetch from 'nice-fetch'

try {
  const [data, response] = await fetch('https://example.com')
} catch (e) {
  console.log(e)
}
// or this

const [data, response] = await fetch('https://example.com').catch((e) =>
  console.log(e)
)

Or if exclusively working with JSON

import { fetchJson } from 'nice-fetch'

try {
  const [data, response] =
    (await fetchJson) <
    { name: string, address: string } >
    'https://example.com'

  console.log(data.name) // correctly typed
} catch (e) {
  console.log(e)
}

A small improvement I know, but it adds up over time :)

Usage

nice-fetch accepts the same arguments as regular fetch with one additional argument which is the type of the body from the response that you expect to be returned, the default value is json. This determines how the response body content should be handled.

// if (response.ok)
const data = await response.json() // <- json is the default
// } else {

Other parameters are all available methods on the Body mixin

for example:

import fetch from 'nice-fetch'

// data is JSON (default)
const [data, response] = await fetch('https://example.com')

// data is JSON
const [data, response] = await fetch(
  'https://example.com',
  { method: 'GET' },
  'json' // <- explicit
)

// data is Blob
const [data, response] = await fetch(
  'https://example.com',
  { method: 'GET' },
  'blob'
)

// data is string
const [data, response] = await fetch(
  'https://example.com',
  undefined // <-- pass undefined for RequestInit
  'text'
)

Return values

The function returns a tuple of data, which is already handled response content (no need for response.json() call) and the original response object.

Error handling

When you write code like this, all errors can be handled in the catch block.

try {
  const [data, response] = await fetch('https://example.com')
} catch (e) {
  console.log(e)
}

In case that the response.ok is not true (status is not in the range 200–299) fetch will throw with the full Response object

In case that the response body content can't be properly handled e.g. invalid JSON, the function will rethrow the error.

In case there is an error from the fetch call itself ( Network request failed, timeout) function will also rethrow that error.