Project support

[Berkmann18]

I've seen that the multi-file support was on the TODO list but as that could mean supporting * ops (e.g: *.js) as well as projects, I was wondering which one it was and if it was the latter, then my question would be:
Will it know about the data-structures that a module (e.g: main.js) uses from another one (regardless of whether it's NodeJS/ES6 modules?
Example in NodeJS (the same could be said for ES6 modules):
main.js

let aModule = require('./aModule');

// some code here
aModule.doSomething();

I'm aware that the latter would possibly require a filter to prevent this generator to go deep in the (yarn|node)_modules or any library files that aren't really part of the project so I'm willing to help (if there's need).

[Bogdan-Lyashenko]

Hey, thanks for the interest.) well, original idea was to use webpack dependencies tree builder for that, I just can’t imagine another better way of handling modules dependencies, so, the short answer is - webpack will manage that. Nice to hear you would like to contribute, it would be really great, thanks. Let me know if you need some guidance where to start.

[Berkmann18]

So would that be basically using webpack without requiring the targeted projects to use webpack?
Sure, will do if I need :).

[Bogdan-Lyashenko]

Yes, exactly.)

[Berkmann18]

Cool :).