Is this for you?
- You have a JS codebase that keeps shipping bugs TypeScript would catch.
- You've tried `// @ts-check` in a few files but never committed fully.
- Tooling choice paralysis — tsc vs. swc vs. esbuild vs. Vite-only.
- A previous migration attempt stalled after 20% coverage.
What you get
- Codebase assessment with module complexity scoring.
- Phased migration plan (config → leaf modules → shared libraries → API layer).
- `tsconfig` recommendations with strictness ramp by phase.
- Tooling setup (build, lint, editor, CI).
- Effort estimates per phase.
Scope
What's in
- TypeScript adoption strategy
- Phasing and sequencing
- Tooling and CI setup recommendations
- tsconfig strictness ramp
What's out
- Performing the migration
- Framework migrations (see Vue and React migration services)
- Type definitions for large third-party libraries without DefinitelyTyped coverage
Process
Intake
Day 1Kickoff, repo access, tooling inventory.
Discovery
Days 2–4Codebase read, module dependency graph, risk areas.
Analysis
Days 5–7Phase design, tsconfig strategy, effort estimation.
Report
Days 8–10Draft, review, finalize, 60-minute walkthrough.
Pricing
50% to start, 50% on report delivery. Includes one 30-minute follow-up call within 30 days of delivery.
One fixed price. No surprises, no “starting at” language. If we agree on scope and you pay the deposit, the engagement is locked in.
Questions
We have a Vue codebase. Does that change anything?
Yes — Vue-specific tooling (volar, vue-tsc) is part of the plan.
React?
Same answer, tailored to your bundler and component library.
Can you do the migration?
Separately, yes.
Will you sign an NDA?
Yes.
About
26+ years of full-stack experience across PHP, JavaScript, and Python. I ship production systems for teams that need senior technical work they can trust, from the founding engineer's perspective.
More about the studioReady to start?
Book an intro call. If we're not a fit, I'll tell you on the call.