Retrying request after refreshing JWT access token in response interceptor

I understand that interceptors are a good way to um, intercept, when my server responds with 401 because the JWT access token has expired. So far, I have something like:

const api = new Frisbee(...);

const refreshAccessToken = async () => {
  const refreshToken = await SecureStore.getItemAsync('refreshToken');
  api.jwt(refreshToken);
  const res = await post('/users/refresh/');
  api.jwt(res.body.access_token);
};

const accessTokenRefresher = {
  async response(response) {
    if (response.status === 401 && response.body.msg === 'Token has expired') {
      await refreshAccessToken();
    }
    return response;
  },
};

api.interceptor.register(accessTokenRefresher);

This is a good start. My Expo app calls /users/refresh/ on 401, and updates the access token as expected. But then I need to call the original URL again (the one that returned the 401 in the first place). What’s the recommended pattern for this? (I can’t access request from response.) Do I need to separately maintain some global state for the last attempted request, and exclude /users/refresh/ from that? It feels messy, hope there’s a nicer way to do this.

[niftylettuce]

@rommyarb yes this works great for React.

[niftylettuce]

Closing in favor of #92