Loader swallows informative error messages when loading modules
kitsonk opened this issue · 1 comments
kitsonk commented
When a module cannot be loaded, in particular, CommonJS ones, for example the following stack trace is wholly uninformative:
and to find out what was really going on, I had to load the module using the NodeJS require directly to get a meaningful stack trace.
We should find a way to provide meaningful debugging and allow the real errors to be emitted.