Service / 02
Vue 3.
Nuxt 3.
Production-ready.
Senior Vue freelance support. Apps your team can actually maintain after I hand them back. Composition API, Pinia, Vitest, Storybook.
Service / 02 / Capabilities
What's covered.
Vue 3 SPAs
Composition API, TypeScript, Pinia, Vite tooling. Components that scale without turning into spaghetti.
Nuxt 3 SSR
Server-rendered pages, Nitro APIs, Nuxt Content sites. Better SEO and faster first loads where it matters.
Component libraries
Storybook-driven, accessible, tested. Reusable building blocks across products and brand families.
10+ years senior delivery
Why me
Senior delivery you don't have to project-manage.
I have been writing Vue since the 2.x days and Nuxt since 1.x. Most engagements I land into involve inheriting code, so I prioritise leaving a codebase your team can maintain, not just shipping the feature.
- Vue 3 + Composition API + Pinia + Vitest as the default stack
- Nuxt 3 with Nitro for SEO-heavy public sites
- Storybook for component review and visual regression
- Comfortable handing back to your team. Code stays maintainable
Engagement / Snapshot
A typical vue & nuxt development engagement.
Lead time
<7
Days to start, contract permitting
Length
4-12
Weeks for fixed-scope work
Reply
<24
Hours, every working day
Day rate
POA
Quoted per engagement
FAQ / Vue & Nuxt Development
Frequently asked
Q · 01
Vue 2 or Vue 3?
Vue 3 with Composition API as default. Happy to pick up Vue 2 / Options API codebases for migrations and ongoing maintenance.
Q · 02
SSR or SPA?
Both. Nuxt 3 with Nitro for SEO-heavy public sites, SPAs for internal dashboards. The right choice depends on the audience and content shape.
Q · 03
How do you handle state?
Pinia by default. For small apps the Composition API + provide/inject is fine. I avoid Vuex for new builds.
Q · 04
Tests?
Vitest for unit + component, Playwright for end-to-end where it earns it, Storybook for visual review and accessibility checks.
How I work
Remote-first. Async by default.
Inspired by Remote and the way Basecamp ran a distributed team without burning anyone out. Meetings are expensive, writing is cheap, and momentum belongs to whoever can make a decision without a calendar invite.
01 / Specs
Specs before code
A short written spec covering problem, scope, and acceptance before anything gets built. Cuts rework, makes review easier, and means we never argue about what was agreed.
02 / Workstreams
Workstreams over standups
Active work lives in tickets and PRs with running notes. Async updates instead of daily standups, so deep work is the default and meetings only happen when they earn it.
03 / Loom > Zoom
Loom over meetings
Most reviews and walkthroughs go out as a 5-minute Loom you can watch at 2× when convenient. We jump on Meet / Zoom / Teams when the topic actually needs a conversation.
Channels / Tools
Slack
Async, threaded, no expectation of instant reply
Loom
PR walkthroughs, demos, design reviews
Google Meet / Zoom / Teams
Booked when conversation > writing
Linear / Jira / GitHub
Source of truth for the work
Notion / Docs
Specs, decision records, retros
The pitch
I write the code, talk to your team, and ship what we agreed. No agencies. No PMs. No surprises.
James Donnelly
Freelance developer · Manchester