package.json & Tooling — Complete Guide
package.json & Tooling — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of React.js Tutorial on Toolliyo Academy.
On this page
React.js Tutorial · Lesson 50 of 100
Enterprise State Architecture
Beginner ✓ → Intermediate ✓ → Advanced → Professional
Advanced · 3 — Production skills · ~18 min read · Module 5: API & State Management
Introduction
This is advanced material: Enterprise State Architecture. It is what teams use on live products. Read the example carefully and try changing one line at a time to see what happens. State architecture is deciding what lives where: local useState, Context, Zustand, Redux, or TanStack Query. Server data and UI state are usually separated. Mixing everything in one global store causes bugs. Clear rules help teams scale.
State mistakes cause the most React bugs for beginners. Keep server data and UI state separate — this lesson shows how teams do that.
When will you use this?
Use these patterns when data is shared across pages or comes from a server.
- Shopping carts, user sessions, and API data need clear state patterns.
- Teams pick Context, Zustand, or Redux based on app size — you will see all three in jobs.
Real-world: where state lives
Architecture doc for SaaS: server data in Query, UI filters in Zustand, form drafts in local useState, auth in Context.
Production-style code
/*
Toolliyo state map:
- TanStack Query → courses, enrollments, quiz results (server)
- Zustand → sidebar open, active filter chips (client UI)
- useState → single form field focus, modal open (local)
- Context → user session, theme (app-wide, low churn)
- NOT in Redux → avoid duplicating Query cache in Redux
*/
function CoursePage({ id }) {
const { data: course } = useQuery({ queryKey: ['course', id], queryFn: () => fetchCourse(id) });
const filter = useFilterStore(s => s.tag);
const [tab, setTab] = useState('outline');
}
What happens in production: Teams avoid "everything in Redux" anti-pattern — clearer mental model and fewer bugs at scale.
Lesson example (start here)
Copy this smaller example first. Once it works, compare it with the real-world code above.
// Server data → TanStack Query
// Global UI (theme, sidebar) → Context or Zustand
// Form typing → local useState
// Cart (needs persist) → Zustand or Redux
Line-by-line walkthrough
| Code | What it means |
|---|---|
// Server data → TanStack Query | Comment — notes for humans; the computer ignores it. |
// Global UI (theme, sidebar) → Context or Zustand | Comment — notes for humans; the computer ignores it. |
// Form typing → local useState | Comment — notes for humans; the computer ignores it. |
// Cart (needs persist) → Zustand or Redux | Comment — notes for humans; the computer ignores it. |
How it works (big picture)
- Ask: does this come from the API?
- Use Query.
- Is it only this screen?
- useState.
- Shared across app?
- Context/Zustand/Redux.
Do this on your computer
- List all data types in your app.
- Assign each to local, server, or global client state.
- Avoid duplicating server data in Redux.
- Read the real-world section and name which part of the app uses this topic.
- Run the example locally and confirm the same behavior in the browser.
- Change one value in the example (text, initial state, or URL) and predict what will happen before you save.
Experiments — try changing this
- Change text or labels in the example and save — watch the browser update.
- Break the code on purpose (remove a bracket), read the error message, then fix it.
- Change the initial state value and see the starting UI change.
- Open React DevTools (browser extension) while running Enterprise State Architecture and inspect component props/state.
Remember
Server state → TanStack Query. Local UI → useState. Shared client state → Context/Zustand/Redux by complexity.
Common questions
One library for everything?
No — use the right tool per data type.
How long should I spend on Enterprise State Architecture?
Until you can explain it in your own words and run the example without looking at the answer. Beginners often need 30–60 minutes per new hook or routing topic; setup lessons may take one afternoon.
What if I get stuck on Enterprise State Architecture?
Re-read the line-by-line walkthrough, check the browser console for red errors, and compare your code character-by-character with the example. Search the exact error text — someone else had it too.
Where is Enterprise State Architecture used in real jobs?
See the real-world section above — the same pattern appears in LMS, banking, e-commerce, and SaaS products. Interviewers ask you to explain it using one concrete example from your project or this lesson.