reactxios v0.0.3

Reactxios

A simple and easy to use Axios provider for react, with support for on-demand configuration.

Motivation

This project originally sprouted from a work requirement, being able to set and configure axios dynamically for a set of multi-tenant apps, while avoiding duplicating interceptors and allowing for integration with other libraries that use hooks. In theory the problem is quite simple in that you can set axios settings whenever the component renders, however this can quickly becomes in-efficient if the provider re-renders many times, especially in large scale applications where the performance of axios (/data fetching) directly reflects the performance of the app. The first solution was adding a "hasSetup" property to axios and checking its status during rendering to run the "setup" function, this worked and was effective and quite elegant, however it had several flaws: 1) - once the setup function had run, axios could no longer be setup again. 2) - if the config changed the setup function would not run. 3) - the provider has no support for any axios teardown / cleanup.

This library addresses these issues by instead using react refs and a DeepEquality check to run the setup and optional teardown functions.

Installation

Ensure that you have the latest version of axios installed: yarn add axios or npm install axios

Then install reactxios: yarn add reactxios or npm install reactxios

Getting started

First import the Reactxios component into your top level, below any configuration providers, but above any components dependant on the axios instance.

Next.js example

import { Reactxios } from "reactxios";

/**

• Write the setup function outside of the component so it
• always keeps the same reference! :)
• The props given to reactxios are automatically passed into the setup function */ const setup = (instance, { config }){ instance.defaults.baseURL = config.baseURL instance.interceptors.request.use( cfg => { cfg.headers = { Accept:"application/json", "Content-Type":"application/json" } return cfg; }) }

export function App({PageComponent, pageProps: { config, ...pageProps }}){

return <PageComponent {...pageProps} />

}

> Next.js example (using the axios instance)
```javascript

import { Axios } from "reactxios";
import { useQuery } from "react-query";

function exampleFetch(){
  return Axios.get("/example/endpoint")
}

export function SomeDataComponent(){

  const { data } = useQuery(["example"], exampleFetch);

  return <p>{data}</p>

}

Props

The reactxios component takes several props as follows

Exports

Reactxios exports

Axios

This is the reactxios default axios instance, if you don't supply your own AxiosInstance to the Reactxios provider reactxios will use this instead.

AxiosConstructor

If you wish to use your own AxiosInstance (in the case where you have several different axios instances and configurations accross the same app at the same time) you can use the AxiosConstructor which ensures the correct types are applied to the AxiosInstance (it also saves having to import from axios ;) ).

Example of using a custom axios instance

import { AxiosConstructor, Reactxios } from "reactxios";
export const Axios = AxiosConstructor();

const setup = (instance, { config }){ instance.defaults.baseURL = config.baseURL instance.interceptors.request.use( cfg => { cfg.headers = { Accept:"application/json", "Content-Type":"application/json" } return cfg; }) }

export function App({PageComponent, pageProps: { config, ...pageProps }}){

return <PageComponent {...pageProps} />

}

### DeepEqual

This is the diffing function used by reactxios to test if the cleanup and setup functions should be run.

### Reactxios

The reactxios provider component, as demonstrated above.

## Typescript

The library supports type checking via typescript, and thus exposes helper types to support better type checking and intellisense.

Below is a demonstration using Reactxios and msal to add an access token to all requests.

> next.js typescript demo
```typescript
import React, { FC, PropsWithChildren } from "react";
import { IPublicClientApplication } from "@azure/msal-browser";
import { useMsal } from "@azure/msal-react";
import { useConfigs } from "../hooks/useConfigs";


import { Reactxios, SetupHook } from "reactxios"


export interface ConfigProps{
  /** Msal instance **/
  msal: IPublicClientApplication
  /** Api Url **/
  url: string;
  /** Msal tenant **/
  tenant: string;
  /** Msal scopes **/
  scopes: string[];
}

const Setup: SetupHook<ConfigProps> = (
  instance,
  {
    msal,
    url,
    tenant,
    scopes
  }
) => {
  axiosInstance.defaults.baseURL = url;
  axiosInstance.interceptors.request.use( ( async (cfg) => {
    const account = msal.getAccountByLocalId(localStorage.getItem("accountId") || "");
    msal.setActiveAccount(account);
    const token = await msal
      .acquireTokenSilent({
        scopes:[`https://${tenant}.onmicrosoft.com/api/access_as_user`],
        account: account || undefined
      })
      .then( res => res?.accessToken )
      .catch( err => {
        if (err instanceof InteractionRequiredAuthError){
          if (account){
            msal
              .acquireTokenRedirect({
                scopes,
                account
              })
              .catch( tokenErr => (toast as {error:(a:string)=>void}).error(tokenErr?.message))
          }
        }
      });
    
    cfg.headers = cfg?.headers || {};
    cfg.headers.Accept = "application/json";
    cfg.headers["Content-Type"] = "application/json";
    cfg.headers.Authorization = `Bearer ${token}`; 

    return cfg;
  }))
}

export const Configs = FC<PropsWithChildren>({children}) => {
  const { instance } = useMsal();
  const { url, tenant, scopes } = useConfigs();

  return <Reactxios<ConfigProps>
    setup={Setup}

    msal={instance}
    url={url}
    tenant={tenant}
    scopes={scopes}
  >
    { children }
  </Reactxios>
}

Credits

This package was written by and is maintained by Elliot Gibson.