Tobias Koppers

You can dynamically load remote modules using this: ``` js // Initializes the share scope. // This fills it with known provided modules from this build and all remotes await...

Thanks fixed

`errorStack` only refers to (webpack)-internal stack traces. Stack traces from loaders can be disabled with `errorDetails: false`

Since this is a virtual filesystem, we should also check how it behaves when requesting `fs.stat` for this (fake) folders.

> Note that the virtual entries won't be returned as part of a `readdir` call though That's probably the problem. When starting watching we will do an initial scan of...

For webpack that's only a filesystem. We don't know it's special/virtual. If it behaves inconsistent that will lead to problems.

 It does already do that

This is not how to use the webpack logger. Use `compilation.getLogger("my-plugin")`

The runtime logger is intended for in browser usage where the browser devtools take care of colors and filtering. It's not intended for usage in node.js, because you won't have...

Send a PR Here is similar code and also the place where this need to be added: https://github.com/webpack/webpack/blob/27796db6ebcae2bed804609e90411204d73c1031/lib/NormalModuleFactory.js#L678-L724