Repository navigation
feat: trace package entry paths for inventory consumers - #11
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.