The last developer walked out
A production front end whose build no longer runs on a modern machine, with no README, no notes and the only contractor unreachable.
Building, documented, back in your hands
Working with JavaScript?
Most JavaScript projects that reach us were written across many hands and many years, with a mix of old patterns and new ones layered on top. We work out which parts still earn their keep and which parts are quietly causing the trouble, without demanding a rewrite.
What it is
JavaScript is the dynamic, prototype-based language that Brendan Eich put together in ten days at Netscape in 1995. It was standardised as ECMAScript and is now looked after by the TC39 committee, which ships a new edition every year.
It runs in every web browser, on the server through Node.js (added in 2009), and in newer runtimes such as Deno, Bun, Cloudflare Workers and small embedded engines like QuickJS. Modern JavaScript from ES2020 onwards has classes, modules, async and await, optional chaining, nullish coalescing and private fields, and remains the largest language on the web by number of developers in active use.
The honest version
No technology is all upside. This is where JavaScript earns its place and where it tends to cause trouble.
Sound familiar?
The JavaScript problems that bring people to us, and what you have once each one is fixed.
A production front end whose build no longer runs on a modern machine, with no README, no notes and the only contractor unreachable.
Building, documented, back in your hands
Pages built in the 2010s with heavy jQuery, an ad-hoc plugin stack and inline handlers, still central to the business.
Modernised in place, not thrown away
A dashboard that works on the developer's laptop and throws in the wild, with Sentry full of noise and no clear reproduction.
Reproduced, traced and closed
A feature that passed QA on Chrome but fails on Safari or an older Firefox, usually over a quietly different API or date behaviour.
Verified across the browsers you care about
A lockfile that has not been refreshed in years, abandoned packages, and advisories that pile up every time somebody runs an audit.
Dependencies on supported versions
An over-eager bundler shipping the whole library when a small slice would do, with no code splitting and no measurement.
Lighter payload, measured
A new Content Security Policy that blocks the inline scripts and event attributes the old pages depended on.
Policy-clean code, policy enforced
A half-converted codebase with .js and .ts mixed, loose any types everywhere, and nobody certain where to draw the line.
Typed in stages that keep shipping
What we do
Call us for one broken script, 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, that is one of the more common calls we get. We start by getting the project to build on a current machine, map out what each part does, write down the bits only the previous person knew, and then plan changes from a stable base rather than guessing from the outside.
Usually in pieces. We leave the parts that work alone, replace one screen or feature at a time with current patterns, and keep the two styles side by side until the old ones are gone. That lets the business keep running while the code quietly improves.
Because some value you expected to be an object or array came back missing, usually from an API response, a race condition or a default that was never set. The fix is to reproduce the exact path, add the guard where the value enters, and tighten the shape so it cannot happen silently again.
Yes. We normally turn on the compiler in a permissive mode first so nothing breaks, convert the most-edited files to .ts, tighten the rules gradually, and keep pull requests small so the team can keep shipping features through the migration.
Most often a browser API or date behaviour differs between the engines, or a feature you rely on arrived later in one than the other. We reproduce the failure on the specific browser, isolate the cause, and either polyfill it or rewrite that path to use something all your target browsers support.
Estimates are free. Tell us what the project is 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: