single-file-edit

To safely refactor TypeScript code across multiple files, apply a staged edit process that updates files one at a time in a dependency-aware order and runs npx tsc --noEmit between edits to catch cross-file issues early.

The best way to implement a feature changing types and callers is to list affected files, propose a dependency-aware update sequence like types then producers then consumers, and edit files sequentially with type-checking between each step.

To prevent broken downstream code when modifying shared modules, establish a planned edit order targeting dependencies first and verify type integrity by running npx tsc --noEmit after each individual file modification before proceeding to the next.

Staged multi-file editing does not require a TypeScript compiler to apply text changes, but running npx tsc --noEmit between file edits is necessary to achieve continuous type verification and catch cross-file integration issues early.

You should avoid restarting backend scripts during multi-file code editing because the workflow requires pausing to verify type correctness between file updates, and restarting scripts mid-sequence disrupts the controlled, staged verification process.