You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a quick approach, I'd search for any module that lets you run a command on a file change and wire that up to run the madge command you're using.
Another approach is to add support for a new watch option in Madge that uses a file watcher (like the sane module) that invokes madge's entry point with the given arguments; you'd effectively end up rerunning madge on every file change.
The best but more involved solution is to layer on caching so that madge/dependency-tree only recompute parts of the tree that have changed. With the previous methods, the files that have changed are ignored and only used as a trigger to rerun madge. This would take some exploration but would be really cool.
Is there a way to use madge CLI in a watch mode to circular dependencies? Since that we are developing, have it running in a console it will be nice.
Thanks
The text was updated successfully, but these errors were encountered: