-
Notifications
You must be signed in to change notification settings - Fork 319
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
Release a madge version to solve "Not all imports in TypeScript are detected" #402
Comments
Please! Tracing this bug was a pain |
Yes! We've been fighting with this for months, finally figured out that it was already fixed in |
@pahen Are you still interested in maintaining this library? If not, would you be interested in passing it's stewardship along to another? |
@pahen Thank you! We all appreciate your contributions to open source very much! |
Thank you so much @pahen for the release and for all the effort in this library! |
We have been facing some problem to detect all the dependencies from our project, and we have seen that are related to skipped files in
madge
.There is an issue in this repository with the title "Not all imports in TypeScript are detected" marked as resolved, but the problem persists as there are some users reporting the same behaviour as we are facing:
#128
#128 (comment)
It seems that the culprit of the problem was an issue in
node-filing-cabinet
and as consequence also innode-dependency-tree
(10.*.*
) that was solved months ago.It looks like you are properly solved in
main
branch inmadge
but these changes have not been release in a proper NPM release, because the latest version6.1.0
uses the buggy version.We can use the workaround of using the git npm dependency, but it would be awesome to release a
madge
version to fix definitely this issue.The text was updated successfully, but these errors were encountered: