Merge branch 'master' into fixed-sidebar

Author: SpaceK33z

.travis.yml

@@ -8,6 +8,8 @@ node_js:
 script:
   - bash ./scripts/deploy.sh
 sudo: required
+cache: yarn
 install:
-  - npm install
+  - npm i yarn -g
+  - yarn
   - sudo pip install proselint

bootstrap.js

@@ -11,4 +11,6 @@ antwar[environment]({
   webpack: require('./webpack.config')
 }).catch(function (err) {
   console.error(err);
+
+  process.exit(1);
 });

content/concepts/output.md

@@ -64,9 +64,9 @@ For more information on cross-origin loading see [MDN](https://developer.mozilla
 
 > Default: `false`
 
-> see also [[library and externals]]
+> see also [library](/guides/author-libraries/)
 
-> see also [[Development Tools]]
+> see also [Development Tools](/guides/development/#choosing-a-tool)
 
 ### `output.devtoolLineToLine`
 

content/development/how-to-write-a-loader.md

@@ -9,7 +9,7 @@ This function is called when a resource should be transformed by this loader.
 
 In the simple case, when only a single loader is applied to the resource, the loader is called with one parameter: the content of the resource file as string.
 
-The loader can access the [[loader API | loaders]] on the `this` context in the function.
+The loader can access the [loader API](api/loaders/) on the `this` context in the function.
 
 A sync loader that only wants to give a one value can simply `return` it. In every other case the loader can give back any number of values with the `this.callback(err, values...)` function. Errors are passed to the `this.callback` function or thrown in a sync loader.
 

content/development/how-to-write-a-plugin.md

@@ -20,7 +20,8 @@ These two components are an integral part of any webpack plugin (especially a `c
 
 ## Basic plugin architecture
 
-Plugins are instanceable objects with an `apply` method on their prototype. This `apply` method is called once by the webpack compiler while installing the plugin. The `apply` method is given a reference to the underlying webpack compiler, which grants access to compiler callbacks. A simple plugin is structured as follows:
+
+Plugins are instantiated objects with an `apply` method on their prototype. This `apply` method is called once by the Webpack compiler while installing the plugin. The `apply` method is given a reference to the underlying Webpack compiler, which grants access to compiler callbacks. A simple plugin is structured as follows:
 
 ```javascript
 function HelloWorldPlugin(options) {
@@ -71,7 +72,7 @@ HelloCompilationPlugin.prototype.apply = function(compiler) {
 module.exports = HelloCompilationPlugin;
 ```
 
-For more information on what callbacks are available on the `compiler`, `compilation`, and other important objects, see the [[plugins API|plugins]] doc.
+For more information on what callbacks are available on the `compiler`, `compilation`, and other important objects, see the [plugins](/api/plugins/) doc.
 
 ## Async compilation plugins
 

content/guides/build-performance.md

@@ -12,5 +12,6 @@ sort: 15
 > resolving
 > DllPlugin
 
-> see also [[development tools]]
-> see also [[resolving]]
+[Development Tools](/guides/development/#choosing-a-tool)
+
+> see also [resolving](/concepts/module-resolution/#resolving-rules-in-webpack)

content/guides/code-splitting-libraries.md

@@ -5,6 +5,7 @@ contributors:
   - pksjce
   - chrisVillanueva
   - johnstew
+  - rafde
 ---
 
 A typical application uses third party libraries for framework/functionality needs. Particular versions of these libraries are used and code here does not change often. However, the application code changes frequently.
@@ -109,6 +110,38 @@ module.exports = function(env) {
 ```
 Now run `webpack` on your application. Bundle inspection shows that `moment` code is present only in the vendor bundle.
 
+## Implicit Common Vendor Chunk
+
+You can configure a `CommonsChunkPlugin` instance to only accept vendor libraries.
+ 
+ __webpack.config.js__
+ 
+```javascript
+var webpack = require('webpack');
+var path = require('path');
+
+module.exports = function() {
+    return {
+        entry: {
+            main: './index.js'
+        },
+        output: {
+            filename: '[chunkhash].[name].js',
+            path: path.resolve(__dirname, 'dist')
+        },
+        plugins: [
+            new webpack.optimize.CommonsChunkPlugin({
+                name: 'vendor',
+                minChunks: function (module) {
+                   // this assumes your vendor imports exist in the node_modules directory
+                   return module.context && module.context.indexOf('node_modules') !== -1;
+                }
+            })
+        ]
+    };
+}
+```
+
 ## Manifest File
 
 But, if we change application code and run `webpack` again, we see that the hash for the vendor file changes. Even though we achieved separate bundles for `vendor` and `main` bundles, we see that the `vendor` bundle changes when the application code changes.

package.json

@@ -98,7 +98,7 @@
     "d3": "^4.2.7",
     "filesize": "^3.3.0",
     "preact": "^6.2.1",
-    "preact-compat": "^3.6.0",
+    "preact-compat": "3.11.0",
     "react": "^15.3.2",
     "react-dom": "^15.3.2",
     "react-router": "^2.8.1",