
Migrating a Legacy JavaScript Codebase to TypeScript - JSJ 680
Failed to add items
Sorry, we are unable to add the item because your shopping cart is already at capacity.
Add to basket failed.
Please try again later
Add to Wish List failed.
Please try again later
Remove from Wish List failed.
Please try again later
Follow podcast failed
Unfollow podcast failed
-
Narrated by:
-
By:
About this listen
Dan walked us through how he started by setting up the project for success before converting even one file—getting CI/CD ready, setting up tsconfig.json, sorting out test dependencies, dealing with mock leaks, and even grappling with quirks between VS Code and WebStorm debugging.
We talked tools (like TS-ESLint, concurrently, and ts-node), why strict typing actually uncovered real bugs (and made the code better!), and why it’s crucial not to touch any .js files until your TypeScript setup is rock solid.
Key Takeaways:
- Gradual migration is 100% possible—and often better—than ripping the bandaid off.
- TypeScript can and will catch bugs hiding in your JavaScript. Be prepared!
- Use VS Code extensions or TS-Node to support your devs’ tooling preferences.
- Don't underestimate the setup phase—it’s the foundation of long-term success.
- Start small: Dan's team converted just one file at first to test the whole pipeline.
Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.
What listeners say about Migrating a Legacy JavaScript Codebase to TypeScript - JSJ 680
Average Customer RatingsReviews - Please select the tabs below to change the source of reviews.
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.