-
Notifications
You must be signed in to change notification settings - Fork 44
Compatibility with uglify plugin? #9
Comments
I have the exactly same issue. Was trying to change my build from gulp but the result becomes much bigger. |
I understand now, at least in part why it doesn't work. Given that the content of the files loaded with a script loader is just taken and wrapped in an eval. I followed the advice here and wrote a simpler "uglify only" loader, which I will at least put on npm in case it's useful to someone else. I also found this loader which I am experimenting with to see if it fits my needs. I am trying to get source maps working, which I think the loader I just referenced achieves. |
Oh yeah, that loader did the trick. But you need to put the
Thanks! |
|
Is there a known issue with comments not being uglified out of modules being loaded with
script-loader
?For instance, I have an entry file which looks like this...
...and a simplified version of my webpack config looks like this...
* using temporary solution for the structure of the
comments
output option from hereIn this case, the resulting file still has a bunch of comments in it.
Am I missing something, or does uglify comment stripping just not work with files loaded with the
script-loader
? Are there other limitation when it comes to minification I should be aware of?Thanks in advance for any help!
The text was updated successfully, but these errors were encountered: