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-fetchy

v1.0.4

Published

A simplified fetch api

Downloads

12

Readme

logo

A simplified fetch API

→ Methods for each HTTP verb means no building request objects

→ API-level error handling means no checking status codes

→ Built-in response parsing means no additional checks and method calls

→ Optional one-time configuration means easy integration for your API

Install

$ npm i --save fetch-fetchy

Basic Usage

import { get, post } from 'fetch-fetchy';

/**
 * Create a user
 */
post('/user', formData)
  .then(onSuccess)
  .catch(onError)

/**
 * Fetch a user
 */
get('/user/hs9hsbs7')
  .then(onSuccess)
  .catch(onError)

Configuration

The default configuration is as follows:

{
	json: true,
	url: window.location.origin,
	headers: { 'Content-Type': 'application/json' },
	mode: 'cors'
}

json

If set to true, request data will automatically be converted to JSON.

url

The url to be used for api requests. When a route begins with /, it is assumed that the request is being made to the application's API. This means that you can define /user as the route instead of https://myapplicationdomain/user. If you set url to https://someotherdomain and specify /user as the route, the request will be made to https://someotherdomain/user. When the route does not begin with /, the full route will be used.

headers

The headers for requests.

mode

The request mode.


You may override these options for all requests by calling configure(). The default options will be overridden using Object.assign(). If you wish to apply options for a single request, just pass those options into that request.

import { configure } from 'fetch-fetchy';
/**
 * Configure fetch-fetchy
 */
const options = {
  url: 'https://myapi.com',
  headers: { Authorization: `Bearer ${jwt}`},
}
configure(options);

API Methods

get(route: String, options: Object) => Promise

post(route: String, body: *, options: Object) => Promise

put(route: String, body: *, options: Object) => Promise

patch(route: String, body: *, options: Object) => Promise

del(route: String, options: Object) => Promise

configure(options: Object) => Object