error.module.reasons is missing

[vjpr]

When I get an error in webpack, I want to see the chain of requests that caused it to be called. But I can't find reasons when an error happened.

Is it not included until the bundle is successfully built?

Is there a way to get the chain of requests that led to a "module not found" error?

[vankop]

Is there a way to get the chain of requests that led to a "module not found" error?

no, we don't log this

[vjpr]

Does any code already exist to search for all paths from entry point to a module?

[vankop]

not sure what you mean.. you can traverse module graph to the entry point ( using code above )

[vjpr]

Just thought maybe there was a function already implemented to do such a thing. But easy enough to write myself.

[vjpr]

QQ: Is there any reason there can be a ModuleGraphConnection with no originModule?

As I understand it, a connection is the graph edge, conn.module -- "requested by" --> conn.originModule.

I'm guessing the ModuleGraphConnection doesn't just model the connection between module and originModule...

[vankop]

entrypoint connection I think should be without originModule