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

use-api-request

v0.1.0

Published

A React Hook for Making Api Requests Using Axios

Downloads

2

Readme

use-api-request

A simple React hook for making network requests using Axios.

NPM styled with prettier Build Status Coverage Status

Install

npm install --save use-api-request

Example

import axios from 'axios';
import { useApiRequest } from 'use-api-request';

function MyComponent() {
  const apiConfig = {
    axios: axios.create({
        baseURL: "https://whereami.com/"
    }),
    key: "example",
    debug: true
  };

  const { state, makeApiRequest } = useApiRequest(apiConfig);
  const { fetching, resources: { posts }, errors } = state;

  const requestConfig = {
     posts: {
        url: "/posts"
      }
  };

  return (
    <>
      <button onClick={() => makeApiRequest(requestConfig)}>Get Posts</button>
      <>
        {fetching.includes("posts") && <div>fetching</div>}
        {posts.data.length > 0 && posts.data.map(post =>
            <div key={post.id}>{post.title}</div>) }
        {errors.posts && <div>{errors.posts.message}</div>}
      </>
    </>
  );
}

Usage

  1. Pass a config object with an Axios instance and a key string, into useApiRequest. The Axios instance takes the exact same configurations as specified in the documentation. Optionally include a debug flag if you'd like to see redux-like logging in your console.

  2. Create a request object -- again, refer to the Axios documentation for examples -- and pass it into makeApiRequest. Note that this library uses Axios.request() under the hood. The request object is nothing more than an Axios request config object assigned to a resource key of your choosing. So, if you name the key things, you will find things many times within the state object. See below for more details.

  3. Call makeApiRequest and look for your response on the resources key of the state object provided by useApiRequest.

Features

Make a single request:

const singleRequestConfig = {
   posts: {
     url: "/posts"
   }
 };

makeApiRequest(singleRequestConfig);

Make multiple concurrent requests:

const concurrentRequestsConfig = {
    albums: {
      url: "/albums"
    },
    users: {
      url: "/users"
    }
  };

makeApiRequests(concurrentRequestsConfig);

Make a sequential request (dependent variables are wrapped in double curly brackets and will always be properties of data):

const sequentialRequestConfig = {
    userPosts: {
      url: "/posts/1",
      next: {
        url: "/posts?userId={{data.userId}}"
      }
    }
  };

makeApiRequest(sequentialRequestConfig);

API

const { state, makeApiRequest, makeApiRequests } = useApiRequest(apiConfig);
const { fetching, resources, errors } = state;

fetching - array of strings corresponding to the resource key(s) used in the request config

resources - object of successful responses; each response can be found under the key used in the request config, and each response contains the entire response generated by Axios

errors - object of errors; each error can be found under the key used in the request config, and each error contains the entire error generated by Axios

License

MIT © jmpolitzer