Practice monorepo migration vocabulary: moving from polyrepo to monorepo, using codemods, updating import paths, visualizing dependency graphs, and rollout strategies.
0 / 5 completed
1 / 5
'We're migrating from ___ to monorepo.' What is the opposite of monorepo?
'Polyrepo' is the standard industry term for the pattern where each project/service lives in its own repository. The polyrepo-to-monorepo migration is a common architectural shift.
2 / 5
'We used ___ to move packages.' Which word fits a code transformation tool?
A 'codemod' is an automated code transformation script. During monorepo migrations, codemods update import paths, configuration files, and package references across the entire codebase.
3 / 5
'The ___ paths needed updating after migration.' Which noun fits?
'Import paths' need updating when packages move from separate repos into a monorepo workspace structure — relative paths and package names often change.
4 / 5
'The dependency graph became ___ after migration.' Which adjective fits?
One major benefit of monorepo migration is that the dependency graph 'becomes visible' — tools like Nx and Turborepo can now visualize and analyze cross-package dependencies.
5 / 5
What is a 'migration rollout' strategy in a monorepo migration?
A migration rollout strategy phases the transition — often moving one team or service at a time to reduce risk and allow teams to adapt their workflows gradually.