MoveSafe

Safer Structural Changes for TypeScript

Moving a file in a TypeScript codebase sounds simple until the change crosses package boundaries, path aliases, barrel exports, tests, or generated code. A move that succeeds in the editor can still leave broken imports elsewhere in the repository.

MoveSafe is currently in development. Its goal is to make structural TypeScript refactoring explicit, inspectable, and verifiable—especially when the change is initiated by a coding agent or automated workflow.

The Problem

Developers and coding agents can edit files quickly, but speed is not the same as safety. Repository-wide moves need to account for:

• Imports and exports that reference the moved module
• TypeScript path aliases and package boundaries
• Re-exports through barrel files
• Tests, configuration, and generated references
• Verification through type-checking and CI

When those relationships are missed, a mechanical refactor becomes a debugging session.

The Direction

MoveSafe is being designed around a few durable principles:

• Preview before mutation — show the intended file and import changes first.
• Deterministic edits — the same input should produce the same result.
• Repository-aware validation — verify changes against the actual TypeScript project.
• Agent-safe operation — expose clear boundaries and machine-readable outcomes for coding agents.
• Recoverability — make partial or failed changes easy to understand and reverse.

Follow the Build

I will publish the architecture, trade-offs, experiments, and real-world refactoring examples as MoveSafe develops. The first articles will cover why TypeScript file moves fail, how repository-wide references can be resolved, and what makes an automated refactor safe enough for CI and coding agents.

Until the first public release is ready, follow the writing section for development notes and technical deep dives.