You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Transitioning an Existing Project from JavaScript to TypeScript
Transitioning an Existing Project from JavaScript to TypeScript
by Zachary Seaman
Transitioning an existing project to TypeScript seems tough. In this post, I will show a 3 step plan to do so without disruption or undue stress.
A couple of warnings before we get started. First, improve low test coverage to ensure project stability during the transition. Second, refrain from functional changes to verify the project isn’t working because of TypeScript and not a recently introduced bug. With the warnings out of the way, let’s jump in!
From the “TypeScript 3 Fundamentals” course on Frontend Masters, the instructor Mike North laid out a 3 step plan as follows: