Series: Axios Lesson 100

API Client Outside Components — Axios instance'ni component'lardan tashqarida boshqarish

Axios instansiyasini React komponentlaridan tashqarida toza modul sifatida boshqarish: Singleton Pattern, React Hooks cheklovlari (useNavigate muammosi), Navigation Helper va markazlashgan token arxitekturasi.

100-dars

API Client Outside Components — Axios instance'ni component'lardan tashqarida boshqarish

React loyihalarida dasturchilar yo'l qo'yadigan eng jiddiy arxitekturaviy xatolardan biri — bu Axios instansiyasini yoki uning interceptorlarini to'g'ridan-to'g'ri React komponentlari ichida (useEffect yoki hodisa ishlovchilarida) yaratish yoki sozlashdir.

API mijozini (API Client) komponentlar daraxtidan butunlay tashqarida, ya'ni alohida src/api/client.ts moduli sifatida Singleton Pattern tamoyili asosida boshqarish zamonaviy frontend arxitekturasining poydevori hisoblanadi.


1. Nima uchun API Client komponentlardan tashqarida bo'lishi shart?

flowchart TD
    subgraph Xavfli["❌ Komponent ichida (Anti-pattern)"]
        CompA["ProfileComponent (useEffect)"] --> Inst1["Yangi Axios Instansiyasi #1"]
        CompB["OrdersComponent (useEffect)"] --> Inst2["Yangi Axios Instansiyasi #2"]
        Inst1 -.->|Har renderda takrorlanuvchi interceptorlar| Bug["Xotira sizishi (Memory Leaks) & ziddiyatlar"]
    end

    subgraph Toza["✅ Komponentlardan tashqarida (Singleton)"]
        ClientMod["src/api/client.ts\n(Yagona apiClient + Interceptors)"]
        ServiceA["UserService"] --> ClientMod
        ServiceB["OrderService"] --> ClientMod
        Comp1["ProfileComponent"] --> ServiceA
        Comp2["OrdersComponent"] --> ServiceB
    end

