Skip to content

fix: peer edge crash due to no parent or detached node #8448

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: latest
Choose a base branch
from

Conversation

milaninfy
Copy link
Contributor

@milaninfy milaninfy commented Jul 21, 2025

node.parent is resulting in null value somewhere in recursive/looped calls to #loadPeerSet method in building ideal tree.

When circular peer ref of a top level dependency replaced/resolved with different compatible version, it makes top level dependency to be removed from it's parent ( node.parent = null ) since it's been replaced, so no longer need to proceed with further peer set exploration.

fixes: #8261

@milaninfy milaninfy marked this pull request as ready for review July 31, 2025 17:40
@milaninfy milaninfy requested a review from a team as a code owner July 31, 2025 17:40
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.

[BUG] Cannot read properties of null (reading 'edgesOut') - on npm i
2 participants