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

@acato/axios-utils

v1.0.2

Published

axios interceptors

Downloads

11

Readme

axios-utils

Easy intercepting of axios resources (instances).

Table of contents

Features

  • Create axios instances (resources) with default request config and/or custom request config
  • Add error interceptors for specific status codes and/or based on regexp's

Installing

Using yarn:

yarn add @acato/axios-utils

Using npm:

npm i @acato/axios-utils

Example

Creating a (axios) resource:

import { createResource } from '@acato/axios-utils'

export const myResource = createResource({ baseUrl: 'https://myhost.com/api' })

Define interceptors:

import { applyInterceptors, addHandler } from '@acato/axios-utils'

// Authorization config:
const requestConfig = (config) => {
  config.headers['Authorization'] = `Bearer ${getTokenFromSomewhere()}`
  return config
}
// Request interceptor:
export const intercept = applyInterceptors({
  request: requestConfig
})
// Request with extra config (makes use of re-usable 'requestConfig'):
export const intercept = applyInterceptors({
   request: (config) => {
    config.headers['x-header'] = 'x-value'
    return requestConfig(config)
  },
})

// Response interceptor:
export const intercept = applyInterceptors({
   response: res => res // or do something useful instead
})

// Error handlers:
const responseErrorConfig = addHandler(
  {
    match: 502, // matches 502 errors (exact match)
    handler: (error, axiosInstance) => // Promise.reject or do something else
  },
  {
    match: /40/, // matches all 40* errors (regexp)
    handler: (error, axiosInstance) => // Promise.reject or do something else
  }
)

export const intercept = applyInterceptors({
  error: responseErrorConfig
})

Our interceptor function is ready and we can intercept axios instances easily:

import { createResource } from '@acato/axios-utils'
import { intercept } from './my-interceptors'

export const myResource = intercept(createResource({ baseURL: 'https://...' }))

API

Interceptors can be connected to your resources by passing relevant interceptor config to applyInterceptors.

applyInterceptors(interceptorConfig)

Interceptor config

{
 // Not required
 request: config => {
  config.headers['Authorization'] = `Bearer ${getTokenFromSomewhere()}`
  return config
 },

 // Not required
 response: res => {
   // do something with response before sending it
 },

 // Not required
 error: addHandler(
    {
      match: /502/,
      handler: (err, axiosInstance) => ...
    },
    {
      match: /40/,
      handler: (err, axiosInstance) => ...
    }
  )
Note that the order of the handlers matters, because the first match will be used to handle the specific error.
So to be sure your handler will be executed, add handlers from specific to more generic, like this:
  addErrorHandler({
        match: 401,
        handler:...
    },
    {
        match: /40/,
        handler: ...
    }
  )

 This errorhandler will first match a 401 error, then all other 40* errors.

}

Return value

applyInterceptors returns a function which accepts an axios resource (instance) as the only argument.

  export const applyInterceptors =
  ({ request, response, error }) =>
  (axiosResource) => {

    // attach interceptors here to the axiosResource:
  ...
  }

Usage

Create a re-usable intercept function:

import { createResource } from '@acato/axios-utils'

export const intercept = applyInterceptors({
  request: ...,
  response: ...,
  error: ...
})

Apply the intercept function on an axios resource:

import { createResource } from '@acato/axios-utils'
import { intercept } from 'my-interceptor'

export const myResource = intercept(
  createResource({
    baseURL: `${API_URL}/api`
  })
)

Now every fetch call with any axios resource 'wrapped' with the intercept function, will trigger our interceptor handlers.