Merge pull request #1 from octohedron/fix/hmr-background

Fix/hmr background

Author: octohedron

README.md

@@ -76,7 +76,7 @@ $ PORT=6002 npm run start
 
 ## Content Scripts
 
-Although this boilerplate uses the webpack dev server, it's also prepared to write all your bundles files on the disk at every code change, so you can point, on your extension manifest, to your bundles that you want to use as [content scripts](https://developer.chrome.com/extensions/content_scripts), but you need to exclude these entry points from hot reloading [(why?)](https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate/issues/4#issuecomment-261788690). To do so you need to expose which entry points are content scripts on the `webpack.config.js` using the `chromeExtensionBoilerplate -> notHotReload` config. Look the example below.
+Although this boilerplate uses the webpack dev server, it's also prepared to write all your bundles files on the disk at every code change, so you can point, on your extension manifest, to your bundles that you want to use as [content scripts](https://developer.chrome.com/extensions/content_scripts), but you need to exclude these entry points from hot reloading [(why?)](https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate/issues/4#issuecomment-261788690). To do so you need to expose which entry points are content scripts on the `webpack.config.js` using the `custom -> notHMR` config. Look the example below.
 
 Let's say that you want use the `myContentScript` entry point as content script, so on your `webpack.config.js` you will configure the entry point and exclude it from hot reloading, like this:
 
@@ -86,8 +86,8 @@ Let's say that you want use the `myContentScript` entry point as content script,
   entry: {
     myContentScript: "./src/js/myContentScript.js"
   },
-  chromeExtensionBoilerplate: {
-    notHotReload: ["myContentScript"]
+  custom: {
+    notHMR: ["myContentScript"]
   }
   …
 }