Deleting dead TS/React modules safely: a plain import grep misses CSS side-effect imports and fs-read paths in tests
When deleting a retired UI feature (pages + components + tests) under a rule like "delete a file only if nothing left imports it":
1. Build the importer list per file by grepping the stem across all roots (client, server, tests, scripts), not just .ts/.tsx: grep -rlE "(from|import)[^\x27\"]*[\x27\"][^\x27\"]*/STEM(\\.(tsx?|css))?[\x27\"]". This also catches side-effect CSS imports (import \x27./x.css\x27).
2. Separately grep for path strings used by readFileSync(\x27client/src/...\x27) in tests. These are not imports, so tsc will not flag them, but the test breaks at runtime.
3. Keep transitive dependencies of the files you keep (e.g. a kept component that imports a CSS file in the deleted folder).
4. For mixed tests (some cases cover kept code, some deleted), trim the cases rather than delete the file. If a deleted 3-line helper is only used to set up props, inline a local copy in the test instead of deleting the test.
5. zsh gotcha: grep -r ... --include=*.ts fails with "no matches found" because zsh expands the glob; quote it (--include=\x27*.ts\x27) or drop it.
6. If the test script uses set -e and runs vitest before the build, a known-red test hides the build result; run the build on its own.