Working with JavaScript?

JavaScript tangled or abandoned? We take it over.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

console.log

still failing

What it is

JavaScript at a glance

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.

Type
Dynamic programming language
First released
1995
License
ECMAScript specification is open
Maintained by
TC39 committee
Typically used for
Browser UIs, server APIs, build tooling, serverless functions, desktop and mobile apps via wrappers

The honest version

JavaScript pros and cons

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

Where JavaScript is strong

  • It runs everywhereEvery browser, every server, Node, Deno, Bun and Cloudflare Workers all speak it, so the same language can cover the whole stack end to end.
  • A huge ecosystemIf somebody has already written the thing you need, odds are it is published on npm and three others like it are too.
  • Backwards compatibility is excellentCode from a decade ago generally keeps working in today's engines, which is unusually kind for a web platform.
  • Modern JavaScript is pleasantES2020 and later cleaned up many of the rough edges, and TypeScript sits alongside it cleanly when static types are wanted.
  • Async is built inThe event-driven async model, with promises and await, fits the way web and network workloads actually behave.
  • Dev tools in every browserInspectors, profilers and debuggers ship with the runtime, so diagnosing an odd page rarely needs a special install.

Where JavaScript bites

  • One name, several worlds'JavaScript' covers browser code, server code under Node, Deno or Bun, and the tooling that bundles everything, and each of those worlds has its own traps.
  • Type coercion footgunsDouble-equals versus triple-equals, undefined against null, truthy strings and zeroes. The rules are learnable but they punish the unwary.
  • Tooling churnWebpack gave way to Vite and Turbopack, Babel ceded ground to swc and esbuild, and every two years the recommended setup moves again.
  • Deep dependency treesAn average project pulls in hundreds of indirect packages, which is convenient until a supply-chain incident forces a weekend audit.
  • Bundle size discipline is rareShipping two megabytes of script to render a form is routine, and the users on slow phones pay the bill.
  • Browser security keeps movingContent Security Policy, cookie rules and cross-origin behaviour change on a regular cadence, and old pages break quietly when they do.

Sound familiar?

Common JavaScript problems we fix

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

last commit: 2021 · author unknown

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

jQuery 1.11 · 48 plugins

A jQuery site that nobody wants to touch

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

Cannot read properties of undefined

Mystery errors in production

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

works in Chrome, blank in Safari

One browser is fine, the other is broken

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

npm audit: 42 high

The dependency tree has rotted

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

bundle: 3.4 MB gzipped

Pages are heavy and slow to load

An over-eager bundler shipping the whole library when a small slice would do, with no code splitting and no measurement.

Lighter payload, measured

CSP violation · inline handler

Tightened security broke the page

A new Content Security Policy that blocks the inline scripts and event attributes the old pages depended on.

Policy-clean code, policy enforced

tsc: 318 errors

The migration to TypeScript stalled

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

JavaScript help, from rescue to upkeep

Call us for one broken script, or hand us the whole front end.

Takeover
Picking up an abandoned codebase, getting it building again, and writing down how it works.
Modernisation
Moving old jQuery and legacy build setups onto something a current team can live with, without a full rewrite.
Debugging
Chasing the real cause of a production error, across browsers and devices, not guessing at it.
Performance
Bundle trimming, code splitting, loading strategy and real-user measurement.
Compatibility
Working out which browsers you really need to support and making the site behave in them.
Managed Tech
Ongoing upkeep, dependency hygiene and a team to call when something falls over.

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 JavaScript alongside something else?

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

Questions

JavaScript questions

Something else? Call+1 737 727 7327

Can you take over a JavaScript codebase whose last developer left?

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.

How do we modernise an old jQuery site without a rewrite?

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.

Why does our JavaScript throw 'Cannot read properties of undefined'?

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.

Can you help us migrate from JavaScript to TypeScript?

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.

Why do our scripts work in Chrome but fail in Safari?

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.

How much does JavaScript help cost?

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

JavaScript 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.