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_checks

v1.0.3

Published

A wrapper for fetch() with safety checks

Downloads

1

Readme

fetch_with_checks

Status: Works

The fetch spec: https://developer.mozilla.org/en-US/docs/Web/API/fetch describes ten different error modes that all throw "TypeError". Nine of these are coding errors and only one is "throws a network error". There is no defined way of telling the difference. This function provides a wrapper to aim to detect known coding errors in advance.

Example

An example can be found in myfetch.tsx. This is an example module containing a React element to implement a cat facts lookup. When supplying a valid URL, the expected result is given. When a URL is invalid, the output will clearly explain why.

Error Types

URLError

  • URL Fails to parse as a new URL(), eg fetch_with_checks("\x00")
  • URL Contains a credentials, eg fetch_with_checks("https://user:[email protected]/")
  • URL Contains invalid scheme, eg fetch_with_checks("hxxp://example.com")

HeaderError

All variations of invalid headers will throw this error, examples from the API guide:

// space in "C ontent-Type"
const headers = {
    "C ontent-Type": "text/xml",
    "Breaking-Bad": "<3"
};


const headers = [
    ["Content-Type", "text/html", "extra"],
    ["Accept"],
];

ModeError

  • Provided mode is not from a valid list, eg fetch_with_checks("https://example.com/", { mode: "not a mode" })
  • Mode is no-cors but method is not a cors-safe method, eg fetch_with_checks("https://example.com/", { mode: "no-cors", method: 'CONNECT' })