Update docs for 1.0

Author: RamDev0228

docs/autoloading.md

@@ -6,7 +6,7 @@ mix.autoload({
 });
 ```
 
-webpack offers the necessary facilities to make a module available as a variable in every other module required by webpack. If you're working with a particular plugin or library that depends upon a global variable, such as jQuery, `mix.autoload()` may prove useful to you.
+Webpack offers the necessary facilities to make a module available as a variable in every other module required by webpack. If you're working with a particular plugin or library that depends upon a global variable, such as jQuery, `mix.autoload()` may prove useful to you.
 
 Consider the following example:
 

docs/basic-example.md

@@ -18,7 +18,7 @@ Done. Simple, right?
 
 With this configuration in place, we may trigger webpack from the command line: `node_modules/.bin/webpack`.
 
-During development, it's unnecessary to minify the output, however, this will be performed automatically when you trigger webpack within a production environment: `export NODE_ENV=production && webpack`.
+During development, it's unnecessary to minify the output, however, this will be performed automatically when you trigger webpack within a production environment: `export NODE_ENV=production webpack`.
 
 ### Less?
 

docs/concatenation-and-minification.md

@@ -38,7 +38,7 @@ mix.minify(['this/one.js', 'and/this/one.js']);
 
 There are a few things worth noting here:
 
-1. This method will overwrite the existing file.
+1. This method will create a companion `*.min.ext` file. So minifying `app.js` will generate `app.min.js`.
 2. Once again, the minification will only take place during a production build. \(`export NODE_ENV=production`\).
 3. There is no need to call `mix.combine(['one.js', 'two.js'], 'merged.js').minify('merged.js');`Just stick with the single `mix.combine()` call. It'll take care of both.
 

docs/faq.md

@@ -6,7 +6,7 @@ No. It has a few optimizations for Laravel, but it can be used for any project.
 
 ### My code isn't being minified.
 
-Minification will only be performed, when your `NODE_ENV` is set to production. Not only will this speed up your compilation time, but it's also unnecessary during development. Here's an example of running webpack for production.
+Minification will only be performed, when your `NODE_ENV` is set to *production*. Not only will this speed up your compilation time, but it's also unnecessary during development. Here's an example of running webpack for production.
 
 ```bash
 export NODE_ENV=production && webpack --progress --hide-modules
@@ -16,10 +16,10 @@ It's highly recommended that you add the following NPM scripts to your `package.
 
 ```js
   "scripts": {
-    "dev": "cross-env NODE_ENV=development webpack --progress --hide-modules",
-    "watch": "cross-env NODE_ENV=development webpack --watch --progress --hide-modules",
-    "hot": "cross-env NODE_ENV=development webpack-dev-server --inline --hot",
-    "production": "cross-env NODE_ENV=production webpack --progress --hide-modules"
+    "dev": "NODE_ENV=development webpack --progress --hide-modules",
+    "watch": "NODE_ENV=development webpack --watch --progress --hide-modules",
+    "hot": "NODE_ENV=development webpack-dev-server --inline --hot",
+    "production": "NODE_ENV=production webpack --progress --hide-modules"
   },
 ```
 

docs/laravel-elixir-vs-mix.md

@@ -6,7 +6,7 @@ mix.js(src|[src], output)
 
 With a single line of code, Laravel Mix allows you to trigger a number of vital actions.
 
-* ES2015 + modules compilation
+* ES2017 + modules compilation
 * Build and compile `.vue` components \(via `vue-loader`\)
 * Hot module replacement
 * Tree-shaking, new in webpack 2 \(removes unused library code\)
@@ -117,4 +117,4 @@ Laravel Mix also ships with basic React support. Simply update your `mix.js()` c
 mix.react('resources/assets/js/app.jsx', 'public/js/app.js');
 ```
 
-Of course, you'll still want to install React and ReactDOM through NPM, per usual, but everything else should be taken care of.
+Of course, you'll still want to install React and ReactDOM through NPM, per usual, but everything else should be taken care of.

docs/mixjs.md

@@ -4,7 +4,6 @@
 * [Basic Example](basic-example.md)
 * [Installation](installation.md)
 * [Laravel Workflow](workflow.md)
-* [Laravel Mix vs. Laravel Elixir](laravel-elixir-vs-mix.md)
 * [FAQ](faq.md)
 
 ## API

docs/readme.md

@@ -5,9 +5,9 @@ mix.js('src', 'output')
    .version([]);
 ```
 
