Course contentsShow
← TypeScript
Lesson 1593 of 1,79637. Migrating JavaScript to TypeScriptFree lesson

Choosing Your First Files

Identify leaf modules with few dependencies as starting points to minimize cascading type errors.

Choosing Your First Files

What you'll learn: How to identify the safest starting points when migrating from JavaScript to TypeScript by targeting leaf modules with minimal dependencies.

Why File Selection Matters

When you begin migrating a JavaScript codebase to TypeScript, the order in which you convert files dramatically affects your experience. Choose poorly, and you'll spend days fighting cascading type errors across dozens of files. Choose wisely, and each file converts smoothly with minimal friction.

Think of your codebase as a tree. Some files are like roots—deeply embedded with connections everywhere. Others are leaves—small, isolated, depending on others but rarely depended upon themselves. You want to start with the leaves.

The Leaf Module Strategy

Leaf modules are files that:

  • Import from other modules (they have dependencies)
  • Are rarely or never imported by other modules (few dependents)
  • Contain isolated logic: utilities, helpers, or standalone components

These are ideal first targets because when you add types to them, the errors stay contained within that file. You won't trigger a chain reaction of type errors rippling through 20 other modules.

Identifying Good Candidates

Look for files like:

  • Pure utility functions that transform data
  • Configuration objects that are only read
  • Standalone helper modules with clear inputs/outputs
  • UI components that don't export types to other components
  • Test files (yes, these count as leaf modules!)

Avoid starting with:

  • Core business logic that everything imports
  • Type definition files that spread types everywhere
  • Central configuration that exports interfaces
  • Shared base classes or heavily-inherited code

The Dependency Test

Before converting a file, ask: "How many other files import from this one?" If the answer is zero or one, it's a great candidate. If it's ten or more, save it for later in your migration.

Key Takeaway: Start your TypeScript migration with leaf modules—files with few or no dependents—to keep type errors isolated and your migration incremental and manageable.