Looking after a custom web app once it's live
When people think about website maintenance, they usually think of WordPress: plugin updates, backups, the odd security patch. A custom web app built with React, Next.js or Node.js is different in a lot of ways, but it has the same basic need. The code you launched with sits on top of other software, and that software keeps moving.
The good news is that a small, well-built app doesn't need much. A short check every few months is usually enough. Here's what I'd put on that list.
1. Know which Node.js version it runs on
Most JavaScript web apps run on Node.js on the server, or at least use it to build the site. Each Node.js major version is supported for a fixed time, and the official release schedule publishes the dates in advance.
As of today, the schedule lists:
- Node.js 20: reached end of life on 30 April 2026, so it no longer gets security fixes.
- Node.js 22: in maintenance, with support ending on 30 April 2027.
- Node.js 24: in maintenance, with support ending on 30 April 2028.
- Node.js 26: the current Active LTS version, supported until 30 April 2029.
The Node.js project's releases page is clear that production apps should only use Active LTS or Maintenance LTS releases. If your app is on Node.js 20 or older, it's worth planning a move. If it's on 22, you have until April, which is a comfortable amount of time if you start in the new year rather than in March.
Where to look depends on how the app is hosted. Your hosting dashboard often shows the runtime version, and the project usually records it in a file like .nvmrc or in the engines field of package.json. If you're not sure, whoever built the app should be able to tell you in a minute.
2. Update dependencies in small steps
A typical React or Node.js project depends on dozens of open-source packages, and those packages depend on others. Updates arrive constantly, and most are small.
The mistake I see most often is leaving them for years and then trying to update everything at once. That turns a routine job into a rebuild. A steadier approach:
- Apply security fixes promptly. Running
npm audit(or the equivalent for your package manager) lists known vulnerabilities in the packages you use. - Take minor updates every few months. Update, run the app's tests, click through the main screens, deploy.
- Plan major upgrades on purpose. A new major version of React, Next.js or a database library can change how things work. Give it its own small piece of work instead of mixing it in with other changes.
3. Keep the boring safety net working
These don't change often, but they're easy to forget:
- Backups of the database, and an occasional test that one actually restores.
- Error logging or monitoring, so you hear about a broken screen from a log rather than a customer.
- Domain and certificate renewals, plus any third-party API keys or accounts the app relies on.
- Access. Make sure you, not just your developer, can get into the hosting, the code repository and the domain.
4. Desktop apps have the same problem
Electron desktop apps for macOS and Windows bundle their own copy of Chromium and Node.js, so they need the same kind of updates. The Electron project only supports its most recent stable major versions, which are listed on its release timeline. An app that hasn't been rebuilt in a long time is running an old browser engine on every machine it's installed on.
How much time this takes
For a small internal tool or customer portal, this is usually a few hours a few times a year, plus a bigger piece of work when a Node.js or framework version is retiring. It's much cheaper than the alternative, which is finding out an app can't be updated at all when something forces the issue.
Where I fit in
I build and look after custom web and desktop apps for small NZ businesses, using React, Next.js, Node.js and Electron. If you have an app that's been running quietly for a while and you're not sure what version it's on or when it was last updated, send me a short note and I'll take a look.