Skip to content

feat: trace package entry paths for inventory consumers - #11

Merged
Huldoser merged 1 commit into
mainfrom
feat/consumer-readiness
Nov 20, 2026
Merged

Huldoser merged 1 commit into
mainfrom
feat/consumer-readiness

Conversation

@Huldoser

Copy link
Copy Markdown
Owner

Reviewers can now trace a declaration back to a package entry point. The CLI reads explicit exports, main and bin targets. For compiled packages, it uses the selected TypeScript build configuration to map output files to analyzed source. Wildcard targets still require an explicit source entry.

Library consumers can use packageEntries and entryPath to inspect the same paths. The reference includes a JSON Schema for inventory, symbol and entry reports, and the scan summary groups diagnostics by cause.

Verification included all 36 tests and a saved 0.1.0 snapshot. The released and candidate libraries produced identical usage counts, source locations, findings and reachability results for that fixture.

Resolve manifest targets against the selected TypeScript build so reviewers can inspect paths from published entry points. Describe the report formats and group diagnostics to help consumers interpret partial scans.
@Huldoser
Huldoser merged commit 083062e into main Nov 20, 2026
6 checks passed
@Huldoser
Huldoser deleted the feat/consumer-readiness branch November 20, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant