
Migrating a Legacy JavaScript Codebase to TypeScript - JSJ 680
Falha ao colocar no Carrinho.
Tente novamente mais tarde
Falha ao adicionar à Lista de Desejos.
Tente novamente mais tarde
Falha ao remover da Lista de Desejos
Tente novamente mais tarde
Falha ao adicionar à Biblioteca
Tente outra vez
Falha ao seguir podcast
Tente outra vez
Falha ao parar de seguir podcast
Tente outra vez
-
Narrado por:
-
De:
Sobre este áudio
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.
O que os ouvintes dizem sobre Migrating a Legacy JavaScript Codebase to TypeScript - JSJ 680
Nota média dos ouvintes. Apenas ouvintes que tiverem escutado o título podem escrever avaliações.Avaliações - Selecione as abas abaixo para mudar a fonte das avaliações.
Nenhuma revisão disponível