docs(readme): Adding example of manual hotloader implementation

In the event users cannot get it to work, theres an example in the docs to reference

Author: ScriptedAlchemy

README.md

@@ -281,6 +281,30 @@ new ExtractCssChunk({
 
 >Keep in mind, by default `[name].css` is used when `process.env.NODE_ENV === 'development'` and `[name].[contenthash].css` during production, so you can likely forget about having to pass anything.
 
+### HMR Troubleshooting
+**Blank array in HMR script?**
+
+If you have issues with HMR, but enabled the loader, plugin, and already tried `hot: true, reloadAll:true`, then your webpack config might be more abstract than my simple lookup functions. In this case, Ive exported out the actual hot loader, you can add this manually and as long as you've got the plugin and loader -- it'll work 
+
+```js
+ rules: [
+      {
+        test: /\.css$/,
+        use: [
+          ExtractCssChunks.hotLoader, // for those who want to manually force hotLoading
+          ExtractCssChunks.loader,
+          {
+            loader: 'css-loader',
+            options: {
+              modules: true,
+              localIdentName: '[name]__[local]--[hash:base64:5]',
+            },
+          },
+        ],
+      },
+    ]
+```
+
 ### HMR Pitfall
 
 The most common workflow when working with webpack is to write a "development" / "production" value in to the