plugins: fix parsing errors

Author: byzyk

.eslintrc

@@ -42,7 +42,8 @@
         "no-extra-semi": 0,
         "no-redeclare": 0,
         "no-unused-labels": 0,
-        "no-use-before-define": 0
+        "no-use-before-define": 0,
+        "no-mixed-spaces-and-tabs": 0
       }
     }
   ]

src/content/plugins/aggressive-splitting-plugin.md

@@ -2,6 +2,7 @@
 title: AggressiveSplittingPlugin
 contributors:
   - pierreneter
+  - byzyk
 ---
 
 The `AggressiveSplittingPlugin` can split bundles into smaller chunks, splitting every chunk until it reaches the specified `maxSize` configured in `options`. It groups modules together by folder structure.
@@ -19,7 +20,7 @@ new webpack.optimize.AggressiveSplittingPlugin(options)
 
 ## Options
 
-```js
+```ts
 {
   minSize: 30000, //Byte, split point. Default: 30720
   maxSize: 50000, //Byte, maxsize of per file. Default: 51200

src/content/plugins/banner-plugin.md

@@ -2,14 +2,15 @@
 title: BannerPlugin
 contributors:
   - simon04
+  - byzyk
 related:
   - title: banner-plugin-hashing test
     url: https://github.com/webpack/webpack/blob/master/test/configCases/plugins/banner-plugin-hashing/webpack.config.js
 ---
 
 Adds a banner to the top of each generated chunk.
 
-``` javascript
+```javascript
 new webpack.BannerPlugin(banner)
 // or
 new webpack.BannerPlugin(options)
@@ -18,7 +19,7 @@ new webpack.BannerPlugin(options)
 
 ## Options
 
-```javascript
+```ts
 {
   banner: string, // the banner as string, it will be wrapped in a comment
   raw: boolean, // if true, banner will not be wrapped in a comment

src/content/plugins/commons-chunk-plugin.md

@@ -7,6 +7,7 @@ contributors:
   - kevinzwhuang
   - jdbevan
   - jeremenichelli
+  - byzyk
 ---
 
 The `CommonsChunkPlugin` is an opt-in feature that creates a separate file (known as a chunk), consisting of common modules shared between multiple entry points.
@@ -22,7 +23,7 @@ new webpack.optimize.CommonsChunkPlugin(options)
 
 ## Options
 
-```javascript
+```ts
 {
   name: string, // or
   names: string[],
@@ -38,7 +39,7 @@ new webpack.optimize.CommonsChunkPlugin(options)
   // If omitted the original filename is not modified (usually `output.filename` or `output.chunkFilename`).
   // This option is not permitted if you're using `options.async` as well, see below for more details.
 
-  minChunks: number|Infinity|function(module, count) -> boolean,
+  minChunks: number|Infinity|function(module, count) => boolean,
   // The minimum number of chunks which need to contain a module before it's moved into the commons chunk.
   // The number must be greater than or equal 2 and lower than or equal to the number of chunks.
   // Passing `Infinity` just creates the commons chunk, but moves no modules into it.
@@ -103,21 +104,24 @@ You must load the generated chunk before the entry point:
 Split your code into vendor and application.
 
 ```javascript
-entry: {
-  vendor: ["jquery", "other-lib"],
-  app: "./entry"
-},
-plugins: [
-  new webpack.optimize.CommonsChunkPlugin({
-    name: "vendor",
-    // filename: "vendor.js"
-    // (Give the chunk a different name)
-
-    minChunks: Infinity,
-    // (with more entries, this ensures that no other module
-    //  goes into the vendor chunk)
-  })
-]
+module.exports = {
+  //...
+  entry: {
+    vendor: ["jquery", "other-lib"],
+    app: "./entry"
+  },
+  plugins: [
+    new webpack.optimize.CommonsChunkPlugin({
+      name: "vendor",
+      // filename: "vendor.js"
+      // (Give the chunk a different name)
+
+      minChunks: Infinity,
+      // (with more entries, this ensures that no other module
+      //  goes into the vendor chunk)
+    })
+  ]
+}
 ```
 
 ```html

src/content/plugins/context-replacement-plugin.md

@@ -2,6 +2,7 @@
 title: ContextReplacementPlugin
 contributors:
   - simon04
+  - byzyk
 related:
   - title: Issue 2783 - ContextReplacementPlugin Description
     url: https://github.com/webpack/webpack/issues/2783#issuecomment-234137265
@@ -17,9 +18,9 @@ The `ContextReplacementPlugin` allows you to override the inferred information.
 ```javascript
 new webpack.ContextReplacementPlugin(
   resourceRegExp: RegExp,
-  newContentResource?: string,
-  newContentRecursive?: boolean,
-  newContentRegExp?: RegExp
+  newContentResource: string, // optional
+  newContentRecursive: boolean, // optional
+  newContentRegExp: RegExp // optional
 )
 ```
 
@@ -58,7 +59,7 @@ new webpack.ContextReplacementPlugin(/^\.\/locale$/, (context) => {
     regExp: /^\.\/\w+/,
     request: '../../locale' // resolved relatively
   });
-}),
+})
 ```
 
 

src/content/plugins/module-concatenation-plugin.md

@@ -3,6 +3,7 @@ title: ModuleConcatenationPlugin
 contributors:
   - skipjack
   - TheLarkInn
+  - byzyk
 related:
   - webpack 3: Official Release!!
 ---
@@ -11,7 +12,7 @@ In the past, one of webpack’s trade-offs when bundling was that each module in
 
 This plugin will enable the same concatenation behavior in webpack.
 
-``` js
+```js
 new webpack.optimize.ModuleConcatenationPlugin()
 ```
 
@@ -29,12 +30,12 @@ As the article explains, webpack attempts to achieve partial scope hoisting. It
 Condition                                     | Outcome
 --------------------------------------------- | --------
 Non ES6 Module                                | Prevent
-Imported By Non Import                        | Root   
-Imported From Other Chunk                     | Root   
-Imported By Multiple Other Module Groups      | Root   
-Imported With `import()`                      | Root   
+Imported By Non Import                        | Root
+Imported From Other Chunk                     | Root
+Imported By Multiple Other Module Groups      | Root
+Imported With `import()`                      | Root
 Affected By `ProvidePlugin` Or Using `module` | Prevent
-HMR Accepted                                  | Root   
+HMR Accepted                                  | Root
 Using `eval()`                                | Prevent
 In Multiple Chunks                            | Prevent
 `export * from "cjs-module"`                  | Prevent
@@ -90,11 +91,13 @@ function tryToAdd(group, module) {
 When using the webpack CLI, the `--display-optimization-bailout` flag will display bailout reasons. When using the webpack config, just add the following to the `stats` object:
 
 ```js
-{
-  ...stats,
-  // Examine all modules
-  maxModules: Infinity,
-  // Display bailout reasons
-  optimizationBailout: true
+module.exports = {
+  //...
+  stats: {
+    // Examine all modules
+    maxModules: Infinity,
+    // Display bailout reasons
+    optimizationBailout: true
+  }
 }
 ```

src/content/plugins/source-map-dev-tool-plugin.md

@@ -4,14 +4,15 @@ contributors:
   - johnnyreilly
   - simon04
   - neilkennedy
+  - byzyk
 related:
   - title: Building Source Maps
     url: https://survivejs.com/webpack/building/source-maps/#-sourcemapdevtoolplugin-and-evalsourcemapdevtoolplugin-
 ---
 
 This plugin enables more fine grained control of source map generation. It is an alternative to the [`devtool`](/configuration/devtool/) configuration option.
 
-``` js
+```js
 new webpack.SourceMapDevToolPlugin(options)
 ```
 
@@ -50,7 +51,7 @@ The following examples demonstrate some common use cases for this plugin.
 
 The following code would exclude source maps for any modules in the `vendor.js` bundle:
 
-``` js
+```js
 new webpack.SourceMapDevToolPlugin({
   filename: '[name].js.map',
   exclude: ['vendor.js']
@@ -61,7 +62,7 @@ new webpack.SourceMapDevToolPlugin({
 
 Set a URL for source maps. Useful for hosting them on a host that requires authorization.
 
-``` js
+```js
 new webpack.SourceMapDevToolPlugin({
   append: "\n//# sourceMappingURL=http://example.com/sourcemap/[url]",
   filename: '[name].map'
@@ -70,7 +71,7 @@ new webpack.SourceMapDevToolPlugin({
 
 And for cases when source maps are stored in the upper level directory:
 
-``` js
+```
 project
 |- dist
   |- public
@@ -81,7 +82,7 @@ project
 
 With next config:
 
-``` js
+```js
 new webpack.SourceMapDevToolPlugin({
   filename: "sourcemaps/[file].map",
   publicPath: "https://example.com/project/",
@@ -91,6 +92,6 @@ new webpack.SourceMapDevToolPlugin({
 
 Will produce the following URL:
 
-``` js
-https://example.com/project/sourcemaps/bundle-[hash].js.map`
+```
+https://example.com/project/sourcemaps/bundle-[hash].js.map
 ```

src/content/plugins/split-chunks-plugin.md

@@ -5,7 +5,7 @@ contributors:
   - jeremenichelli
   - chrisdothtml
   - EugeneHlushko
-
+  - byzyk
 related:
   - title: "webpack 4: Code Splitting, chunk graph and the splitChunks optimization"
     url: https://medium.com/webpack/webpack-4-code-splitting-chunk-graph-and-the-splitchunks-optimization-be739a861366
@@ -42,25 +42,30 @@ W> Default configuration was chosen to fit web performance best practices but th
 This configuration object represents the default behavior of the `SplitChunksPlugin`.
 
 ```js
-splitChunks: {
-	chunks: "async",
-	minSize: 30000,
-	minChunks: 1,
-	maxAsyncRequests: 5,
-	maxInitialRequests: 3,
-	automaticNameDelimiter: '~',
-	name: true,
-	cacheGroups: {
-		vendors: {
-			test: /[\\/]node_modules[\\/]/,
-			priority: -10
-		},
-		default: {
-			minChunks: 2,
-			priority: -20,
-			reuseExistingChunk: true
-		}
-	}
+module.exports = {
+	//...
+  optimization: {
+    splitChunks: {
+    	chunks: "async",
+    	minSize: 30000,
+    	minChunks: 1,
+    	maxAsyncRequests: 5,
+    	maxInitialRequests: 3,
+    	automaticNameDelimiter: '~',
+    	name: true,
+    	cacheGroups: {
+    		vendors: {
+    			test: /[\\/]node_modules[\\/]/,
+    			priority: -10
+    		},
+    		default: {
+    			minChunks: 2,
+    			priority: -20,
+    			reuseExistingChunk: true
+    		}
+    	}
+    }
+  }
 }
 ```
 
@@ -206,13 +211,13 @@ module.exports = {
 
 ### Defaults: Example 1
 
-``` js
+```js
 // index.js
 
 import("./a"); // dynamic import
 ```
 
-``` js
+```js
 // a.js
 import "react";
 
@@ -232,22 +237,22 @@ What's the reasoning behind this? `react` probably won't change as often as your
 
 ### Defaults: Example 2
 
-``` js
+```js
 // entry.js
 
 // dynamic imports
 import("./a");
 import("./b");
 ```
 
-``` js
+```js
 // a.js
 import "./helpers"; // helpers is 40kb in size
 
 //...
 ```
 
-``` js
+```js
 // b.js
 import "./helpers";
 import "./more-helpers"; // more-helpers is also 40kb in size
@@ -299,7 +304,7 @@ Create a `vendors` chunk, which includes all code from `node_modules` in the who
 __webpack.config.js__
 
 
-``` js
+```js
 module.exports = {
 	//...
 	optimization: {