Asosiy afzalliklari:

  1. Clean Architecture (Ajratilgan mas'uliyat): UI komponentlari faqat ma'lumotlarni chizish va foydalanuvchi bilan muloqot uchun javob beradi. Tarmoq konfiguratsiyasi, tokenlar, sarlavhalar va qayta urinishlar biznes-mantiq qatlamida yashirin bo'ladi.
  2. Global Yagona Instansiya (Singleton): Butun dastur bo'ylab barcha so'rovlar bitta markaziy apiClient orqali o'tadi. Bu barcha so'rovlarning bir xil baseURL, timeout va xavfsizlik filtrlari ostida ishlashini kafolatlaydi.
  3. Interceptorlar Takrorlanishining Oldini Olish: Agar interceptor komponent ichida qo'shilsa, komponent har safar qayta render bo'lganda yangi interceptor qo'shilib, so'rovlar bir necha marta ko'payib ketishi (interceptor leak) mumkin.

2. Asosiy To'siq: Interceptor ichida React Hook'lari ishlamaydi!

Axios mijozini React'dan tashqarida saqlashning eng mashhur qiyinchiligi bor:

[!CAUTION] React Hooks Qoidasi: React Hook'larini (useNavigate(), useLocation(), useDispatch()) faqat va faqat React funksional komponentlari yoki boshqa maxsus hooklar ichidagina chaqirish mumkin.

Agar src/api/client.ts faylidagi Response Interceptor ichida 401 Unauthorized bo'lganda foydalanuvchini login sahifasiga yo'naltirmoqchi bo'lsak, const navigate = useNavigate() deb yoza olmaymiz:

Invalid hook call. Hooks can only be called inside of the body of a function component.

3. Yechim: Navigatsiya va Holatni Tashqaridan Boshqarish Usullari

Ushbu muammoni hal qilishning 3 ta sinalgan professional usuli mavjud:

1-Usul: Hard Redirect (window.location.href) — Eng ishonchli usul

Agar Refresh Token muddati ham tugagan bo'lsa, bu foydalanuvchi seansi to'liq yakunlanganini bildiradi. Bunday paytda window.location.href = '/login' orqali sahifani yangilab o'tish eng xavfsizidir:

  • Brauzer xotiradagi barcha eski qoldiqlarni to'liq tozalaydi;
  • React kontekstiga yoki router versiyasiga bog'lanib qolmaydi.

2-Usul: Navigation Helper (SPA ichida qayta yuklanmasdan o'tish)

Agar sahifani to'liq yangilamasdan (soft redirect) yo'naltirish kerak bo'lsa, kichik navigatsiya yordamchisi tuziladi:

// src/utils/navigation.ts
type NavigateFunction = (path: string) => void;

let navigateFn: NavigateFunction | null = null;

export const setNavigationHandler = (fn: NavigateFunction) => {
  navigateFn = fn;
};

export const navigateTo = (path: string) => {
  if (navigateFn) {
    navigateFn(path);
  } else {
    window.location.href = path; // Fallback
  }
};

Ilovaning boshlang'ich nuqtasida (App.tsx yoki RouterSetup.tsx):

import { useNavigate } from 'react-router-dom';
import { setNavigationHandler } from './utils/navigation';

export const NavigationBinder = () => {
  const navigate = useNavigate();
  useEffect(() => {
    setNavigationHandler(navigate);
  }, [navigate]);
  return null;
};

4. Amaliyot: Mukammal Tashqi client.ts Arxitekturasi

Quyida barcha token boshqaruvi, avtomatik refresh va toza chiqish funksiyalarini React'dan tashqarida xavfsiz jamlagan to'liq kod keltirilgan:

// src/api/client.ts
import axios, { AxiosError, InternalAxiosRequestConfig } from 'axios';

// 1. In-Memory Token Manager (Komponentlardan mustaqil xotirada yashaydi)
let memoryAccessToken: string | null = null;

export const TokenManager = {
  getToken: (): string | null => memoryAccessToken,
  setToken: (token: string | null): void => {
    memoryAccessToken = token;
  },
  clearToken: (): void => {
    memoryAccessToken = null;
  },
};

// 2. Yagona global Axios instansiyasi
export const apiClient = axios.create({
  baseURL: import.meta.env.VITE_API_BASE_URL || 'https://api.mysite.com/v1',
  timeout: 10000,
  withCredentials: true, // HttpOnly Cookie uchun
});

// 3. REQUEST INTERCEPTOR: Har bir so'rovga tokenni avtomatik qo'shish
apiClient.interceptors.request.use(
  (config: InternalAxiosRequestConfig) => {
    const token = TokenManager.getToken();
    if (token && config.headers) {
      config.headers.Authorization = `Bearer ${token}`;
    }
    return config;
  },
  (error) => Promise.reject(error)
);

// 4. RESPONSE INTERCEPTOR: 401 holatini tashqarida global boshqarish
apiClient.interceptors.response.use(
  (response) => response,
  async (error: AxiosError) => {
    const originalRequest = error.config as
      | (InternalAxiosRequestConfig & { _retry?: boolean })
      | undefined;

    if (error.response?.status === 401 && originalRequest && !originalRequest._retry) {
      // Cheksiz siklning oldini olamiz
      if (originalRequest.url?.includes('/auth/refresh')) {
        TokenManager.clearToken();
        if (!window.location.pathname.includes('/login')) {
          window.location.href = '/login';
        }
        return Promise.reject(error);
      }

      originalRequest._retry = true;

      try {
        // Yashirin refresh so'rovi (toza axios chaqiruvi)
        const res = await axios.post<{ accessToken: string }>(
          'https://api.mysite.com/v1/auth/refresh',
          {},
          { withCredentials: true }
        );

        const newToken = res.data.accessToken;
        TokenManager.setToken(newToken);

        if (originalRequest.headers) {
          originalRequest.headers.Authorization = `Bearer ${newToken}`;
        }

        // Asl so'rovni yangi token bilan takrorlaymiz
        return apiClient(originalRequest);
      } catch (refreshError) {
        // Refresh ham o'xshamasa -> toza chiqish
        TokenManager.clearToken();
        localStorage.removeItem('user_profile');

        if (!window.location.pathname.includes('/login')) {
          const currentUrl = encodeURIComponent(window.location.pathname + window.location.search);
          window.location.href = `/login?redirect=${currentUrl}`;
        }

        return Promise.reject(refreshError);
      }
    }

    return Promise.reject(error);
  }
);

5. Komponentlar va Servislar Uchun Qulaylik

Ushbu qat'iy ajratilgan arxitektura sababli, istalgan servis va komponent mutlaqo yengil va toza ko'rinishga ega bo'ladi:

// src/services/todoService.ts
import { apiClient } from '../api/client';

export interface Todo {
  id: number;
  title: string;
  completed: boolean;
}

export const TodoService = {
  getTodos: async (): Promise<Todo[]> => {
    // Komponent faqat ma'lumotni so'raydi, barcha token, refresh va xatoliklar fonda bajariladi!
    const res = await apiClient.get<Todo[]>('/todos');
    return res.data;
  },
};

6. Ichkarida vs Tashqarida Taqqoslovi

Mezon Komponent Ichida Sozlash Komponentdan Tashqarida (client.ts)
Instansiyalar soni Har bir komponent yoki renderda yangilanadi Butun ilova uchun yagona (Singleton)
Interceptor xavfi Duplikatsiya va xotira sizishi (Memory leak) Bir marta xavfsiz ro'yxatdan o'tadi
Testlash qulayligi Juda qiyin (React rendering talab qiladi) Juda oson (oddiy modul sifatida mock qilinadi)
Navigatsiya (Redirect) useNavigate oson ishlaydi window.location yoki Navigation Helper talab etiladi
Arxitektura tozaligi Tartibsiz va qorishiq (Spaghetti code) Qat'iy ajratilgan (Clean Architecture)

Xulosa

Axios instansiyasini React komponentlari ichida emas, balki ulardan tashqarida yagona mustaqil modul sifatida boshqarish — bu professional veb-dasturlashning oltin qoidasidir.

Ushbu yondashuv orqali siz:

  • Interceptorlar takrorlanishining oldini olasiz;
  • Tokenlar va avtomatik refresh mantiqini UI kodlaridan butunlay yashirasiz;
  • Ilovangizni yengil, kengaytiriluvchan va oson testlanuvchan holatga keltirasiz.