Still on Create React App
How you'll know: react-scripts in package.json, and builds that print deprecation warnings or block newer libraries.
Fix: Move to Vite for a browser-only app, or to a framework if the app needs server rendering. The components mostly carry over. The build config, environment variables and test runner are what change.
Effects feeding effects
How you'll know: Several useEffect calls that each set state the next one watches, and screens that flicker or show old values for a moment.
Fix: Calculate derived values during render, and move data loading into the framework's loaders or a fetching library that handles caching and cancellation.
One context that re-renders everything
How you'll know: Typing in one field makes the whole page lag, because a single context holds the user, the theme, the cart and the form.
Fix: Split context by how often each value changes, or move fast-changing state down to the components that use it.
'use client' at the top of every file
How you'll know: A Next.js app that ships as much JavaScript as a browser-only app would.
Fix: Move the boundary down to the interactive pieces, such as forms, menus and charts, so the rest renders on the server.
Data fetched in an effect with no cleanup
How you'll know: Switch customers quickly and the screen shows the previous one's details.
Fix: Cancel or ignore stale requests, or let a fetching library track which response belongs to which request.