Team Coordination During Migration
You'll learn how to establish team conventions, communication practices, and safeguards that prevent migration drift when gradually moving from JavaScript to TypeScript.
Why Coordination Matters
When migrating a codebase to TypeScript, you're not just converting files—you're establishing a new contract between team members. Without clear conventions and guardrails, your migration can become chaotic: some developers add new .js files, others use any everywhere, and nobody's sure what "migrated" actually means.
Think of it like renovating a house while people still live in it. You need clear zones: "This room is done—don't use old materials here," "This is the construction zone," and "These tools are banned going forward."
Establish Conventions for New Code
The most critical decision: all new code must be TypeScript. This prevents the codebase from growing in the wrong direction while you migrate.
Document clear rules:
- All new files must use
.tsor.tsxextensions - Define what "properly typed" means (no
anywithout comment justification, for example) - Agree on strictness expectations (even if existing files don't meet them)
- Establish naming conventions for type files (
types.ts,*.types.ts, etc.)
Create a team style guide that answers: "When I write new code tomorrow, what TypeScript practices should I follow?"
Communication Channels Matter
Set up explicit communication paths:
- Dedicated Slack/Teams channel for migration questions
- Weekly sync or standup item to share progress
- Migration wiki or doc tracking which modules are done
- Code review guidelines specific to TypeScript (not just general review)
The goal: nobody should be blocked wondering "Is this typed yet?" or "Can I depend on types from that module?"
Preventing .js Files from Being Added
Use automation to enforce your "no new JavaScript" rule:
ESLint configuration to warn about .js in certain directories:
// .eslintrc.json
{
"overrides": [
{
"files": ["src/**/*.js"],
"rules": {
"no-restricted-syntax": [
"error",
{
"message": "New .js files are not allowed. Use .ts instead."
}
]
}
}
]
}
Pre-commit hooks that reject new .js files in migrated directories.
CI checks that fail if the count of .js files increases from the baseline.
The key is making the wrong thing hard to do accidentally.
Tracking Progress Visibly
Make migration status transparent:
- Maintain a checklist of modules/directories
- Use GitHub Projects or similar to track file conversion
- Add badges to your README showing percentage complete
- Celebrate milestones publicly
When everyone can see progress, momentum builds and stragglers become obvious.
Key Takeaway: Successful team migration requires explicit conventions for new code, clear communication channels for questions and status, and automated guardrails that prevent .js files from sneaking back into your codebase—coordination transforms migration from chaos into systematic progress.