前端应用
state-management
更新于 2026-08-22
State Management 工程规则
Client state rules: server state vs UI state separation and cache ownership
- 技术栈
- State Management
- 主题
- 工程基线
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Keep components pure during render; move side effects into effects or event handlers
- ✓ Lift state only as high as the closest common consumer needs it
- ✓ Give every list a stable key derived from the item identity, never from the array index when order can change
✕ 常见反模式
- ✕ Deriving state in useEffect when a plain computed value would do
- ✕ Passing fresh object or function literals into memoized children every render
- ✕ Mixing data fetching concerns directly into presentational leaf components
◎ 交付前验证
- ◎ React DevTools profiler shows no render loops after the change
- ◎ Strict Mode double-invocation does not duplicate side effects
- ◎ Server and client render output match (no hydration mismatch warnings)
同分类条目
40 篇前端应用
React 工程规则
React 19 delivery rules: pure render, server actions and stable list identity
前端应用
Next.js 工程规则
Next.js 15 App Router rules: async cookies/headers and server/client boundary discipline
前端应用
Nuxt 工程规则
Nuxt 3 rules: data fetching composables and SSR-safe state
前端应用
Vue 工程规则
Vue 3 Composition API rules: pure computed state and typed props
前端应用
Svelte 工程规则
Svelte 5 rules: runes-based reactivity and effect discipline
前端应用
Solid 工程规则
Solid.js rules: fine-grained reactivity without dependency-array leakage