Repository navigation
fix: discover nested dependency manifests - #250
Merged
theyashasvipandey merged 3 commits intoOct 11, 2026
Merged
theyashasvipandey merged 3 commits into
theyashasvipandey merged 3 commits into
Conversation
Collaborator
|
@MEETNANDA8107 Thanks for the PR and for contributing to MEX! We also have a Discord community ,feel free to join if you’d like. :) |
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
2 participants
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.
Summary
package.jsonmanifests at arbitrary nesting depth.pyproject.tomlmanifests at arbitrary nesting depth.node_modulesand.gitdirectories during manifest discovery.Testing
npx vitest run test/checkers.test.ts— 109/109 passednpm run typecheck— passedgit diff --check— cleanThe full test suite was also run; it reported unrelated failures in other subsystems, while the dependency checker suite remained fully passing.