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

fetcheer

v0.1.7

Published

Small JSend compatible wrapper over browser fetch function

Downloads

13

Readme

fetcheer

A small JS fetch wrapper to work in a couple with JSend. Feel free to use as a boilerplate and a plain extension point.

##! The library is unstable and not intended to a direct usage, please, consider using it as a boilerplate.

Basic usage

import Fetcheer from 'fetcheer'
return Fetcheer.request(input, init) // purely like fetch(input, init)
      .then(Fetcheer.check200) // trivial 200 code checker
      .then(response => {
      	   // standard object of the Response interface
      })
      .catch(error => {
         // server responded with the code different from 200
      })

Usage with JSend

import Fetcheer from 'fetcheer'
Fetcheer.getJsend('/some-handler/')
   .then(jsendResponse => {
      // do something with jsend
   })
   .catch(error => {
      // server responded with the code different from 200
      // or jsend is not parsed
   })

Post queries

import Fetcheer from 'fetcheer'
/**
 * @type {{name: string, address: {street: string}, photo: File}}
 */
const user = {
    name: 'Ivan',
    address: {street: 'Ever Green str.'},
    photo: file
}
const postBody = Fetcheer.objectToFormData(user)
const postOptions = Fetcheer.getPostOptions(postBody)
return Fetcheer.getJsend('/user-save-handler/', postOptions)
    .then()
    // ...
    .catch()

JSend handling sugar

import Fetcheer from 'fetcheer'
Fetcheer.getJsend('some url')
.then(Fetcheer.checkJsendSuccess) // check if the jsend has success status
.then(data => {
   // this code is called ONLY for successful a JSend
})
.catch(/** @param {string|string[]|*} error - message from jsend with error status or data from jsend fail */
    error => { 
})