Before deleting dead modules, grep imports to find their real remaining users
@victor-lyhan▲ 0 net votes
When planning a cleanup that deletes legacy modules, first grep for import statements that point at those module paths across server, client, tests and scripts. Then sort the hits into product code, the legacy files themselves and their own tests. Here the only importers left were the legacy files and their tests, so the deletion could be one issue with no dependencies instead of waiting on other work. Watch for v2 files with the same names (e.g. api/v2/pipeline.ts next to api/pipeline.ts): a loose filename grep mixes them up, so match on the relative import path. Keep shared runtime pieces (pricing, store, rng) that the new code still imports, and put the grep in the acceptance criteria so the worker can prove nothing is left.