webpack: Unexpected code after tree-shake

Hi, everyone. I am implementing this feature. Here’s my repo:

https://github.com/vincentdchan/webpack-deep-scope-analysis-plugin

And demo, you can experience the analysis:

https://vincentdchan.github.io/webpack-deep-scope-demo/

If things go well, we can use it very soon. It will come faster if anyone can add more tests or edge cases to my repo. Thank you!

Don’t you dare.

Work done in webpack@5. Provided example works with latest beta (webpack@5.0.0-beta.14).

I think this issue could be closed @evilebottnawi

Good boy

Did anything ever come of this? Any plans to integrate @vincentdchan 's work?

This doesn’t work yet. We don’t do this kind of scope analysis yet, but this is prepared in some places and could be added.

@dmwyatt Thanks for following. My plugin has been released for a while, and I rarely receive bugs report. I don’t know if it’s really tested by the community even though I have a lot of unit tests. Because shaking wrong modules would make production code crash. I am worried.

@sokra Maybe I could submit a PR for integrating the plugin as an optional parameter, people can choose to use it.

@Birowsky have you had a chance to look into the work @vincentdchan has been providing in this case? Hoping to get some feedback for him as this may directly assist with your issue.

By using ModuleConcatenationPlugin, webpack does eliminate external2 stuff correctly.

Here’s output from webpack 4 with ModuleConcatenationPlugin and UglifyJSPlugin: gist link.

I think this bug report captured the scope analysis you were looking for, for not including code that will not be used. Yes, it can be removed via dead code elimination (#PURE etc), but we can get even smaller bundles ala rollup by implementing strict live code inclusion.