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

@unfuck/fetch

v0.0.4

Published

It's just fetch with a few DX improvements:

Downloads

3

Readme

Unfucked fetch

It's just fetch with a few DX improvements:

  • Data is cached on the object once retrieved from the stream so it isn't destroyed (removes need to clone entire object for simple situations).

  • Provides convenience 'gimme' method that will attempt to interpret data type based on headers and return data from relevant stream method.

  • Each of these features are provided on a custom FkResponse with overloads for the data retrieval methods.

  • Throws a fucking error. I prefer returned errors over throws too, they are the way errors should be done. BUT, when the rest of the language/ecosystem is built around throw/try-catch it makes things really, really annoying to have one common method that is different. Also not having a proper, ubiquitous option type kinda makes returned errors suck (still love you tho Go).

  • Throws http-errors except for the custom NetworkError. If anyone knows of a better more TS friendly error lib I'll use that, or make my own.

  • You can use fkFetch method directly the same as fetch or use createFkFetch to make your own instance with custom MIME type mapping.

  • Decided not to Monkey-Patch fetch as this does change the use patterns considerably.

  • Auto-capitalizes 'patch' to 'PATCH', because, come on... Nobody cares if it's not a standard verb, it's used nearly everywhere. The fact you have to point out in the docs that you must manually capitalize it is CLEAR a sign that it should be done automatically.