185 symbols are exported and used only inside their own file

[divshekhar]

A dead-export audit over packages/ found three distinct groups, and only the smallest is actually dead:

signal	count	what to do
exported, zero references anywhere	21	delete (tracked separately)
exported, referenced only by tests	40	mostly legitimate test seams; leave
exported, referenced only inside its own file	185	drop the export, keep the code

That last group is the one worth a sweep. Nothing outside the file uses them, so the export is noise that makes the module surface look larger than it is and defeats dead-code detection for everything else — a symbol exported for no reason can never be reported as unused.

What to do

Remove the export keyword where nothing outside the file references the symbol. Mechanical, wide, and the compiler proves each one: if pnpm typecheck passes, the removal was safe.

Worth doing package by package rather than as one enormous PR — packages/core and packages/server first, since they carry the most.

Care needed: a symbol referenced only by its own .test.ts is a test seam, not dead. Those stay exported. The audit counted them separately for exactly this reason.

[hardikguptaofficialgit]

Status check: fix is already on release/v2.12.0. Remains open until that ships via #564 (install-gate unblock: #581).

[divshekhar]

Claimed — #745 is open against this. Posting it here because three contributors duplicated each other's work today, and in every case the issue said nothing about the PR that already existed.

If you were about to pick this up: check that PR first, and if it has stalled, say so there rather than starting a second one. If you are its author and it has stalled, a comment saying what you are blocked on is enough to get a review.

[divshekhar]

Start here / Reproduce / Done when — added per #133.

Start here: pick ONE package and one directory inside it, not all 185 at once. packages/server/src/events/ or packages/browser/src/observers/ are good first slices. A reviewable PR here is 10-30 symbols in one area, not a repo-wide sweep.

Reproduce: for a candidate symbol, grep -rn "<name>" packages/ --include='*.ts' | grep -v '<its own file>'. No hits outside its own file means the export is noise.

Done when: pnpm typecheck passes with the export removed. That is the whole proof — the compiler cannot miss a real external reference. Then pnpm lint && pnpm test:unit.

Watch out for: a symbol referenced only by its own .test.ts is a legitimate test seam and is a DIFFERENT group in the table above (40 of them). Leave those alone. Also check the package's public barrel (index.ts) before removing — an export re-exported there is part of the shipped surface even if nothing in-repo calls it.