Enable text compression using React, Webpack and Apache

Short answer: the kushalvm's solution is not complete. In order to compress the page size with gzip/brotli, there are two steps:

1. Create .gz/.br files in build time (or dynamically generate them by a server)
2. Serve them (instead of .js files)

And you are doing the first part but not the second one. Because when you build a react project (in case of client-side rendering - CSR) you simply create one .html file importing some script tags (your react project). If you use brotli or compression plugin for webpack you have created some .gz/.br files, but still, the HTML file imports the old .js scripts.

So what are the different methods you can use to serve compressed files you need to configure your server (you cannot do this just by changing your React configs)

Solutions

1)If you are using client-side rendering, you can create a custom express server used to serve files, it is very simple and takes less than 10 lines of code, you can read the doc about this in the Official React Docs (with express-static-gzip)So your server file will look like this:

const express = require('express');const path = require('path');const app = express();app.use(  expressStaticGzip(path.join(__dirname, 'build'), {  enableBrotli: true, // only if you have brotli files too  }),);app.use(express.static(path.join(__dirname, 'build')));app.get('/', function(req, res) {  res.sendFile(path.join(__dirname, 'build', 'index.html'));});app.listen(9000);

This server, will read the files in the build directory, and if a request for some js assets arrives, it checks (if the browser supports the compression, and if compression file exists for it) then serves compressed files

2) If you use SSR (for example Next.js or React-Starter-kit) you can create a custom express server, and use the same approach above.

3) If you use Apache webserver, you can use Apache gzip/brotli compressions config file like this:

# enable the rewrite capabilitiesRewriteEngine On# prevents the rule from being overrided by .htaccess files in subdirectoriesRewriteOptions InheritDownBefore# provide a URL-path base (not a file-path base) for any relative paths in the rule's targetRewriteBase /# GZIP## allows you to have certain browsers uncompress information on the flyAddEncoding gzip .gz## serve gzip .css files if they exist and the client accepts gzipRewriteCond %{HTTP:Accept-encoding} gzipRewriteCond %{REQUEST_FILENAME}\.gz -sRewriteRule ^(.*)\.css $1\.css\.gz [QSA]## serve gzip .js files if they exist and the client accepts gzipRewriteCond %{HTTP:Accept-encoding} gzipRewriteCond %{REQUEST_FILENAME}\.gz -sRewriteRule ^(.*)\.js $1\.js\.gz [QSA]## serve gzip .html files if they exist and the client accepts gzipRewriteCond %{HTTP:Accept-encoding} gzipRewriteCond %{REQUEST_FILENAME}\.gz -sRewriteRule ^(.*)\.html $1\.html\.gz [QSA]## serve correct content types, and prevent mod_deflate double gzipRewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1,E=is_gzip:1]RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1,E=is_gzip:1]RewriteRule \.html\.gz$ - [T=text/html,E=no-gzip:1,E=is_gzip:1]Header set Content-Encoding "gzip" env=is_gzip

4) If you use a third party JamStack/CDN provider like Netlify or AWS, they have some configs for you to enable dynamic gzip.

You can also Build Time gzip. here is the process.

1. Install the Webpack compression plugin

   npm install compression-webpack-plugin --save-dev

2. Install and Import the plugin var CompressionPlugin = require('compression-webpack-plugin');

3. Add it to plugins array

  plugins: [    new webpack.DefinePlugin({       'process.env': {        'NODE_ENV': JSON.stringify('production')      }    }),    new webpack.optimize.DedupePlugin(),    new webpack.optimize.UglifyJsPlugin(),    new webpack.optimize.AggressiveMergingPlugin(),    new CompressionPlugin({   <-- Add this      asset: "[path].gz[query]",      algorithm: "gzip",      test: /\.js$|\.css$|\.html$/,      threshold: 10240,      minRatio: 0.8    })  ]

4. Finally, add this middleware to Express to return .js.gz so you can still load bundle.js from the html but will receive bundle.js.gz

app.get('*.js', function (req, res, next) {  req.url = req.url + '.gz';  res.set('Content-Encoding', 'gzip');  next();});

I was also struggling with serving the compressed version with my React SSR app; in my case the brotli type with js.br extension > "bundle.js.br". The following snippet helped me in the end to serve it properly. I reduced my client-side uncompressed bundle in development mode from 1.7 MB to 0.27 MB. Try and figure it out for you. There is no extra plugin needed to serve the file. Of course, the compressed version must be generated first with webpack. For webpack brotli compression I use the npmjs packages compression-webpack-plugin in conjunction with zlib.

var express = require('express');var app = express();app.get('*.js', (req, res, next) => {  if (req.header('Accept-Encoding').includes('br')) {    req.url = req.url + '.br';    console.log(req.header('Accept-Encoding'));    res.set('Content-Encoding', 'br');    res.set('Content-Type', 'application/javascript; charset=UTF-8');  }  next();});app.use(express.static('public'));

Now let me explain my snippet above which I use for my SSR React app to serve the compressed file.

• Using the argument '*.js' at the beginning means that this app.get works for every endpoint that is fired to fetch a JS file.
• Inside the callback, I attach .br to the URL of the request. Furthermore, the Content-Encoding response header is set to br.
• The Content-Type header is set to application/javascript; charset=UTF-8 to specify the MIME type.
• At the end and very important, next() makes possible to continue to any callback that may be next.
• Do not forget to provide the folder where your compressed bundle is placed. I used app.use(express.static('public')) in my case.