Joel Kemp

That sounds good. Would madge be the supplier of the html detective and partial-resolver (like the resolvers in filing-cabinet)? Or would you pass that off to users of madge to...

Is it fine to have the most recently registered language pack win in the case of conflicts (i.e., when folks override an existing file extension's language pack)? Or should it...

@reuwi please feel free to submit a PR.

Hey! What does the debug output look like? https://github.com/pahen/madge#debugging Curious if the dependencies are being extracted by the typescript detective. If so, the it's either something specific to the cli...

Hey! Does it still happen if you set `includeNpm` to true: https://github.com/pahen/madge#configuration?

Thanks for confirming. We just delegate to the typescript compiler for module path resolution: https://github.com/dependents/node-filing-cabinet/blob/master/index.js#L145-L153. Are you supplying a typescript config? If so, perhaps there's a relevant configuration option you...

Thanks for reporting the issue. I'm afraid that the fancy footwork is defeating static analysis here :) The only way for dependency-tree to recognize those imports is to evaluate the...

This still might be unsupported at the commonjs resolution layer, but your madgerc might have a bug (may or may not fix it): `"es6.mixedImports": true` should be `es6: { mixedImports:...

Thanks for confirming! Assuming that's a valid import (curious why you need to qualify that import with the package name), there must be support for that missing in the node-filing-cabinet...

Hey! It feels like a post-webpack run type of situation where you'd need webpack to run to do the replacement. My only hunch without running madge on the webpack output...