-
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
tsconfig for resolving aliased modules #167
Comments
I read madge's source code and opened issue for dependent module |
mrjoelkemp
added a commit
to dependents/node-filing-cabinet
that referenced
this issue
Nov 19, 2018
Refs pahen/madge#184 Refs pahen/madge#167 Refs pahen/madge#179 Refs #63
mrjoelkemp
added a commit
to dependents/node-filing-cabinet
that referenced
this issue
Nov 19, 2018
Refs pahen/madge#184 Refs pahen/madge#167 Refs pahen/madge#179 Refs #63
mrjoelkemp
added a commit
to dependents/node-dependency-tree
that referenced
this issue
Nov 19, 2018
Refs pahen/madge#184 Refs pahen/madge#167 Refs pahen/madge#179
mrjoelkemp
added a commit
to dependents/node-dependency-tree
that referenced
this issue
Nov 19, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello. Thank you for madge) It's really awesome!
Seems like magde has no option for providing tsconfig. I need to resolve aliased imports inside typescript files. When I change aliased import to standard one dependency graph is shown correctly.
The text was updated successfully, but these errors were encountered: