Adding gZip compression plugin
See original GitHub issueI am following this tutorial on adding a gZip compression to webpack: http://forum.vuejs.org/topic/4059/adding-gzip-to-webpack-using-compression-plugin
Wanted to check if I am doing this correctly by only adding it to the webpack.config.prod.js
or should I also add it to others?
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
How to Enable GZIP Compression in WordPress (3 Ways)
Enabling GZIP Compression with WPRocket ... WP Rocket is the best caching plugin for WordPress. It is incredibly easy to use and turns...
Read more >How to Enable GZIP Compression to Speed Up WordPress ...
The easiest way to enable GZIP compression on your WordPress site is by using a caching or performance optimization plugin. For example, if...
Read more >How to Enable Compression in WordPress
To enable WordPress GZIP compression using WP Super Cache, first install and activate the plugin. Then navigate to WP Super Cache > Advanced ......
Read more >Enabling WordPress GZIP Compression
To enable WordPress GZIP compression with WP Super Cache, go to the WordPress dashboard > WP Super Cache > Advanced > and check...
Read more >Speed Up Your WordPress Website with Gzip Compression
Find the option labeled Compress pages so they're served more quickly to visitors, and check the box next to it. Then click on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jrodl3r its not something that I had previously concerned myself with, but there doesn’t seem to be much of a downside to adding it. Losing IE6 support ??
@IljaDaderko and I both ran into the issue when Google brought it up. I don’t blindly follow everything Google says, but if they are saying it would be beneficial to gzip your assets to delivery your site more quickly, I think they probably know what they are talking about.
And then I was just listening to the latest episode of javascrip jabber and they had Yehuda Katz on as a guest talking about Ember. He said the point of a framework is to solve problems that people didn’t know they had. I think compression falls under this. I think as long as we declare it in the readme under features it should be cool. Those that are too naive to know what it is will receive the benefits of it, and anyone that purposefully interested in not compressing their assets would you could safely assume have the skills needed to know where to look to remove it.
@choonkending As a side note. if we could get the [page speed(https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Freact-webpack-node.herokuapp.com%2F&tab=mobile) numbers a better then we could actually advertise that as a feature as well.
@jrodl3r care to offer a pull request with that added in?