Updated paths for webpack config and bundle tracker output file

Author: owais

README.md

@@ -53,19 +53,19 @@ STATICFILES_DIRS = (
 ```
 
 <br>
-Assuming your webpack config lives at `./assets/webpack.config.js` and looks like this
+Assuming your webpack config lives at `./webpack.config.js` and looks like this
 ```javascript
 module.exports = {
   context: __dirname,
   entry: {
-    app: './js/index'
+    app: './assets/js/index'
     output: {
       path: require('path').resolve('./assets/bundles/'),
       filename: '[name]-[hash].js',
   },
 
   plugins: [
-    new BundleTracker({filename: './assets/webpack-stats.json'})
+    new BundleTracker({filename: './webpack-stats.json'})
   ]
 }
 
@@ -92,7 +92,7 @@ WEBPACK_LOADER = {
 }
 ```
 
-`BUNDLE_DIR_NAME` refers to the dir in which webpack outputs the bundles. It should not be the full path. If `./assets` it one of you static dirs and webpack generates the bundles in `./assets/output/bundles/`, then `BUNDLE_DIR_NAME` should be `output/bundles/`.
+`BUNDLE_DIR_NAME` refers to the dir in which webpack outputs the bundles. It should not be the full path. If `./assets` is one of you static dirs and webpack generates the bundles in `./assets/output/bundles/`, then `BUNDLE_DIR_NAME` should be `output/bundles/`.
 
 If the bundle generates a file called `main-cf4b5fab6e00a404e0c7.js` and your STATIC_URL is `/static/`, then the `<script>` tag will look like this
 
@@ -105,17 +105,17 @@ If the bundle generates a file called `main-cf4b5fab6e00a404e0c7.js` and your ST
 #### STATS_FILE
 ```python
 WEBPACK_LOADER = {
-	'STATS_FILE': os.path.join(BASE_DIR, 'assets/webpack-stats.json')
+	'STATS_FILE': os.path.join(BASE_DIR, 'webpack-stats.json')
 }
 ```
 
 `STATS_FILE` is the filesystem path to the file generated by `webpack-bundle-tracker` plugin. If you initialize `webpack-bundle-tracker` plugin like this
 
 ```javascript
-new BundleTracker({filename: './assets/webpack-stats.json'})
+new BundleTracker({filename: './webpack-stats.json'})
 ```
 
-and your webpack config is located at `/home/src/assets/webpack.config.js`, then the value of `STATS_FILE` should be `/home/src/assets/webpack-stats.json`
+and your webpack config is located at `/home/src/webpack.config.js`, then the value of `STATS_FILE` should be `/home/src/webpack-stats.json`
 
 <br>
 
@@ -181,14 +181,14 @@ INSTALLED_APPS = (
 **It is up to you**. There are a few ways to handle this. I like to have slightly separate configs for production and local. I tell git to ignore my local stats + bundle file but track the ones for production. Before pushing out newer version to production, I generate a new bundle using production config and commit the new stats file and bundle. I store the stats file and bundles in a directory that is added to the `STATICFILES_DIR`. This gives me integration with collectstatic for free. The generated bundles are automatically collected to the target directory and synched to S3.
 
 
-`./assets/webpack_production.config.js`
+`./webpack_production.config.js`
 ```javascript
 config = require('./webpack.config.js');
 
 config.output.path = require('path').resolve('./assets/dist');
 
 config.plugins = [
-    new BundleTracker({filename: './assets/webpack-stats-prod.json'})
+    new BundleTracker({filename: './webpack-stats-prod.json'})
 ]
 
 // override any other settings here like using Uglify or other things that make sense for production environments.
@@ -201,7 +201,7 @@ module.exports = config;
 if not DEBUG:
     WEBPACK_LOADER.update({
         'BUNDLE_DIR_NAME': 'dist/',
-        'STATS_FILE': os.path.join(BASE_DIR, 'assets/webpack-stats-prod.json'
+        'STATS_FILE': os.path.join(BASE_DIR, 'webpack-stats-prod.json'
     })
 ```