Node.js API Migration and Upgrade
Bring an old Node.js app up to a current LTS release, replace dead packages and move it to TypeScript if you want.
Shahid Malla · Top Rated on Fiverr and Upwork
600+ Fiverr reviews, 4.9 average · 13+ years · 900+ projects
Node.js LTSTypeScriptDependency upgrades
About this package
This package brings an aging Node.js API, stuck on Node 14 or 16 with npm audit warnings and abandoned packages, up to a current LTS release, and on Premium moves it to TypeScript or from Express to NestJS. The goal is the same behavior on supported foundations, so your hosting, security scans and next features stop fighting the old stack.
Pin behavior, then change
Starter adds smoke tests on the main routes. Business goes further and writes tests around the routes that matter before touching any code, recording what each one returns today, so after the upgrade a failing test points straight at a changed response. Deprecated libraries such as request are swapped for maintained ones, callback code becomes async and await, and npm audit findings are fixed or explained.
- ES modules are adopted where they simplify things, not everywhere for the sake of it.
- Each step is its own commit, so you can review it and roll it back on its own.
- Business and Premium deploy to staging so you can check real screens against the upgraded API.
TypeScript and NestJS on Premium
Moving to TypeScript happens file by file, starting with the data models, so the type checker starts catching mistakes early without a big-bang rewrite. For a larger codebase you can choose a move from Express to NestJS, which gives modules and dependency injection a team can grow into. The database driver or ORM is upgraded too, a CI pipeline runs the tests on every push, and the production rollout comes with a rollback plan.
Done when
The API runs on the current LTS release, the tests pass in CI or locally, the upgrade notes list every package swapped and why, and your frontend works against staging without changes. Performance tuning and new endpoints are separate work.
Compare packages
| Package | Starter$399 | Business$1,099 | Premium$2,299 |
|---|---|---|---|
| Current Node.js LTS | |||
| Dependency audit and updates | |||
| Tests before any change | Smoke tests | Main routes | Main routes |
| Async and await conversion | – | ||
| Staging deploy | – | ||
| TypeScript migration | – | – | |
| Express to NestJS | – | – | Optional |
| CI pipeline | – | – | |
| Production rollout with rollback | – | – | |
| Delivery time | 7 days | 14 days | 28 days |
| Revisions | 2 | 3 | 5 |
What I need from you
After you pay, a project opens for your order. Send these there and the delivery clock starts.
- Repository access and the branch running in production
- Your current Node.js version and how the app is started
- An .env example with secrets removed
- A database copy with personal data removed, or a staging database
- The routes or jobs that matter most to your business
About the developer
Shahid Malla
AI agent and AI chat developer, full-stack developer
Top Rated on Fiverr and Upwork
- Based in
- Kashmir, India
- Experience
- 13+ years
- Projects
- 900+ delivered
- Languages
- English, Hindi
I have built websites, WHMCS modules and web apps for clients since before AI coding tools existed. Today I build with AI-assisted tools and review every change myself, which is why fixed prices here are lower than an agency's for the same scope. I work while the US, Canada and Australia sleep, so each morning there is progress on your staging link.
Read my 600+ Fiverr reviews · Upwork profile · Portfolio · About me
Questions about this package
Should I move to TypeScript now or later?
If the codebase will keep growing or change hands, now is cheaper than later, because the tests written during the upgrade make the move safer. For a small, stable API that rarely changes, staying on JavaScript with current packages is a reasonable choice, and Business covers that well.
Will my API's responses change?
They should not. The tests recorded before the upgrade compare responses afterwards, so any difference shows up as a failing test that I fix or explain to you. Where a response must change, for example a security fix to an error message, it is listed in the upgrade notes.
Can you move the app to Bun or Deno instead?
Possibly, but I recommend Node.js LTS for most production APIs because of its long support windows and package compatibility. If you have a specific reason to switch runtimes, I check your dependencies against it first and quote the move separately.
How ordering a package works
-
1
Choose a plan
Pick Starter, Business or Premium and pay once by card, PayPal or crypto. The price on the page is the price.
-
2
Send your content
A project opens for your order. Send your text, logo, photos and any logins I need there.
-
3
I build it
I build on a private staging link you can open on your phone, with updates as I go.
-
4
Launch and handover
After your approval the site goes live on your domain, and every login is yours.
One-time price, no monthly fee from me
You pay for the build once. Your domain and hosting are registered in your name and renewed with your hosting provider, who bills you directly. I add nothing on top, and the site keeps running whether or not you hire me again.
What I do not build
Gambling and adult websites, and sites that sell content without the rights to it. Need something not listed? Ask for a custom quote.
More node.js apps and apis
- Node.js REST APIA documented REST API in Express or NestJS with auth, validation and a database behind it.Starting at $399 · 7 days
- Real-Time Chat App with Socket.IOLive one-to-one and group chat with typing indicators, read receipts and stored message history.Starting at $449 · 8 days
- Node.js Backend for a Mobile AppThe API, sign-in, push notifications and admin panel behind a Flutter, React Native or native mobile app.Starting at $449 · 9 days