
Migrating a Legacy JavaScript Codebase to TypeScript - JSJ 680
No se pudo agregar al carrito
Solo puedes tener X títulos en el carrito para realizar el pago.
Add to Cart failed.
Por favor prueba de nuevo más tarde
Error al Agregar a Lista de Deseos.
Por favor prueba de nuevo más tarde
Error al eliminar de la lista de deseos.
Por favor prueba de nuevo más tarde
Error al añadir a tu biblioteca
Por favor intenta de nuevo
Error al seguir el podcast
Intenta nuevamente
Error al dejar de seguir el podcast
Intenta nuevamente
-
Narrado por:
-
De:
Acerca de esta escucha
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.
Todavía no hay opiniones