Working with Node.js?

Node.js app past its sell-by date? We bring it current.

Most Node.js apps that reach us were built on a version that is no longer supported, with a dependency tree nobody has touched in years. We get the runtime current and the packages clean, without rewriting the parts that are still doing their job.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

server.log

still failing

What it is

Node.js at a glance

Node.js is a JavaScript runtime for the server, built around the V8 engine from Chrome and the libuv event loop. It was first released in 2009 by Ryan Dahl and is now maintained by the OpenJS Foundation. It lets the same language run on the browser and the server, which is why it ended up behind so much of the modern web.

It is used for HTTP APIs, server-rendered frontends with frameworks such as Next.js, realtime services, build tooling, serverless functions and desktop apps through Electron. Major LTS versions come out on an eighteen-month cycle, and the current long-term release at the time of writing is version 22.

Type
JavaScript and TypeScript runtime
First released
2009
License
MIT
Maintained by
OpenJS Foundation
Typically used for
APIs, server-rendered frontends, realtime servers, build tooling, serverless functions, command-line tools

The honest version

Node.js pros and cons

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

Where Node.js is strong

  • One language, both sidesJavaScript or TypeScript runs on the browser and the server, so a small team can own the whole stack without context switching.
  • The npm ecosystem is hugeFor almost any protocol, format or integration there is a well-worn library already published, which saves weeks of boilerplate on most projects.
  • Async by defaultThe event loop handles many concurrent requests on modest hardware, which makes it a natural fit for JSON APIs and streaming workloads.
  • Cloud providers love itVercel, AWS Lambda, Cloud Run and the rest treat Node as a first-class runtime, with fast cold starts and official base images for every current version.
  • Modern JavaScript is finally standardES modules, top-level await and the built-in fetch client are no longer experimental, which closes a long-running gap with browser code.

Where Node.js bites

  • Support windows are shortEach major LTS gets roughly thirty months before it stops receiving security fixes. Miss one cycle and your production runtime is already out of support.
  • ESM and CommonJS still fightMixing require and import across a mature codebase produces ERR_REQUIRE_ESM errors that can take real effort to untangle, especially with transitive dependencies.
  • Dependency rot is realPostinstall scripts, abandoned maintainers and the occasional supply-chain incident mean a package tree that was fine two years ago is now a liability nobody wants to open.
  • The heap has a ceilingThe default limit is around 1.5 GB, so a process can be killed by the OOM reaper long before the host is actually full, often without a clear stack trace.
  • Versions fight deploysThe engines field in package.json, the Node version on the build server and the one on the host rarely agree after an upgrade, and npm ci will refuse to proceed until they do.
  • Lockfile noisepackage-lock.json churn on every install clutters diffs and hides the one line that actually matters.

Sound familiar?

Common Node.js problems we fix

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

Node 16 reached end of life September 2023

The runtime is past end of life

An old Node version that stopped getting security patches, held in place because an upgrade broke something last time it was tried.

Upgraded to a supported LTS

JavaScript heap out of memory

The process keeps running out of memory

A leak in a long-lived server, a cache without a bound, or simply the default 1.5 GB heap meeting a workload that outgrew it.

Stable memory, measured

Error [ERR_REQUIRE_ESM]

ESM vs CommonJS breaks after an upgrade

A dependency went pure ESM and now a require() call throws at startup, with a stack that points nowhere helpful.

Modules sorted, build green

42 high severity vulnerabilities

npm audit is a wall of red

Years of unpatched dependencies, some genuinely exploitable and some noise. Nobody has time to tell which is which.

Only the real ones left, triaged

deployed by someone who left

Inherited from a developer who moved on

No README, no .env template, a Dockerfile that only built on their laptop, and a hosting account in their name.

Buildable from a fresh checkout

listen EADDRINUSE :::3000

It crashes under load

Zombie processes, unhandled promise rejections, or a cluster setup that was never finished.

Stays up through the peak

What we do

Node.js help, from upgrade to upkeep

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

LTS upgrades
Moving Node 14, 16 or 18 apps onto a current LTS, with dependencies and the Dockerfile brought along.
Memory and performance
Heap profiling, leak hunting and sensible tuning, with before-and-after numbers you can show.
Dependency clean-up
Pruning dead packages, replacing abandoned ones and getting the audit list down to things that actually matter.
Takeovers
Picking up a codebase from a previous developer or agency, documenting it, and making it buildable on any machine.
Deploys and infrastructure
CI, containers and hosting on Vercel, Lambda, Cloud Run or a plain server, whichever fits the app.
Managed Tech
Patching, 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 Node.js alongside something else?

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

Questions

Node.js questions

Something else? Call+1 737 727 7327

Can you upgrade our Node app from Node 14 or 16 to a current LTS?

Yes. We rehearse the upgrade on a branch, work through the breaking changes in the standard library and in your dependencies, fix the ESM and CommonJS fallout, and only merge once the test suite and a staging deploy are both green.

Why does our Node.js server run out of memory?

Usually one of three things: a slow leak in a long-lived cache or event emitter, a workload that has outgrown the default 1.5 GB heap, or a dependency holding onto references it should have released. We take a heap snapshot, find the source, and either fix the code or raise the limit with a reason for doing so.

Can you take over a Node.js codebase from a previous developer?

Yes, and we do this often. We get it building from a clean checkout, write down the parts that live only in someone's head, move hosting and domains into your name, and leave you with something a new developer could pick up in an afternoon.

How do we fix 'ERR_REQUIRE_ESM' after an upgrade?

It means a package you depend on has gone ESM-only while your code still uses require. The fix is either to move the calling file to import syntax, pin to the last CommonJS release of that package while you plan the migration, or use a dynamic import. Which one is right depends on where it sits in the tree.

What should we do about hundreds of npm audit warnings?

Most of them are noise from devDependencies that never run in production. We triage the list, upgrade or replace the handful that are genuinely exploitable, suppress the rest with a note explaining why, and set up a review on a schedule rather than a panic every quarter.

How much does Node.js help cost?

Estimates are free. Tell us what the app does and what's going wrong, and you get a price before any work starts.

Free estimate

Node.js 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.