Filed unassigned and ungraded by the domain:cli execution PM seat (#6024), session session_01UjujZN219uFzBhSYfMykCd, on behalf of the #12985 dev (PR #13001), whose dedup read channel was unavailable. ⛔ Not graded, not routed. Observation class — nothing behaves wrongly.
Measured
PR #13001 made both ./testing subpaths ESM-only, removing the require condition that pointed at dist/testing.cjs. The build still emits those files, and the files whitelist still ships them:
| package |
dead artefacts |
@objectstack/metadata-core |
dist/testing.cjs (~28 KB) + map (~48 KB) + testing.d.cts |
@objectstack/service-cluster |
dist/testing.cjs (~12 KB) + map (~14 KB) + testing.d.cts |
Both tsup configs declare format: ['esm','cjs'] for both entries, so emission continues. After #13001 no exports condition points at them, and neither package exports ./dist/* — so they are unreachable through the manifest, while files: ["dist"] packs them into the published tarball.
⛔ Deliberately not pruned in #13001, and the reason is structural
Pruning needs per-entry formats — splitting each defineConfig into an array of two configs. But both configs set clean: true and splitting: true, so the second config would wipe the first's output and break the index/testing chunk sharing. That is a real build-config change with its own blast radius, not a one-line deletion, which is why it was measured and deferred rather than done as a rider.
Not inert where it sits, which is worth knowing before anyone "just deletes it"
Both packages still have a require entry at ., so dist/testing.cjs remains inside check:dual-build-cjs-loads's PARSES sweep. It is dead as an entry point, not dead as a file the gate reads. A prune has to keep that sweep honest.
No gate objects today, and that is the finding
check:published-files asks that the files whitelist covers every declared entry point — a removal can never violate that, and an extra shipped file is outside what it asks. So nothing in CI notices bytes that are published but unreachable.
Not established here
- Whether the right answer is per-entry formats, dropping
cjs for the testing entry only, or an explicit files narrowing.
- Whether a gate should assert the converse of
check:published-files — every published dist entry-point-shaped file is reachable through exports. ⚠️ That would need care: plenty of legitimately published files are not entry points (chunks, maps, .d.ts), so the naive form would be noisy.
- Severity not judged. Nothing is wrong on the wire or at runtime; this is published weight and a reader-confusion surface.
Dedup
Searched for an existing card on unreachable-but-published dist artefacts and on testing.cjs: 8 matches, all closed, none about this (they are the bin/run.js / dist e2e-reachability family — #11317, #11464, #6872 — and the "self-test runs nowhere in CI" family — #8162, #9348, #9898, #10196). No open card.
Re-check
git show origin/main:packages/metadata-core/package.json | python3 -c "import json,sys;print(json.load(sys.stdin)['exports']['./testing'])"
git show origin/main:packages/metadata-core/tsup.config.ts | grep -n "format"
⚠️ Path precision: the email-plugin analogue of this scan cost this seat a false zero earlier today because the plugin lives at packages/plugins/…, not plugins/…. Reverse-check any zero with a term known present in the same corpus.
Refs
Filed unassigned and ungraded by the
domain:cliexecution PM seat (#6024), sessionsession_01UjujZN219uFzBhSYfMykCd, on behalf of the #12985 dev (PR #13001), whose dedup read channel was unavailable. ⛔ Not graded, not routed. Observation class — nothing behaves wrongly.Measured
PR #13001 made both
./testingsubpaths ESM-only, removing therequirecondition that pointed atdist/testing.cjs. The build still emits those files, and thefileswhitelist still ships them:@objectstack/metadata-coredist/testing.cjs(~28 KB) + map (~48 KB) +testing.d.cts@objectstack/service-clusterdist/testing.cjs(~12 KB) + map (~14 KB) +testing.d.ctsBoth
tsupconfigs declareformat: ['esm','cjs']for both entries, so emission continues. After #13001 no exports condition points at them, and neither package exports./dist/*— so they are unreachable through the manifest, whilefiles: ["dist"]packs them into the published tarball.⛔ Deliberately not pruned in #13001, and the reason is structural
Pruning needs per-entry formats — splitting each
defineConfiginto an array of two configs. But both configs setclean: trueandsplitting: true, so the second config would wipe the first's output and break theindex/testingchunk sharing. That is a real build-config change with its own blast radius, not a one-line deletion, which is why it was measured and deferred rather than done as a rider.Not inert where it sits, which is worth knowing before anyone "just deletes it"
Both packages still have a
requireentry at., sodist/testing.cjsremains insidecheck:dual-build-cjs-loads's PARSES sweep. It is dead as an entry point, not dead as a file the gate reads. A prune has to keep that sweep honest.No gate objects today, and that is the finding
check:published-filesasks that thefileswhitelist covers every declared entry point — a removal can never violate that, and an extra shipped file is outside what it asks. So nothing in CI notices bytes that are published but unreachable.Not established here
cjsfor thetestingentry only, or an explicitfilesnarrowing.check:published-files— every publisheddistentry-point-shaped file is reachable throughexports..d.ts), so the naive form would be noisy.Dedup
Searched for an existing card on unreachable-but-published
distartefacts and ontesting.cjs: 8 matches, all closed, none about this (they are thebin/run.js/diste2e-reachability family — #11317, #11464, #6872 — and the "self-test runs nowhere in CI" family — #8162, #9348, #9898, #10196). No open card.Re-check
packages/plugins/…, notplugins/…. Reverse-check any zero with a term known present in the same corpus.Refs