-
-
Notifications
You must be signed in to change notification settings - Fork 63
Description
Clear and concise description of the problem
When optimizing the production build and determining why some modules appear in specific chunks, I would appreciate the ability to identify the import path. This feature would enable me to break, change, or refactor the codebase to enhance the output. Currently, I have to click through the import path manually to identify issues. In the Graph module, I would select one module as the starting point and another as the endpoint, which would display the entire import path between them. This would effectively solve many problems related to backtracking incorrect imports. When working on huge applications 10k+ modules, this would drastically improve UX.
Suggested solution
In Graph module, we would select starting and ending module. This would provide us with all possible import paths. We would have similar view as Graph, but only with the selected modules, instead of whole Graph that is hard to navigate with huge codebases.
Alternative
No response
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.