Services

Three things teams hire me for. Each one links to work you can read before deciding.

01

Vue and Nuxt migrations

Your app is on Vue 2, Nuxt 2, or a Nuxt 3 version you have stopped upgrading, and the longer it sits the more it costs.

I audit what you have, write the migration path with milestones, and run it incrementally so the app keeps shipping while it moves. No big-bang rewrite.

I have done this on an open-source codebase with a large installed base, and written up a Nuxt 3 to Nuxt 4 migration of a production app in detail.

What you get

  • A written audit of the current codebase and its risk areas
  • A staged migration plan with milestones you can schedule around
  • The migration itself, shipped incrementally
  • Handover notes your team can work from afterwards

Evidence

02

Features and bug fixing in existing apps

You have a working Vue, React or Angular app — possibly with jQuery still in it — and you need someone who can work in it without a three-month ramp-up.

I read the codebase before changing it, find the cause rather than the symptom, and leave the fix documented. Most of my work has been in codebases I did not write.

This includes the awkward ones: intermittent bugs that only appear under real usage, and legacy code nobody wants to open.

What you get

  • Features built to match the conventions already in your codebase
  • Root-cause fixes, with the reasoning written down
  • Code review and notes for the team that maintains it next

Evidence

  • Open-source Nuxt 2 → 3 migration
03

Auth integration

You need Microsoft Entra ID (Azure AD), MSAL or OAuth working properly in a Vue or Nuxt app, including the parts the official docs skip.

Token refresh, route guards and SSR are where these integrations usually break. I have a public Nuxt 3 starter covering exactly that, which other people have picked up and used.

What you get

  • A working sign-in flow wired into your existing routing
  • Token refresh and route guards that behave on reload and in SSR
  • A written explanation of how the flow works, so it is maintainable

Evidence

How I work

Where I am

Gujarat, India, IST (UTC+5:30).

Estimates

I read the codebase first, then send scope and milestones in writing. If I am not the right person for the job, I will say so on the first call.

While the work runs

Work lands in small reviewable pieces rather than one large drop at the end, so you can change direction without losing a month.

When it ends

Handover notes covering how things work and where the awkward parts are. Written for whoever maintains it next.

Working on something that needs a frontend engineer?

Tell me what you are building and what is in the way. If I am not the right person for it, I will say so.

Get in touch What I do