Working with React?

React app slow, warning-spammed or two majors behind? We fix it.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

console

still failing

What it is

React at a glance

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.

Type
JavaScript UI library
First released
2013
License
MIT, free and permissive
Maintained by
Meta and open source contributors
Typically used for
Single-page apps, dashboards, marketing sites via Next.js, mobile via React Native, design systems

The honest version

React pros and cons

No technology is all upside. This is where React earns its place and where it tends to cause trouble.

Where React is strong

  • The model the industry agreed onComponents, props and one way data flow are now the shape of front end work almost everywhere. Hiring, documentation and examples all assume you build this way.
  • An ecosystem that already has the piece you needNext.js, Remix, React Native, React Query, Tanstack Router and a long list of design systems all slot into a React app without a rewrite.
  • Strict Mode and good development toolsThe browser extension shows renders, props and context at a glance, and Strict Mode surfaces unsafe patterns during development before they ship.
  • Server Components where they fitUsed through Next.js, server components let data fetching sit next to the markup it feeds, which cuts client bundle size for pages that are mostly read-only.
  • First class TypeScriptTypes for props, hooks and events are supported by the whole ecosystem, so refactors stay safe as a codebase grows past a few thousand files.
  • Concurrent rendering when you need itTransitions, Suspense for data and automatic batching let heavy screens stay responsive without rewriting the components doing the work.

Where React bites

  • Every major version broke somethingReact 16 to 17 to 18 each changed patterns teams depended on: ReactDOM.render was deprecated for createRoot, Suspense semantics shifted, and server rendered pages started throwing hydration errors that had been silent before.
  • The hook rules are easy to breakHooks have to run in the same order on every render, and the lint rule that enforces it is advisory. One early return or one conditional hook is enough to turn a working screen into a crash.
  • Re-render footgunsComponents can render far more than they should, and the common response is to scatter useMemo and useCallback everywhere, which rarely helps and makes the code harder to read.
  • State management choice fatigueRedux, Zustand, Jotai, Recoil, plain context, React Query, server state in Next.js. Every team picks a different mix and nobody is quite sure which parts the next team will keep.
  • Class components still live in old codeAny codebase that predates 2019 still has some classes, lifecycle methods and HOCs in it. They work, but patterns from that era do not mix cleanly with hooks around them.
  • The toolchain keeps shiftingCreate React App was the default starter for years and is now retired. Teams have moved to Vite, Next.js or custom setups, and build configuration has become a running cost of its own.

Sound familiar?

Common React problems we fix

The React problems that bring people to us, and what you have once each one is fixed.

ReactDOM.render is no longer supported in React 18

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

Profiler: 142 renders per interaction

The UI re-renders constantly

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

Warning: Hydration failed because the initial UI does not match

Hydration errors on Next.js

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

Rendered more hooks than during the previous render

A screen crashes on a specific interaction

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 build: 94s

The Create React App build is slow

CRA is retired, Webpack config is frozen on an old version, and cold starts hurt every pull request.

Vite build, seconds not minutes

class App extends React.Component

Half classes, half hooks

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

bundle: 1.8 MB gzipped

The bundle is too big to load on mobile

Every route pulls in every library, there is no code splitting, and icon packs ship in full.

Routes split, bundle under budget

state libs: 3 in one repo

Nobody agrees where state lives

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

React help, from upgrade to upkeep

Call us for one stuck upgrade, or hand us the whole front end.

Version upgrades
React 16 or 17 to 18 or 19, with the deprecations, hydration errors and library updates worked through in order.
Performance
Render profiling, memoisation where it actually helps, code splitting and bundle budgets, measured before and after.
Class to hooks
Converting legacy class components and HOCs to function components, one feature at a time, with tests kept green.
State and data
Picking one approach for server state and one for client state, and removing the libraries you no longer need.
Toolchain
Moving off Create React App to Vite or Next.js, with CI, type checking and lint rules that catch hook mistakes early.
Managed Tech
Dependency updates, monitoring and a team to call, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running React alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

React questions

Something else? Call+1 737 727 7327

Can you upgrade our React 16 or 17 app to React 18 or 19?

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.

Why does our React app re-render so much?

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.

Can you convert our class components to function components with hooks?

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.

Our React app has hydration errors on Next.js, can you fix them?

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.

Our Create React App build is slow, can you migrate to Vite?

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.

How much does React help cost?

Estimates are free. Describe the app and what is going wrong and you get a price before any work begins.

Free estimate

React app giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.