fix: properly handle cyclic nodes with getParentClientNodes #14522
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.
getParentClientNodesrecursively goes through and figures out the module graph, but there is no protection against import cycles in the traversal, which leads to max Callstack errors everytime a file within the cycle is changedimport cycles are obvisouly not a good thing, I have tried to figure out the cyclic import but has been unable to find it. I have tried https://github.com/sverweij/dependency-cruiser but it was unable to find anything. so I did some debuging and found that the cycle involves
virtual:cloudflare/worker-entry, which makes it way harder to detect as its a virtual module. so I am still unable to figure out the issue.Which is why I just fixed the function to keep track of seen modules, this also removes the need of extra
uniqueModulefunction which make this slightly better