Stuck on React 16 or 17
Dependencies are falling behind, security advisories have piled up, and new hires have not worked on a pre-18 codebase in years. Every attempt to upgrade stalls on one library.
Upgraded, tests green, no new warnings
Working with React?
Most React apps that reach us were started on one major version and have been dragged along ever since, picking up class components, context providers and state libraries on the way. We work out which parts still earn their keep, update the rest, and leave the console quiet.
What it is
React is a JavaScript library for building user interfaces, created at Facebook (now Meta) and first released in 2013. It is open source under the MIT licence and introduced the component model, JSX and the virtual DOM that most of the front end industry eventually settled on.
Hooks arrived in 2019 and replaced classes for day to day work. React 18 (2022) added concurrent rendering and automatic batching, and React 19 added Actions and Server Components in Next.js. It powers a large share of the modern web, from small dashboards to apps that millions of people use daily.
The honest version
No technology is all upside. This is where React earns its place and where it tends to cause trouble.
Sound familiar?
The React problems that bring people to us, and what you have once each one is fixed.
Dependencies are falling behind, security advisories have piled up, and new hires have not worked on a pre-18 codebase in years. Every attempt to upgrade stalls on one library.
Upgraded, tests green, no new warnings
Context providers pass fresh objects on every render, parent state updates cascade everywhere, and memoisation was added later without measuring whether it helped.
Renders down to what the screen needs
Server markup and client markup differ because of dates, random ids, or code that reads window during render. The warning hides a real bug underneath.
Pages render the same on both sides
A hook sits behind an if or an early return, so the hook order changes mid-session. It works locally and fails in production.
Hook rules enforced, lint turned up
CRA is retired, Webpack config is frozen on an old version, and cold starts hurt every pull request.
Vite build, seconds not minutes
Old screens still use componentDidMount and HOCs; new screens use hooks. Shared logic is duplicated because the two shapes do not compose.
One pattern across the codebase
Every route pulls in every library, there is no code splitting, and icon packs ship in full.
Routes split, bundle under budget
Redux for some screens, context for others, a bit of Zustand that someone tried on a Friday. Server state and client state are tangled together.
One place for each kind of state
What we do
Call us for one stuck upgrade, or hand us the whole front end.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. We go through the deprecations in order, switch ReactDOM.render to createRoot, work through Strict Mode and Suspense changes, and update the libraries that break along the way. We rehearse the upgrade on a branch and only merge when the test suite and the real screens both pass.
Usually a context provider that passes a fresh object on every render, parent state that updates more than it needs to, or keys that change between renders. We profile the actual renders instead of sprinkling useMemo around and hoping.
Yes. We do it feature by feature rather than all at once, keeping the public behaviour the same, so the rest of the app does not have to change in step. Tests stay green through each step.
Yes. Hydration errors almost always come from markup that differs between server and client: dates, random ids, code that reads window during render, or conditional output based on things only the browser knows. We find the specific mismatch and remove the cause, not just the warning.
Yes. CRA is retired, so this is the common move now. We port the build and test setup to Vite, keep your existing scripts working, and usually see cold builds drop from over a minute to a few seconds.
Estimates are free. Describe the app and what is going wrong and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: