Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

With treeshaking is this plugin still needed? #51

Open
frankandrobot opened this issue Feb 22, 2022 · 2 comments
Open

With treeshaking is this plugin still needed? #51

frankandrobot opened this issue Feb 22, 2022 · 2 comments

Comments

@frankandrobot
Copy link

The title says it all. If I'm not mistaken, webpack5 has pretty decent treeshaking support so I'm asking if this is needed in webpack5? webpack4?
@pinturic
Copy link

pinturic commented Feb 23, 2022 •
edited
Loading

The point is not only about the final package; I want to know which part of my code is not used anymore so I can remove it.
Especially after (big) refactoring I run this code to see if any portion of the code can be removed.

@MQuy
Copy link
Owner

MQuy commented Feb 23, 2022

like @pinturic mentioned, webpack does tree shaking but it is just the output. If you want to cleanup your codebase, this plugin will help you to know which one to do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@frankandrobot @MQuy @pinturic