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

fetch-with-status

v0.0.8

Published

fetch with status helpers

Downloads

3

Readme

fetch-with-status

fetch with status helpers.

A small lib so you remember to check the status code of your request.

npm version

Installation

npm install fetch-with-status

yarn add fetch-with-status

example

const {withStatus} = require('fetch-with-status')

withStatus(fetch('https://jsonplaceholder.typicode.com/posts/1'))
  .when(200, (request) =>
    request.json())
  .when([404, 405], (request) =>
    throw new Error('Oh no!'))
  .build()
  .then((json) =>
    console.log(json))
  .catch((error) =>
    console.log('error', error.message))

Summary

API

when

Takes a number | array of numbers and a function.

What gets returned from executed .when get passed to original promise chain after execution.

Syntax

  .when(206, (request, next) => {})

  .when([206, 500], (request, next) => {})

Parameters

  • number || Array of numbers: desired status code:s
  • function:
    • params:
      • response: fetch response object
      • next: call next() if you want to continue to the standard .then promise chain
    • returns: any

Return value

self so we can chain multible .when

Build

Syntax

  .build()

Parameters

none

Return value

Promise: originl fetch promise

Usage

// Require it like this
const {withStatus} = require('fetch-with-status')

// Wrap your fetch with the `withStatus` function
withStatus(fetch(/*URL*/))
  // then add all the status handlers you want
  // the full request object is returned in all handlers
  .when(200, (request, next) => {
    console.log('we got an 206 response')
    // if you want to continue down the promise chain call 'next'
    // and your value will be passed down to the first .then
    next(request.json())
  })

  .when([404, 405, 406], (request) => {
    // here we don't call next because we don't want to continue down the promise chain
    console.log('we got an 404, 405 or 406 response')
  })
  // after you added all your desired handlers call .build
  .build()
  // now we have the original promise so we can add .then:s and a .catch
  .then(() => {
    // only request with handlers that call 'next' appear here
  })
  .catch((error) => {

  })

TODO:

  • make stuff immutable (more fp)
  • tests