A page breaks after an update. The build fails on TypeScript errors. A component works locally but fails when the app renders on the server. You need someone to follow the problem through the code and get the affected part working again.

I investigate and fix reproducible issues in existing React, Next.js and Nuxt applications. That can include component behaviour, state handling, routing, hydration, API requests, or a related set of build and type errors.

The starting package covers one agreed issue in one repository. Before work begins, we define what is broken, how to reproduce it and what a successful fix should do. If the investigation reveals a wider problem, I explain the options before expanding the work.

You receive the implementation, checks of the affected behaviour and clear notes on what changed. The aim is a fix you can review and maintain.

Reproduce one reported issue and identify its cause.

Implement the fix in the existing application and follow its conventions.

Check the affected user flow, including relevant responsive or server-rendering behaviour.

Run the applicable existing build, type checks and tests. Add a focused regression test where it will meaningfully protect the fix.

Deliver a branch or pull request with a concise explanation and verification notes.

One consolidated round of feedback within the agreed scope.

Corrections for defects introduced by my changes, reported within 14 calendar days of handoff.

US$350 covers one reproducible bug, or a related group of build errors caused by the same underlying problem, in one existing repository. We agree the affected route, component or build target before starting.

Framework upgrades, repository-wide TypeScript migrations, multiple unrelated defects, new features and infrastructure rebuilds need a separate estimate. Paid tools and hosting are not included. Production deployment can be agreed separately; the starting package delivers reviewed code and handoff notes.

Confirm the problem. I review the reproduction steps, expected behaviour and relevant setup, then confirm the fixed scope.

Investigate and implement. I trace the failure, make the change and keep you informed if the cause affects the agreed scope.

Verify and hand over. I check the affected path, deliver the changes and document any remaining dependency or deployment steps.

The three-business-day delivery period starts when the agreed scope, repository access and required test access are in place. Waiting for missing information or external access may move the delivery date.

Repository access and the branch you want me to use.

A short description or recording of the issue, with reproduction steps.

The expected behaviour and any recent changes that may be relevant.

Setup instructions, relevant error output and test credentials where needed.

An existing test or staging environment if the issue depends on one. Share credentials through an appropriate private channel.