Limit module depth of compiler messages

Jul 6, 2014 at 10:26 PM
When I build a nodejs + express project, I see lots of JS error messages about "Ambiguous reference to named function expression. Cross-browser behavior difference" in nodejs modules used by modules referenced by my code. For example: C:\src\myproj\node_modules\stylus\node_modules\glob\node_modules\minimatch\minimatch.js

My project doesn't reference minmatch, but I do reference stylus and stylus uses glob which uses minmatch.

Is there some way to constrain the JS scanner to only report issues in modules I write or directly reference? I'm really not interested in all that noise from modules I don't directly use or have control over. Such a constraint might also help reduce memory consumption.

July 3 build, VS2013
Jul 11, 2014 at 9:12 PM
This will be fixed in the next build.
Oct 6, 2014 at 5:24 PM
the problem is still there!