For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

I notice there are a bunch of addPresentationalDependecy calls also made on module instead of current. But they are all like that, so I guess that's correct, right? (I'm not sure what a presentation dependency is...)

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

I notice there are a bunch of addPresentationalDependecy calls also made on module instead of current. But they are all like that, so I guess that's correct, right? (I'm not sure what a presentation dependency is...)

That's fine. presentational dependencies only exist on Module not on AsyncDependenciesBlock. That are dependencies that doesn't point to a module and have only effects on the generated code. They are often not walked, as they do not influence the module graph, etc.