add singlequotes rule, autofix examples

Author: byzyk

.eslintrc

@@ -30,11 +30,9 @@
   "overrides": [
     {
       "files": ["src/content/**/*.md"],
-      "parserOptions": {
-        "codeFrame": true,
-      },
       "rules": {
         "indent": ["error", 2],
+        "quotes": ["error", "single"],
         "no-undef": 0,
         "no-constant-condition": 0,
         "no-useless-escape": 0,

src/content/api/loaders.md

@@ -147,7 +147,7 @@ module.exports = function(content) {
 
 module.exports.pitch = function(remainingRequest, precedingRequest, data) {
   if (someCondition()) {
-    return "module.exports = require(" + JSON.stringify("-!" + remainingRequest) + ");";
+    return 'module.exports = require(' + JSON.stringify('-!' + remainingRequest) + ');';
   }
 };
 ```
@@ -171,7 +171,7 @@ Given the following example this require call is used:
 In `/abc/file.js`:
 
 ``` js
-require("./loader1?xyz!loader2!./resource?rrr");
+require('./loader1?xyz!loader2!./resource?rrr');
 ```
 
 
@@ -270,15 +270,15 @@ In the example:
 ``` js
 [
   {
-    request: "/abc/loader1.js?xyz",
-    path: "/abc/loader1.js",
-    query: "?xyz",
+    request: '/abc/loader1.js?xyz',
+    path: '/abc/loader1.js',
+    query: '?xyz',
     module: [Function]
   },
   {
-    request: "/abc/node_modules/loader2/index.js",
-    path: "/abc/node_modules/loader2/index.js",
-    query: "",
+    request: '/abc/node_modules/loader2/index.js',
+    path: '/abc/node_modules/loader2/index.js',
+    query: '',
     module: [Function]
   }
 ];

src/content/api/module-methods.md

@@ -129,8 +129,8 @@ require(dependency: String);
 Synchronously retrieve the exports from another module. The compiler will ensure that the dependency is available in the output bundle.
 
 ``` javascript
-var $ = require("jquery");
-var myModule = require("my-module");
+var $ = require('jquery');
+var myModule = require('my-module');
 ```
 
 W> Using it asynchronously may not have the expected effect.
@@ -154,19 +154,19 @@ Multiple requires to the same module result in only one module execution and onl
 W> This is only needed in rare cases for compatibility!
 
 ``` javascript
-var d1 = require("dependency");
-require("dependency") === d1;
-delete require.cache[require.resolve("dependency")];
-require("dependency") !== d1;
+var d1 = require('dependency');
+require('dependency') === d1;
+delete require.cache[require.resolve('dependency')];
+require('dependency') !== d1;
 ```
 
 ``` javascript
 // in file.js
 require.cache[module.id] === module;
-require("./file.js") === module.exports;
+require('./file.js') === module.exports;
 delete require.cache[module.id];
 require.cache[module.id] === undefined;
-require("./file.js") !== module.exports; // in theory; in praxis this causes a stack overflow
+require('./file.js') !== module.exports; // in theory; in praxis this causes a stack overflow
 require.cache[module.id] !== module;
 ```
 
@@ -277,7 +277,7 @@ W> This feature relies on [`Promise`](https://developer.mozilla.org/en-US/docs/W
 
 ``` javascript
 require(['b'], function(b) {
-  var c = require("c");
+  var c = require('c');
 });
 ```
 

src/content/api/module-variables.md

@@ -33,7 +33,7 @@ Indicates whether or not [Hot Module Replacement](/concepts/hot-module-replaceme
 The ID of the current module.
 
 ``` javascript
-module.id === require.resolve("./file.js");
+module.id === require.resolve('./file.js');
 ```
 
 

src/content/api/node.md

@@ -23,13 +23,13 @@ npm install --save-dev webpack
 Then require the webpack module in your Node.js script:
 
 ``` js
-const webpack = require("webpack");
+const webpack = require('webpack');
 ```
 
 Or if you prefer ES2015:
 
 ``` js
-import webpack from "webpack";
+import webpack from 'webpack';
 ```
 
 
@@ -150,7 +150,7 @@ The `watch` method returns a `Watching` instance that exposes
 
 ``` js
 watching.close(() => {
-  console.log("Watching Ended.");
+  console.log('Watching Ended.');
 });
 ```
 
@@ -332,16 +332,16 @@ replace the default `outputFileSystem` with
 instead of to disk:
 
 ``` js
-const MemoryFS = require("memory-fs");
-const webpack = require("webpack");
+const MemoryFS = require('memory-fs');
+const webpack = require('webpack');
 
 const fs = new MemoryFS();
 const compiler = webpack({ /* options*/ });
 
 compiler.outputFileSystem = fs;
 compiler.run((err, stats) => {
   // Read the output later:
-  const content = fs.readFileSync("...");
+  const content = fs.readFileSync('...');
 });
 ```
 

src/content/concepts/module-resolution.md

@@ -29,9 +29,9 @@ Using `enhanced-resolve`, webpack can resolve three kinds of file paths:
 ### Absolute paths
 
 ```js
-import "/home/me/file";
+import '/home/me/file';
 
-import "C:\\Users\\me\\file";
+import 'C:\\Users\\me\\file';
 ```
 
 Since we already have the absolute path to the file, no further resolution is required.
@@ -40,8 +40,8 @@ Since we already have the absolute path to the file, no further resolution is re
 ### Relative paths
 
 ```js
-import "../src/file1";
-import "./file2";
+import '../src/file1';
+import './file2';
 ```
 
 In this case, the directory of the resource file where the `import` or `require` occurs is taken to be the context directory. The relative path specified in the `import/require` is joined to this context path to produce the absolute path to the module.
@@ -50,8 +50,8 @@ In this case, the directory of the resource file where the `import` or `require`
 ### Module paths
 
 ```js
-import "module";
-import "module/lib/file";
+import 'module';
+import 'module/lib/file';
 ```
 
 Modules are searched for inside all directories specified in [`resolve.modules`](/configuration/resolve/#resolve-modules).

src/content/concepts/plugins.md

@@ -6,6 +6,7 @@ contributors:
   - jhnns
   - rouzbeh84
   - johnstew
+  - byzyk
 ---
 
 **Plugins** are the [backbone](https://github.com/webpack/tapable) of webpack. webpack itself is built on the **same plugin system** that you use in your webpack configuration!
@@ -25,7 +26,7 @@ const pluginName = 'ConsoleLogOnBuildWebpackPlugin';
 class ConsoleLogOnBuildWebpackPlugin {
   apply(compiler) {
     compiler.hooks.run.tap(pluginName, compilation => {
-      console.log("The webpack build process is starting!!!");
+      console.log('The webpack build process is starting!!!');
     });
   }
 }

src/content/configuration/dev-server.md

@@ -27,7 +27,7 @@ This set of options is picked up by [webpack-dev-server](https://github.com/webp
 module.exports = {
   //...
   devServer: {
-    contentBase: path.join(__dirname, "dist"),
+    contentBase: path.join(__dirname, 'dist'),
     compress: true,
     port: 9000
   }
@@ -164,7 +164,7 @@ You can prevent all these messages from showing, by using this option:
 module.exports = {
   //...
   devServer: {
-    clientLogLevel: "none"
+    clientLogLevel: 'none'
   }
 };
 ```
@@ -223,7 +223,7 @@ By default it will use your current working directory to serve content, but you
 module.exports = {
   //...
   devServer: {
-    contentBase: path.join(__dirname, "public")
+    contentBase: path.join(__dirname, 'public')
   }
 };
 ```
@@ -236,7 +236,7 @@ It is also possible to serve from multiple directories:
 module.exports = {
   //...
   devServer: {
-    contentBase: [path.join(__dirname, "public"), path.join(__dirname, "assets")]
+    contentBase: [path.join(__dirname, 'public'), path.join(__dirname, 'assets')]
   }
 };
 ```
@@ -295,7 +295,7 @@ module.exports = {
   //...
   devServer: {
     lazy: true,
-    filename: "bundle.js"
+    filename: 'bundle.js'
   }
 };
 ```
@@ -316,7 +316,7 @@ module.exports = {
   //...
   devServer: {
     headers: {
-      "X-Custom-Foo": "bar"
+      'X-Custom-Foo': 'bar'
     }
   }
 };
@@ -387,7 +387,7 @@ Specify a host to use. By default this is `localhost`. If you want your server t
 module.exports = {
   //...
   devServer: {
-    host: "0.0.0.0"
+    host: '0.0.0.0'
   }
 };
 ```
@@ -461,9 +461,9 @@ module.exports = {
   //...
   devServer: {
     https: {
-      key: fs.readFileSync("/path/to/server.key"),
-      cert: fs.readFileSync("/path/to/server.crt"),
-      ca: fs.readFileSync("/path/to/ca.pem"),
+      key: fs.readFileSync('/path/to/server.key'),
+      cert: fs.readFileSync('/path/to/server.crt'),
+      ca: fs.readFileSync('/path/to/ca.pem'),
     }
   }
 };
@@ -739,7 +739,7 @@ module.exports = {
   //...
   devServer: {
     proxy: {
-      "/api": "http://localhost:3000"
+      '/api': 'http://localhost:3000'
     }
   }
 };
@@ -754,9 +754,9 @@ module.exports = {
   //...
   devServer: {
     proxy: {
-      "/api": {
-        target: "http://localhost:3000",
-        pathRewrite: {"^/api" : ""}
+      '/api': {
+        target: 'http://localhost:3000',
+        pathRewrite: {'^/api' : ''}
       }
     }
   }
@@ -770,8 +770,8 @@ module.exports = {
   //...
   devServer: {
     proxy: {
-      "/api": {
-        target: "https://other-server.example.com",
+      '/api': {
+        target: 'https://other-server.example.com',
         secure: false
       }
     }
@@ -790,12 +790,12 @@ module.exports = {
   //...
   devServer: {
     proxy: {
-      "/api": {
-        target: "http://localhost:3000",
+      '/api': {
+        target: 'http://localhost:3000',
         bypass: function(req, res, proxyOptions) {
-          if (req.headers.accept.indexOf("html") !== -1) {
-            console.log("Skipping proxy for browser request.");
-            return "/index.html";
+          if (req.headers.accept.indexOf('html') !== -1) {
+            console.log('Skipping proxy for browser request.');
+            return '/index.html';
           }
         }
       }
@@ -811,8 +811,8 @@ module.exports = {
   //...
   devServer: {
     proxy: [{
-      context: ["/auth", "/api"],
-      target: "http://localhost:3000",
+      context: ['/auth', '/api'],
+      target: 'http://localhost:3000',
     }]
   }
 };
@@ -858,7 +858,7 @@ For example, the dev-server is proxied by nginx, and available on `myapp.test`:
 module.exports = {
   //...
   devServer: {
-    public: "myapp.test:80"
+    public: 'myapp.test:80'
   }
 };
 ```
@@ -884,7 +884,7 @@ The `publicPath` can be changed so the bundle is put in a directory:
 module.exports = {
   //...
   devServer: {
-    publicPath: "/assets/"
+    publicPath: '/assets/'
   }
 };
 ```
@@ -899,7 +899,7 @@ It is also possible to use a full URL. This is necessary for Hot Module Replacem
 module.exports = {
   //...
   devServer: {
-    publicPath: "http://localhost:8080/assets/"
+    publicPath: 'http://localhost:8080/assets/'
   }
 };
 ```
@@ -1006,7 +1006,7 @@ To show only errors in your bundle:
 module.exports = {
   //...
   devServer: {
-    stats: "errors-only"
+    stats: 'errors-only'
   }
 };
 ```

src/content/configuration/entry-context.md

@@ -20,7 +20,7 @@ The base directory, an **absolute path**, for resolving entry points and loaders
 ``` js
 module.exports = {
   //...
-  context: path.resolve(__dirname, "app")
+  context: path.resolve(__dirname, 'app')
 };
 ```
 
@@ -43,9 +43,9 @@ Simple rule: one entry point per HTML page. SPA: one entry point, MPA: multiple
 module.exports = {
   //...
   entry: {
-    home: "./home.js",
-    about: "./about.js",
-    contact: "./contact.js"
+    home: './home.js',
+    about: './about.js',
+    contact: './contact.js'
   }
 };
 ```