This Only Happens in Development
You'll learn: Why the double-fetch behavior you see during development vanishes when your app goes live.
The Relief: It's Only for You
When you've been wrestling with useEffect running twice and seeing two network requests on mount, here's the good news: this behavior is completely stripped out in production builds. Your actual users will never experience the double-mounting that StrictMode intentionally causes.
StrictMode is a development-only tool. When you run npm run build or create a production bundle, React removes all StrictMode checks. The extra mount-unmount-remount cycle? Gone. The double network fetch? Gone.
Your users see exactly what you'd expect: one mount, one effect run, one fetch.
Why This Matters
This means the "problem" you've been solving with cleanup functions isn't actually causing user-facing issues. The abort signals and ignore flags you implement serve a different purpose: they protect against real race conditions that can happen when dependencies change rapidly or components unmount unexpectedly.
Think of StrictMode like a smoke detector that beeps during drills but stays silent when guests are over. It's deliberately annoying in development to force you to write resilient code, but it doesn't bother your production users.
The Lesson Behind the Annoyance
React's double-mounting teaches you to handle effects that can run multiple times, effects that need cleanup, and effects that might be interrupted. These are real scenarios that can happen in production (just not from StrictMode itself), so the training is valuable even though the specific trigger is development-only.
Key Takeaway: StrictMode's double-mounting only happens in development builds—production users see one mount and one effect run, but your cleanup code still protects against real-world race conditions and unmounts.