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
AMD not finding nested depedencies #67
Comments
define(['dep'], function() {
// Lazy load a file
require(['some_file'], function() {});
}); That option would allow |
Yes, that's right. I would like to see a graph for my entire dependency tree. |
That's what I thought this module did—showed you the whole dependency tree? |
Any thoughts on it? @pahen @mrjoelkemp? I'm quite surprised it only shows one level of dependencies. Is that intentional? |
The expectation of the api seems to be such that you pass in a directory path if you want a scan of all files to be included in the tree. Your usage only specifies a single file. If you need to specify just that one file, then recursively tracing the tree is one solution. Alternatively, you could look into running madge on the bundled/optimized output using the mainRequireModule setting. |
That helps, thanks! On Tue, 1 Dec 2015, 12:11 Joel Kemp notifications@github.com wrote:
|
No problem! Safe to close this issue?
|
this LIMITATION of one level dependencies, I have also wasted some time for this, trying to use another tool (dependo) which is using your project. |
Given:
When I run:
The output is:
How come madge is not finding the nested AMD dependencies?
The text was updated successfully, but these errors were encountered: