深入探究 React 和 React Native 中使用 TypeScript 的状态管理(2025 版)

57 阅读4分钟

2025年国情咨文 状态管理已从技术考量演变为战略架构决策,它能够成就或毁掉您的应用程序。在 2025 年,随着应用程序处理实时数据、AI 集成和复杂的用户工作流,选择正确的状态管理方法比以往任何时候都更加重要。该领域已经成熟,像Redux Toolkit这样的解决方案已成为企业标准,而像Zustand和Jotai这样的灵活替代方案则占据了中端市场的主导地位。本指南将通过实用的 TypeScript 示例探索现代状态管理生态系统,您可以将其直接应用于您的项目。

为什么国家管理在2025年比以往任何时候都更加重要 假设一个在城市高峰时段运营的送餐应用。该应用必须同时处理以下任务:实时订单跟踪、司机位置更新、库存变化、促销横幅、用户身份验证和支付处理。仅使用本地状态和 Context API 会导致:

性能灾难:单个驱动程序位置更新将触发整个应用程序的重新渲染,导致用户在浏览菜单或下订单时出现明显的滞后。

状态同步的噩梦:由于状态管理分散,不同的组件显示有关订单状态或库存可用性的相互冲突的信息。

调试地狱:如果没有集中状态和开发工具,追踪促销横幅消失或订单处理失败的原因几乎变得不可能。

团队协作挑战:如果没有可预测的状态容器,从事不同功能的多个开发人员将不断与状态结构变化发生冲突。

离线功能限制:实现强大的离线功能和数据同步需要基本解决方案无法提供的复杂状态管理模式。

2025 年的应用格局需要能够处理以下问题的状态管理解决方案:

多设备实时数据同步 AI/ML 模型状态管理 跨平台一致性(Web、iOS、Android) 具有冲突解决功能的离线优先功能 微前端架构支持 大玩家:深入探讨实际实施情况

  1. Context API + Hooks:轻量级冠军 真实场景:具有主题支持(亮/暗/阅读模式)和用户偏好持久性的多语言新闻应用程序。

其工作原理:主题和语言偏好设置很少更改,并且几乎每个组件都会使用它们。较低的更新频率最大限度地减少了性能问题。

TypeScript 实现:

// types/theme.ts export type ThemeMode = "light" | "dark" | "reading"; export type Language = "en" | "es" | "fr" | "de";

export interface AppSettings { theme: ThemeMode; language: Language; fontSize: number; reduceAnimations: boolean; }

// context/AppSettingsContext.tsx import React, { createContext, useContext, useReducer, ReactNode } from "react"; import { AppSettings, ThemeMode, Language } from "../types/theme";

type Action = | { type: "SET_THEME"; payload: ThemeMode } | { type: "SET_LANGUAGE"; payload: Language } | { type: "SET_FONT_SIZE"; payload: number } | { type: "TOGGLE_ANIMATIONS" };

const settingsReducer = (state: AppSettings, action: Action): AppSettings => { switch (action.type) { case "SET_THEME": return { ...state, theme: action.payload }; case "SET_LANGUAGE": return { ...state, language: action.payload }; case "SET_FONT_SIZE": return { ...state, fontSize: action.payload }; case "TOGGLE_ANIMATIONS": return { ...state, reduceAnimations: !state.reduceAnimations }; default: return state; } };

const initialState: AppSettings = { theme: "light", language: "en", fontSize: 16, reduceAnimations: false, };

const AppSettingsContext = createContext<{ settings: AppSettings; dispatch: React.Dispatch; } | null>(null);

export const AppSettingsProvider: React.FC<{ children: ReactNode }> = ({ children, }) => { const [settings, dispatch] = useReducer(settingsReducer, initialState);

// Persist settings to localStorage React.useEffect(() => { localStorage.setItem("appSettings", JSON.stringify(settings)); }, [settings]);

return ( <AppSettingsContext.Provider value={{ settings, dispatch }}> {children} </AppSettingsContext.Provider> ); };

export const useAppSettings = () => { const context = useContext(AppSettingsContext); if (!context) { throw new Error("useAppSettings must be used within AppSettingsProvider"); } return context; };

// components/ThemeToggle.tsx import React from "react"; import { useAppSettings } from "../context/AppSettingsContext"; import { ThemeMode } from "../types/theme";

export const ThemeToggle: React.FC = () => { const { settings, dispatch } = useAppSettings();

const cycleTheme = () => { const themes: ThemeMode[] = ["light", "dark", "reading"]; const currentIndex = themes.indexOf(settings.theme); const nextIndex = (currentIndex + 1) % themes.length; dispatch({ type: "SET_THEME", payload: themes[nextIndex] }); };

return ( <button onClick={cycleTheme} className={theme-btn ${settings.theme}}> Switch to{" "} {settings.theme === "light" ? "Dark" : settings.theme === "dark" ? "Reading" : "Light"}{" "} Mode ); }; 2. Redux Toolkit(RTK):企业标准 真实场景:具有复杂交易流程、实时余额更新、欺诈检测警报和监管合规要求的银行应用程序。

其优势:银行领域需要绝对的可预测性、审计追踪、时间旅行调试以及复杂的异步工作流。RTK 的中间件生态系统、开发者工具和可预测的状态更新至关重要。

TypeScript 实现:www.mxwd.cc

// features/transactions/transactionsSlice.ts import { createSlice, createAsyncThunk, PayloadAction } from "@reduxjs/toolkit"; import { Transaction, TransactionFilters, TransactionState } from "./types"; import { bankingAPI } from "../../api/bankingAPI";

const initialState: TransactionState = { transactions: [], filters: { dateRange: { start: null, end: null }, amountRange: { min: 0, max: 10000 }, categories: [], status: "completed", }, loading: false, error: null, selectedTransaction: null, };

// Async thunk for fetching transactions export const fetchTransactions = createAsyncThunk( "transactions/fetchTransactions", async (filters: TransactionFilters, { rejectWithValue }) => { try { const response = await bankingAPI.getTransactions(filters); return response.data; } catch (error) { return rejectWithValue( error.response?.data?.message || "Failed to fetch transactions" ); } } );

// Async thunk for transferring funds export const transferFunds = createAsyncThunk( "transactions/transferFunds", async ( transferData: { fromAccount: string; toAccount: string; amount: number; description: string; }, { rejectWithValue } ) => { try { const response = await bankingAPI.transfer(transferData); return response.data; } catch (error) { return rejectWithValue( error.response?.data?.message || "Transfer failed" ); } } );

const transactionsSlice = createSlice({ name: "transactions", initialState, reducers: { setFilters: (state, action: PayloadAction<Partial>) => { state.filters = { ...state.filters, ...action.payload }; }, clearFilters: (state) => { state.filters = initialState.filters; }, selectTransaction: (state, action: PayloadAction) => { state.selectedTransaction = state.transactions.find((t) => t.id === action.payload) || null; }, }, extraReducers: (builder) => { builder // Fetch transactions cases .addCase(fetchTransactions.pending, (state) => { state.loading = true; state.error = null; }) .addCase(fetchTransactions.fulfilled, (state, action) => { state.loading = false; state.transactions = action.payload; }) .addCase(fetchTransactions.rejected, (state, action) => { state.loading = false; state.error = action.payload as string; }) // Transfer funds cases .addCase(transferFunds.fulfilled, (state, action) => { state.transactions.unshift(action.payload); }) .addCase(transferFunds.rejected, (state, action) => { state.error = action.payload as string; }); }, });

export const { setFilters, clearFilters, selectTransaction } = transactionsSlice.actions; export default transactionsSlice.reducer;

// features/transactions/TransactionList.tsx import React, { useEffect } from "react"; import { useDispatch, useSelector } from "react-redux"; import { RootState } from "../../app/store"; import { fetchTransactions, setFilters } from "./transactionsSlice"; import { TransactionFilters } from "./types";

export const TransactionList: React.FC = () => { const dispatch = useDispatch(); const { transactions, filters, loading, error } = useSelector( (state: RootState) => state.transactions );

useEffect(() => { dispatch(fetchTransactions(filters)); }, [dispatch, filters]);

const handleFilterChange = (newFilters: Partial) => { dispatch(setFilters(newFilters)); };

if (loading) return

Loading transactions...
; if (error) return
Error: {error}
;

return (

{transactions.map((transaction) => ( ))}
); }; 3. Zustand:极简主义奇迹 真实场景:一种协作设计工具,多个用户可以同时编辑文档,并具有实时光标位置和存在指示器。

优势:Zustand 的简洁性和性能使其成为光标移动等高频更新的理想选择。其较小的软件包体积有利于 Web 应用程序,而简单的 API 则支持快速开发。

TypeScript 实现:

// stores/useCollaborationStore.ts import { create } from "zustand"; import { devtools } from "zustand/middleware"; import { User, CursorPosition, DesignDocument } from "../types/collaboration";

interface CollaborationState { // Document state currentDocument: DesignDocument | null; elements: DesignElement[];

// User presence activeUsers: User[]; userCursors: Record<string, CursorPosition>;

// Actions setCurrentDocument: (doc: DesignDocument) => void; updateElement: (elementId: string, updates: Partial) => void; addElement: (element: DesignElement) => void; setUserCursor: (userId: string, position: CursorPosition) => void; addActiveUser: (user: User) => void; removeActiveUser: (userId: string) => void;

// Derived state getElement: (elementId: string) => DesignElement | undefined; getUsersInDocument: () => User[]; }

export const useCollaborationStore = create()( devtools((set, get) => ({ currentDocument: null, elements: [], activeUsers: [], userCursors: {},

setCurrentDocument: (doc) => set({ currentDocument: doc }),

updateElement: (elementId, updates) =>
  set((state) => ({
    elements: state.elements.map((element) =>
      element.id === elementId ? { ...element, ...updates } : element
    ),
  })),

addElement: (element) =>
  set((state) => ({ elements: [...state.elements, element] })),

setUserCursor: (userId, position) =>
  set((state) => ({
    userCursors: { ...state.userCursors, [userId]: position },
  })),

addActiveUser: (user) =>
  set((state) => ({
    activeUsers: state.activeUsers.some((u) => u.id === user.id)
      ? state.activeUsers
      : [...state.activeUsers, user],
  })),

removeActiveUser: (userId) =>
  set((state) => ({
    activeUsers: state.activeUsers.filter((user) => user.id !== userId),
    userCursors: Object.fromEntries(
      Object.entries(state.userCursors).filter(([id]) => id !== userId)
    ),
  })),

getElement: (elementId) =>
  get().elements.find((element) => element.id === elementId),

getUsersInDocument: () =>
  get().activeUsers.filter(
    (user) => user.currentDocumentId === get().currentDocument?.id
  ),

})) );

// components/CursorTracker.tsx import React, { useEffect } from "react"; import { useCollaborationStore } from "../stores/useCollaborationStore";

export const CursorTracker: React.FC = () => { const { userCursors, getUsersInDocument } = useCollaborationStore(); const users = getUsersInDocument();

return (

{Object.entries(userCursors).map(([userId, position]) => { const user = users.find((u) => u.id === userId); if (!user) return null;

    return (
      <div
        key={userId}
        className="user-cursor"
        style={{ left: position.x, top: position.y }}
      >
        <div className="cursor-arrow" style={{ color: user.color }} />
        <span className="user-name" style={{ backgroundColor: user.color }}>
          {user.name}
        </span>
      </div>
    );
  })}
</div>

); };

// components/DesignCanvas.tsx import React from "react"; import { useCollaborationStore } from "../stores/useCollaborationStore";

export const DesignCanvas: React.FC = () => { const { elements, updateElement, setUserCursor } = useCollaborationStore();

const handleCanvasMouseMove = (event: React.MouseEvent) => { const rect = event.currentTarget.getBoundingClientRect(); const cursorPosition = { x: event.clientX - rect.left, y: event.clientY - rect.top, };

// Update local cursor position in store
setUserCursor("current-user-id", cursorPosition);

// In a real app, you'd also send this to other collaborators via WebSocket

};

return (

{elements.map((element) => ( <DesignElement key={element.id} element={element} onUpdate={(updates) => updateElement(element.id, updates)} /> ))}
); }; 4. React Query / TanStack Query:数据获取大师 真实场景:社交媒体仪表板显示来自多个trx租赁端点的个性化内容提要、通知、用户配置文件和分析数据。

工作原理:React Query 可以轻松处理服务器状态同步、缓存、后台更新和分页。它消除了手动管理加载状态、错误处理和缓存逻辑的需要。

TypeScript 实现:

// hooks/useSocialData.ts import { useQuery, useMutation, useQueryClient } from "@tanstack/react-query"; import { socialAPI } from "../api/socialAPI"; import { Post, UserProfile, Notification } from "../types/social";

// Query keys for consistent caching export const queryKeys = { posts: (filters?: any) => ["posts", filters], post: (id: string) => ["post", id], profile: (userId: string) => ["profile", userId], notifications: ["notifications"], };

// Custom hook for posts with filters export const usePosts = (filters: { type?: string; userId?: string } = {}) => { return useQuery<Post[], Error>({ queryKey: queryKeys.posts(filters), queryFn: () => socialAPI.getPosts(filters), staleTime: 5 * 60 * 1000, // Consider data fresh for 5 minutes gcTime: 30 * 60 * 1000, // Keep unused data in cache for 30 minutes }); };

// Custom hook for user profile export const useUserProfile = (userId: string) => { return useQuery<UserProfile, Error>({ queryKey: queryKeys.profile(userId), queryFn: () => socialAPI.getUserProfile(userId), enabled: !!userId, // Only fetch if userId is available }); };

// Custom hook for notifications with real-time updates export const useNotifications = () => { return useQuery<Notification[], Error>({ queryKey: queryKeys.notifications, queryFn: () => socialAPI.getNotifications(), refetchInterval: 30000, // Auto-refresh every 30 seconds }); };

// Mutation for creating a new post export const useCreatePost = () => { const queryClient = useQueryClient();

return useMutation({ mutationFn: (postData: { content: string; media?: File }) => socialAPI.createPost(postData), onSuccess: (newPost) => { // Update the posts cache with the new post queryClient.setQueryData<Post[]>(queryKeys.posts(), (oldPosts = []) => [ newPost, ...oldPosts, ]);

  // Invalidate and refetch to ensure we have the latest data
  queryClient.invalidateQueries({ queryKey: queryKeys.posts() });
},
onError: (error) => {
  console.error("Failed to create post:", error);
  // Show error notification to user
},

}); };

// components/NewsFeed.tsx import React from "react"; import { usePosts, useCreatePost } from "../hooks/useSocialData"; import { PostCard } from "./PostCard"; import { CreatePostForm } from "./CreatePostForm";

export const NewsFeed: React.FC = () => { const { data: posts, isLoading, error } = usePosts(); const createPostMutation = useCreatePost();

const handleCreatePost = (content: string, media?: File) => { createPostMutation.mutate({ content, media }); };

if (isLoading) return

Loading posts...
; if (error) return
Error: {error.message}
;

return (

  <div className="posts-container">
    {posts?.map((post) => (
      <PostCard key={post.id} post={post} />
    ))}
  </div>

  {posts?.length === 0 && (
    <div className="empty-state">
      <p>No posts yet. Be the first to share something!</p>
    </div>
  )}
</div>

); }; 决策框架:为您的2025项目选择正确的解决方案 项目类型 推荐的解决方案 关键考虑因素 小型企业应用程序 Context API + useReducer 简单,无依赖,内置于 React。非常适合状态更新较少的低复杂度应用。 中等复杂度的应用程序 立场 + React 查询 性能卓越,样板代码精简,开发体验出色。非常适合初创企业和中型应用。 企业应用程序 Redux 工具包 + RTK 查询 可预测的状态流、出色的开发者工具、强大的生态系统。对于大型团队和复杂的业务逻辑至关重要。 实时协作应用程序 立场/Recoil + WebSockets 细粒度更新,极少重新渲染。非常适合具有实时协作功能的应用。 数据密集型仪表板 React 查询 + 状态 卓越的数据同步、缓存和后台更新功能。非常适合仪表板和分析平台。 跨平台移动应用程序 Redux Toolkit 或 Zustand 跨 iOS 和 Android 的一致状态管理。Redux 适用于复杂应用,Zustand 适用于简单应用。 2025年的先进模式

  1. 与 XState 的状态机集成 对于关键任务工作流程(支付处理、入职流程),将您的状态管理解决方案与 XState 结合起来:

// machines/checkoutMachine.ts import { createMachine, assign } from "xstate"; import { useMachine } from "@xstate/react"; import { checkoutAPI } from "../api/checkout";

interface CheckoutContext { cartItems: CartItem[]; shippingAddress: Address | null; paymentMethod: PaymentMethod | null; orderId: string | null; error: string | null; }

type CheckoutEvent = | { type: "SET_SHIPPING"; address: Address } | { type: "SET_PAYMENT"; method: PaymentMethod } | { type: "CONFIRM_ORDER" } | { type: "RETRY" };

export const checkoutMachine = createMachine<CheckoutContext, CheckoutEvent>({ id: "checkout", initial: "shipping", context: { cartItems: [], shippingAddress: null, paymentMethod: null, orderId: null, error: null, }, states: { shipping: { on: { SET_SHIPPING: { actions: assign({ shippingAddress: (, event) => event.address, }), target: "payment", }, }, }, payment: { on: { SET_PAYMENT: { actions: assign({ paymentMethod: (, event) => event.method, }), target: "review", }, }, }, review: { on: { CONFIRM_ORDER: "processing", }, }, processing: { invoke: { src: (context) => checkoutAPI.processOrder({ items: context.cartItems, shipping: context.shippingAddress!, payment: context.paymentMethod!, }), onDone: { actions: assign({ orderId: (, event) => event.data.orderId, }), target: "success", }, onError: { actions: assign({ error: (, event) => event.data.message, }), target: "failure", }, }, }, success: { type: "final" }, failure: { on: { RETRY: "processing", }, }, }, });

// components/CheckoutFlow.tsx export const CheckoutFlow: React.FC = () => { const [state, send] = useMachine(checkoutMachine);

return (

{state.matches("shipping") && ( <ShippingForm onSubmit={(address) => send({ type: "SET_SHIPPING", address })} /> )}

  {state.matches("payment") && (
    <PaymentForm
      onSubmit={(method) => send({ type: "SET_PAYMENT", method })}
    />
  )}

  {state.matches("review") && (
    <OrderReview
      context={state.context}
      onConfirm={() => send({ type: "CONFIRM_ORDER" })}
    />
  )}

  {state.matches("processing") && <ProcessingSpinner />}

  {state.matches("failure") && (
    <ErrorDisplay
      error={state.context.error}
      onRetry={() => send({ type: "RETRY" })}
    />
  )}

  {state.matches("success") && (
    <OrderConfirmation orderId={state.context.orderId!} />
  )}
</div>

); }; 2. 使用 Zustand 和 React Query 的离线优先策略 // stores/useOfflineStore.ts import { create } from "zustand"; import { persist, createJSONStorage } from "zustand/middleware"; import { asyncStorage } from "zustand/middleware";

interface OfflineState { queue: Array<{ id: string; type: string; payload: any; timestamp: number; }>; addToQueue: (action: { type: string; payload: any }) => void; processQueue: () => Promise; clearProcessed: (ids: string[]) => void; }

export const useOfflineStore = create()( persist( (set, get) => ({ queue: [],

  addToQueue: (action) => {
    const id = Math.random().toString(36).substr(2, 9);
    set((state) => ({
      queue: [...state.queue, { id, ...action, timestamp: Date.now() }],
    }));
  },

  processQueue: async () => {
    const { queue, clearProcessed } = get();
    const successfulIds: string[] = [];

    for (const item of queue) {
      try {
        // Execute the action based on type
        switch (item.type) {
          case "CREATE_POST":
            await socialAPI.createPost(item.payload);
            break;
          case "UPDATE_PROFILE":
            await socialAPI.updateProfile(item.payload);
            break;
          // Add more action types as needed
        }
        successfulIds.push(item.id);
      } catch (error) {
        console.error(`Failed to process action ${item.id}:`, error);
      }
    }

    clearProcessed(successfulIds);
  },

  clearProcessed: (ids) => {
    set((state) => ({
      queue: state.queue.filter((item) => !ids.includes(item.id)),
    }));
  },
}),
{
  name: "offline-queue",
  storage: createJSONStorage(() => asyncStorage),
}

) );

// hooks/useOfflineSync.ts export const useOfflineSync = () => { const { processQueue, queue } = useOfflineStore(); const queryClient = useQueryClient();

// Process queue when coming online useEffect(() => { const handleOnline = () => { if (queue.length > 0) { processQueue().then(() => { // Refetch all queries to sync with server queryClient.invalidateQueries(); }); } };

window.addEventListener("online", handleOnline);
return () => window.removeEventListener("online", handleOnline);

}, [processQueue, queue.length, queryClient]);

return { pendingActions: queue.length }; }; 结论:构建未来 到 2025 年,状态管理不再是选择单个库,而是创建解决不同问题的分层架构:

服务器状态:使用 React Query/TanStack Query 进行数据获取、缓存和同步 客户端状态:选择 Zustand 以实现简单性,或选择 Redux Toolkit 以实现复杂的应用程序 工作流状态:在关键流程中为有限状态机实现 XState 持久层:将解决方案与智能持久策略相结合,以提供离线支持 最成功的应用程序会结合使用这些工具,充分利用每种工具的优势,同时保持清晰的关注点分离。请记住,最好的状态管理解决方案是让你的应用程序可靠、可维护且开发体验愉悦的解决方案,而不一定是在 GitHub 上获得最多 Stars 的解决方案。

当您在 2025 年构建下一个应用程序时,请考虑从服务器状态的 React Query 和客户端状态的 Zusand 开始,然后根据应用程序的复杂性要求扩展到更专业的解决方案。