Skip to content

Loader swallows informative error messages when loading modules #42

@kitsonk

Description

@kitsonk

When a module cannot be loaded, in particular, CommonJS ones, for example the following stack trace is wholly uninformative:

windows_10

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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions