Consider the benefits of type safety and improved tooling against the costs of a learning curve and build overhead before migrating a project.
Use editor settings like `checkJs` or a `// @ts-check` comment to get immediate type feedback on your JavaScript code without any build changes.
Add TypeScript as a dependency and configure `tsconfig.json` with non-strict settings like `allowJs` to compile existing JavaScript without errors.
Activate `checkJs` in your `tsconfig.json` to enforce type safety during the build and install necessary `@types` packages for dependencies.
Add types to your JavaScript project using JS Doc comments, allowing TypeScript to provide strong typing without converting files to `.ts`.
Gradually rename `.js` files to `.ts` one at a time, updating syntax from CommonJS to ES Modules and adding explicit types as you go.
Review the complete migration path, from enabling editor checks and introducing the compiler to incrementally converting files and adding types.
Demonstrate the value of TypeScript by enabling `checkJs` on an existing project to reveal hidden type-related issues as a practical proof point.
43:27Simone Sanfratello
48:56Tal Joffe
31:13Stefan Baumgartner
37:18Tal Joffe
29:44Jens Claes
44:31Rob Richardson
28:44Lars Hupel
29:30Peter Kröner
Jobs that call for the skills explored in this talk.
doinstruct Software GmbH
Berlin, Germany
Speech Processing Solutions
Vienna, Austria
Schulz.codes GmbH
Darmstadt, Germany
autoiXpert GmbH & Co. KG
Stuttgart, Germany
GEBIT Solutions GmbH
Mindpeak