-To assist with long-term caching, Laravel Mix provides the `mix.version()` method, which enables file name hashing. such as `app.8e5c48eadbfdd5458ec6.js`. This is useful for cache-busting. Imagine that your server automatically caches scripts for a year, to improve performance. That's great, but, each time you make a change to your application code, you need some way to instruct the server to bust the cache. This is typically done through the use of query strings, or file hashing.
+To assist with long-term caching, Laravel Mix provides the `mix.version()` method, which enables file hashing. such as `app.js?id=8e5c48eadbfdd5458ec6`. This is useful for cache-busting. Imagine that your server automatically caches scripts for a year, to improve performance. That's great, but, each time you make a change to your application code, you need some way to instruct the server to bust the cache. This is typically done through the use of query strings, or file hashing.
 
-With versioning enabled, each time your code changes, a new hashed file will be generated, and the old one will be deleted. Consider the following `webpack.mix.js` file.
+With versioning enabled, each time your code changes, a new hashed query  string file will be generated. Consider the following `webpack.mix.js` file.
 
 ```js
 let mix = require('laravel-mix');
@@ -17,7 +17,7 @@ mix.js('resources/assets/js/app.js', 'public/js')
    .version();
 ```
 
-Upon compilation, you'll see `./public/css/app.8e5c48eadbfdd5458ec6.css` and .`/public/js/app.8e5c48eadbfdd5458ec6.js`. Of course, your particular hash will be unique. Each time you adjust your JavaScript, the compiled files will receive a newly hashed name, which will effectively bust the cache, once pushed to production.
+Upon compilation, you'll see `/css/app.css?id=5ee7141a759a5fb7377a` and `/js/app.js?id=0441ad4f65d54589aea5` in your `mix-manifest.json` file. Of course, your particular hash will be unique. Each time you adjust your JavaScript, the compiled files will receive a newly hashed name, which will effectively bust the cache, once pushed to production.
 
 As an example, try running`webpack --watch`, and then change a bit of your JavaScript. You'll instantly see a newly generated bundle and stylesheet.
 

docs/versioning.md

@@ -21,11 +21,11 @@ Think of this file as your home base for all front-end configuration.
 ```js
 let mix = require('laravel-mix');
 
-mix.js('resources/assets/js/app.js', 'public/js');
-mix.sass('resources/assets/sass/app.scss', 'public/css');
+mix.js('resources/assets/js/app.js', 'public/js')
+    .sass('resources/assets/sass/app.scss', 'public/css');
 ```
 
-By default, we've enabled JavaScript ES2015 + module bundling, as well as Sass compilation.
+By default, we've enabled JavaScript ES2017 + module bundling, as well as Sass compilation.
 
 ### Step 4: Compilation
 
@@ -54,6 +54,8 @@ npm run watch
 
 Laravel ships with a `./resources/assets/js/components/Example.vue` file. Give it a tweak, and wait for the OS notification, which signals that the compilation has completed. Great!
 
+> Tip: You may also use `mix.browserSync('myapp.dev')` to automatically reload the browser when any relevant file in your Laravel app is changed.
+
 ### Step 5: Update Your View
 
 Again, Laravel ships with a welcome page. We can use this for our demo. Update it to:
@@ -78,18 +80,3 @@ Again, Laravel ships with a welcome page. We can use this for our demo. Update i
 ```
 
 And reload the page in your browser. Great! It works.
-
-### Step 6: Hot Reloading
-
-It would be nice if we could update a Vue component, and instantly see it refresh in the browser, without having to perform a manual refresh. Even better, it would be nice if this refresh didn't reset our component's state. Well, hot module replacement to the rescue!
-
-Return to the command line, and hit `Ctrl+c` to cancel the webpack watcher. Instead, we'll run:
-
-```bash
-npm run hot
-```
-
-"hot" stands for "hot module replacement." This command is the only thing you have to do to activate automatic reloading. Return to your browser, give it a refresh, and then return to your editor to modify the `./resources/assets/js/components/Example.vue` file. Change the template however you wish, and watch as the browser instantly refreshes to reflect your change \(once you hit save, of course\). Amazing!
-
-
-