From c3aa183461244f3681961976aebff934aa2b0a9b Mon Sep 17 00:00:00 2001
From: Jordan Harband <ljharb@gmail.com>
Date: Wed, 25 Jan 2017 09:27:37 -0800
Subject: [PATCH] Set theme jekyll-theme-cayman and migrate Page Generator
 content

---
 _config.yml |    8 +
 index.html  | 3476 ---------------------------------------------------
 index.md    | 2976 +++++++++++++++++++++++++++++++++++++++++++
 params.json |    7 -
 4 files changed, 2984 insertions(+), 3483 deletions(-)
 create mode 100644 _config.yml
 delete mode 100644 index.html
 create mode 100644 index.md
 delete mode 100644 params.json
diff --git a/_config.yml b/_config.yml
new file mode 100644
index 00000000..764888e1
--- /dev/null
+++ b/_config.yml
@@ -0,0 +1,8 @@
+title: Airbnb JavaScript Style Guide
+description: A mostly reasonable approach to JavaScript
+google_analytics: 
+show_downloads: true
+theme: jekyll-theme-cayman
+
+gems:
+  - jekyll-mentions
diff --git a/index.html b/index.html
deleted file mode 100644
index 277b0b7b..00000000
--- a/index.html
+++ /dev/null
@@ -1,3476 +0,0 @@
-<!DOCTYPE html>
-<html lang="en-us">
-  <head>
-    <meta charset="UTF-8">
-    <title>Airbnb JavaScript Style Guide by airbnb</title>
-    <meta name="viewport" content="width=device-width, initial-scale=1">
-    <link rel="stylesheet" type="text/css" href="stylesheets/normalize.css" media="screen">
-    <link href='https://fonts.googleapis.com/css?family=Open+Sans:400,700' rel='stylesheet' type='text/css'>
-    <link rel="stylesheet" type="text/css" href="stylesheets/stylesheet.css" media="screen">
-    <link rel="stylesheet" type="text/css" href="stylesheets/github-light.css" media="screen">
-  </head>
-  <body>
-    <section class="page-header">
-      <h1 class="project-name">Airbnb JavaScript Style Guide</h1>
-      <h2 class="project-tagline">A mostly reasonable approach to JavaScript</h2>
-      <a href="https://github.com/airbnb/javascript" class="btn">View on GitHub</a>
-      <a href="https://github.com/airbnb/javascript/zipball/master" class="btn">Download .zip</a>
-      <a href="https://github.com/airbnb/javascript/tarball/master" class="btn">Download .tar.gz</a>
-    </section>
-
-    <section class="main-content">
-      <h1>
-<a id="airbnb-javascript-style-guide-" class="anchor" href="#airbnb-javascript-style-guide-" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Airbnb JavaScript Style Guide() {</h1>
-
-<p><em>A mostly reasonable approach to JavaScript</em></p>
-
-<p><a href="https://www.npmjs.com/package/eslint-config-airbnb"><img src="https://img.shields.io/npm/dm/eslint-config-airbnb.svg" alt="Downloads"></a>
-<a href="https://www.npmjs.com/package/eslint-config-airbnb-base"><img src="https://img.shields.io/npm/dm/eslint-config-airbnb-base.svg" alt="Downloads"></a>
-<a href="https://gitter.im/airbnb/javascript?utm_source=badge&amp;utm_medium=badge&amp;utm_campaign=pr-badge"><img src="https://badges.gitter.im/Join%20Chat.svg" alt="Gitter"></a></p>
-
-<p>Other Style Guides</p>
-
-<ul>
-<li><a href="es5/">ES5</a></li>
-<li><a href="react/">React</a></li>
-<li><a href="https://github.com/airbnb/css">CSS &amp; Sass</a></li>
-<li><a href="https://github.com/airbnb/ruby">Ruby</a></li>
-</ul>
-
-<h2>
-<a id="table-of-contents" class="anchor" href="#table-of-contents" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Table of Contents</h2>
-
-<ol>
-<li><a href="#types">Types</a></li>
-<li><a href="#references">References</a></li>
-<li><a href="#objects">Objects</a></li>
-<li><a href="#arrays">Arrays</a></li>
-<li><a href="#destructuring">Destructuring</a></li>
-<li><a href="#strings">Strings</a></li>
-<li><a href="#functions">Functions</a></li>
-<li><a href="#arrow-functions">Arrow Functions</a></li>
-<li><a href="#classes--constructors">Classes &amp; Constructors</a></li>
-<li><a href="#modules">Modules</a></li>
-<li><a href="#iterators-and-generators">Iterators and Generators</a></li>
-<li><a href="#properties">Properties</a></li>
-<li><a href="#variables">Variables</a></li>
-<li><a href="#hoisting">Hoisting</a></li>
-<li><a href="#comparison-operators--equality">Comparison Operators &amp; Equality</a></li>
-<li><a href="#blocks">Blocks</a></li>
-<li><a href="#comments">Comments</a></li>
-<li><a href="#whitespace">Whitespace</a></li>
-<li><a href="#commas">Commas</a></li>
-<li><a href="#semicolons">Semicolons</a></li>
-<li><a href="#type-casting--coercion">Type Casting &amp; Coercion</a></li>
-<li><a href="#naming-conventions">Naming Conventions</a></li>
-<li><a href="#accessors">Accessors</a></li>
-<li><a href="#events">Events</a></li>
-<li><a href="#jquery">jQuery</a></li>
-<li><a href="#ecmascript-5-compatibility">ECMAScript 5 Compatibility</a></li>
-<li><a href="#ecmascript-6-styles">ECMAScript 6 Styles</a></li>
-<li><a href="#testing">Testing</a></li>
-<li><a href="#performance">Performance</a></li>
-<li><a href="#resources">Resources</a></li>
-<li><a href="#in-the-wild">In the Wild</a></li>
-<li><a href="#translation">Translation</a></li>
-<li><a href="#the-javascript-style-guide-guide">The JavaScript Style Guide Guide</a></li>
-<li><a href="#chat-with-us-about-javascript">Chat With Us About JavaScript</a></li>
-<li><a href="#contributors">Contributors</a></li>
-<li><a href="#license">License</a></li>
-</ol>
-
-<h2>
-<a id="types" class="anchor" href="#types" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Types</h2>
-
-<p><a name="types--primitives"></a><a name="1.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#types--primitives">1.1</a> <strong>Primitives</strong>: When you access a primitive type you work directly on its value.</p>
-
-<ul>
-<li><code>string</code></li>
-<li><code>number</code></li>
-<li><code>boolean</code></li>
-<li><code>null</code></li>
-<li><code>undefined</code></li>
-</ul>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-<span class="pl-k">let</span> bar <span class="pl-k">=</span> foo;
-
-bar <span class="pl-k">=</span> <span class="pl-c1">9</span>;
-
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo, bar); <span class="pl-c">// =&gt; 1, 9</span></pre></div>
-
-<p><a name="types--complex"></a><a name="1.2"></a></p>
-</li>
-<li>
-<p><a href="#types--complex">1.2</a>  <strong>Complex</strong>: When you access a complex type you work on a reference to its value.</p>
-
-<ul>
-<li><code>object</code></li>
-<li><code>array</code></li>
-<li><code>function</code></li>
-</ul>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> [<span class="pl-c1">1</span>, <span class="pl-c1">2</span>];
-<span class="pl-k">const</span> <span class="pl-c1">bar</span> <span class="pl-k">=</span> foo;
-
-bar[<span class="pl-c1">0</span>] <span class="pl-k">=</span> <span class="pl-c1">9</span>;
-
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo[<span class="pl-c1">0</span>], bar[<span class="pl-c1">0</span>]); <span class="pl-c">// =&gt; 9, 9</span></pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="references" class="anchor" href="#references" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>References</h2>
-
-<p><a name="references--prefer-const"></a><a name="2.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#references--prefer-const">2.1</a> Use <code>const</code> for all of your references; avoid using <code>var</code>. eslint: <a href="http://eslint.org/docs/rules/prefer-const.html"><code>prefer-const</code></a>, <a href="http://eslint.org/docs/rules/no-const-assign.html"><code>no-const-assign</code></a></p>
-
-<blockquote>
-<p>Why? This ensures that you can't reassign your references, which can lead to bugs and difficult to comprehend code.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">var</span> a <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-<span class="pl-k">var</span> b <span class="pl-k">=</span> <span class="pl-c1">2</span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">a</span> <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-<span class="pl-k">const</span> <span class="pl-c1">b</span> <span class="pl-k">=</span> <span class="pl-c1">2</span>;</pre></div>
-
-<p><a name="references--disallow-var"></a><a name="2.2"></a></p>
-</li>
-<li>
-<p><a href="#references--disallow-var">2.2</a> If you must reassign references, use <code>let</code> instead of <code>var</code>. eslint: <a href="http://eslint.org/docs/rules/no-var.html"><code>no-var</code></a> jscs: <a href="http://jscs.info/rule/disallowVar"><code>disallowVar</code></a></p>
-
-<blockquote>
-<p>Why? <code>let</code> is block-scoped rather than function-scoped like <code>var</code>.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">var</span> count <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-<span class="pl-k">if</span> (<span class="pl-c1">true</span>) {
-  count <span class="pl-k">+=</span> <span class="pl-c1">1</span>;
-}
-
-<span class="pl-c">// good, use the let.</span>
-<span class="pl-k">let</span> count <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-<span class="pl-k">if</span> (<span class="pl-c1">true</span>) {
-  count <span class="pl-k">+=</span> <span class="pl-c1">1</span>;
-}</pre></div>
-
-<p><a name="references--block-scope"></a><a name="2.3"></a></p>
-</li>
-<li>
-<p><a href="#references--block-scope">2.3</a> Note that both <code>let</code> and <code>const</code> are block-scoped.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// const and let only exist in the blocks they are defined in.</span>
-{
-  <span class="pl-k">let</span> a <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-  <span class="pl-k">const</span> <span class="pl-c1">b</span> <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-}
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(a); <span class="pl-c">// ReferenceError</span>
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(b); <span class="pl-c">// ReferenceError</span></pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="objects" class="anchor" href="#objects" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Objects</h2>
-
-<p><a name="objects--no-new"></a><a name="3.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#objects--no-new">3.1</a> Use the literal syntax for object creation. eslint: <a href="http://eslint.org/docs/rules/no-new-object.html"><code>no-new-object</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">item</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">Object</span>();
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">item</span> <span class="pl-k">=</span> {};</pre></div>
-
-<p><a name="objects--reserved-words"></a><a name="3.2"></a></p>
-</li>
-<li>
-<p><a href="#objects--reserved-words">3.2</a> If your code will be executed in browsers in script context, don't use <a href="http://es5.github.io/#x7.6.1">reserved words</a> as keys. It won't work in IE8. <a href="https://github.com/airbnb/javascript/issues/61">More info</a>. It’s OK to use them in ES6 modules and server-side code. jscs: <a href="http://jscs.info/rule/disallowIdentifierNames"><code>disallowIdentifierNames</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">superman</span> <span class="pl-k">=</span> {
-  default<span class="pl-k">:</span> { clark<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>kent<span class="pl-pds">'</span></span> },
-  private<span class="pl-k">:</span> <span class="pl-c1">true</span>,
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">superman</span> <span class="pl-k">=</span> {
-  defaults<span class="pl-k">:</span> { clark<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>kent<span class="pl-pds">'</span></span> },
-  hidden<span class="pl-k">:</span> <span class="pl-c1">true</span>,
-};</pre></div>
-
-<p><a name="objects--reserved-words-2"></a><a name="3.3"></a></p>
-</li>
-<li>
-<p><a href="#objects--reserved-words-2">3.3</a> Use readable synonyms in place of reserved words. jscs: <a href="http://jscs.info/rule/disallowIdentifierNames"><code>disallowIdentifierNames</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">superman</span> <span class="pl-k">=</span> {
-  class<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>alien<span class="pl-pds">'</span></span>,
-};
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">superman</span> <span class="pl-k">=</span> {
-  klass<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>alien<span class="pl-pds">'</span></span>,
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">superman</span> <span class="pl-k">=</span> {
-  type<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>alien<span class="pl-pds">'</span></span>,
-};</pre></div>
-
-<p><a name="es6-computed-properties"></a><a name="3.4"></a></p>
-</li>
-<li>
-<p><a href="#es6-computed-properties">3.4</a> Use computed property names when creating objects with dynamic property names.</p>
-
-<blockquote>
-<p>Why? They allow you to define all the properties of an object in one place.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre>
-<span class="pl-k">function</span> <span class="pl-en">getKey</span>(<span class="pl-smi">k</span>) {
-  <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">`</span>a key named <span class="pl-s1"><span class="pl-pse">${</span>k<span class="pl-pse">}</span></span><span class="pl-pds">`</span></span>;
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">obj</span> <span class="pl-k">=</span> {
-  id<span class="pl-k">:</span> <span class="pl-c1">5</span>,
-  name<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>San Francisco<span class="pl-pds">'</span></span>,
-};
-obj[<span class="pl-en">getKey</span>(<span class="pl-s"><span class="pl-pds">'</span>enabled<span class="pl-pds">'</span></span>)] <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">obj</span> <span class="pl-k">=</span> {
-  id<span class="pl-k">:</span> <span class="pl-c1">5</span>,
-  name<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>San Francisco<span class="pl-pds">'</span></span>,
-  [<span class="pl-en">getKey</span>(<span class="pl-s"><span class="pl-pds">'</span>enabled<span class="pl-pds">'</span></span>)]<span class="pl-k">:</span> <span class="pl-c1">true</span>,
-};</pre></div>
-
-<p><a name="es6-object-shorthand"></a><a name="3.5"></a></p>
-</li>
-<li>
-<p><a href="#es6-object-shorthand">3.5</a> Use object method shorthand. eslint: <a href="http://eslint.org/docs/rules/object-shorthand.html"><code>object-shorthand</code></a> jscs: <a href="http://jscs.info/rule/requireEnhancedObjectLiterals"><code>requireEnhancedObjectLiterals</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">atom</span> <span class="pl-k">=</span> {
-  value<span class="pl-k">:</span> <span class="pl-c1">1</span>,
-
-  <span class="pl-en">addValue</span><span class="pl-k">:</span> <span class="pl-k">function</span> (<span class="pl-smi">value</span>) {
-    <span class="pl-k">return</span> <span class="pl-smi">atom</span>.<span class="pl-c1">value</span> <span class="pl-k">+</span> value;
-  },
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">atom</span> <span class="pl-k">=</span> {
-  value<span class="pl-k">:</span> <span class="pl-c1">1</span>,
-
-  <span class="pl-en">addValue</span>(<span class="pl-smi">value</span>) {
-    <span class="pl-k">return</span> <span class="pl-smi">atom</span>.<span class="pl-c1">value</span> <span class="pl-k">+</span> value;
-  },
-};</pre></div>
-
-<p><a name="es6-object-concise"></a><a name="3.6"></a></p>
-</li>
-<li>
-<p><a href="#es6-object-concise">3.6</a> Use property value shorthand. eslint: <a href="http://eslint.org/docs/rules/object-shorthand.html"><code>object-shorthand</code></a> jscs: <a href="http://jscs.info/rule/requireEnhancedObjectLiterals"><code>requireEnhancedObjectLiterals</code></a></p>
-
-<blockquote>
-<p>Why? It is shorter to write and descriptive.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">lukeSkywalker</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Luke Skywalker<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">obj</span> <span class="pl-k">=</span> {
-  lukeSkywalker<span class="pl-k">:</span> lukeSkywalker,
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">obj</span> <span class="pl-k">=</span> {
-  lukeSkywalker,
-};</pre></div>
-
-<p><a name="objects--grouped-shorthand"></a><a name="3.7"></a></p>
-</li>
-<li>
-<p><a href="#objects--grouped-shorthand">3.7</a> Group your shorthand properties at the beginning of your object declaration.</p>
-
-<blockquote>
-<p>Why? It's easier to tell which properties are using the shorthand.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">anakinSkywalker</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Anakin Skywalker<span class="pl-pds">'</span></span>;
-<span class="pl-k">const</span> <span class="pl-c1">lukeSkywalker</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Luke Skywalker<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">obj</span> <span class="pl-k">=</span> {
-  episodeOne<span class="pl-k">:</span> <span class="pl-c1">1</span>,
-  twoJediWalkIntoACantina<span class="pl-k">:</span> <span class="pl-c1">2</span>,
-  lukeSkywalker,
-  episodeThree<span class="pl-k">:</span> <span class="pl-c1">3</span>,
-  mayTheFourth<span class="pl-k">:</span> <span class="pl-c1">4</span>,
-  anakinSkywalker,
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">obj</span> <span class="pl-k">=</span> {
-  lukeSkywalker,
-  anakinSkywalker,
-  episodeOne<span class="pl-k">:</span> <span class="pl-c1">1</span>,
-  twoJediWalkIntoACantina<span class="pl-k">:</span> <span class="pl-c1">2</span>,
-  episodeThree<span class="pl-k">:</span> <span class="pl-c1">3</span>,
-  mayTheFourth<span class="pl-k">:</span> <span class="pl-c1">4</span>,
-};</pre></div>
-
-<p><a name="objects--quoted-props"></a><a name="3.8"></a></p>
-</li>
-<li>
-<p><a href="#objects--quoted-props">3.8</a> Only quote properties that are invalid identifiers. eslint: <a href="http://eslint.org/docs/rules/quote-props.html"><code>quote-props</code></a> jscs: <a href="http://jscs.info/rule/disallowQuotedKeysInObjects"><code>disallowQuotedKeysInObjects</code></a></p>
-
-<blockquote>
-<p>Why? In general we consider it subjectively easier to read. It improves syntax highlighting, and is also more easily optimized by many JS engines.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">bad</span> <span class="pl-k">=</span> {
-  <span class="pl-s"><span class="pl-pds">'</span>foo<span class="pl-pds">'</span></span><span class="pl-k">:</span> <span class="pl-c1">3</span>,
-  <span class="pl-s"><span class="pl-pds">'</span>bar<span class="pl-pds">'</span></span><span class="pl-k">:</span> <span class="pl-c1">4</span>,
-  <span class="pl-s"><span class="pl-pds">'</span>data-blah<span class="pl-pds">'</span></span><span class="pl-k">:</span> <span class="pl-c1">5</span>,
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">good</span> <span class="pl-k">=</span> {
-  foo<span class="pl-k">:</span> <span class="pl-c1">3</span>,
-  bar<span class="pl-k">:</span> <span class="pl-c1">4</span>,
-  <span class="pl-s"><span class="pl-pds">'</span>data-blah<span class="pl-pds">'</span></span><span class="pl-k">:</span> <span class="pl-c1">5</span>,
-};</pre></div>
-
-<p><a name="objects--prototype-builtins"></a></p>
-</li>
-<li>
-<p><a href="#objects--prototype-builtins">3.9</a> Do not call <code>Object.prototype</code> methods directly, such as <code>hasOwnProperty</code>, <code>propertyIsEnumerable</code>, and <code>isPrototypeOf</code>.</p>
-
-<blockquote>
-<p>Why? These methods may be shadowed by properties on the object in question - consider <code>{ hasOwnProperty: false }</code> - or, the object may be a null object (<code>Object.create(null)</code>).</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-smi">object</span>.<span class="pl-en">hasOwnProperty</span>(key));
-
-<span class="pl-c">// good</span>
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-c1">Object</span>.<span class="pl-c1">prototype</span>.<span class="pl-smi">hasOwnProperty</span>.<span class="pl-c1">call</span>(object, key));
-
-<span class="pl-c">// best</span>
-<span class="pl-k">const</span> <span class="pl-c1">has</span> <span class="pl-k">=</span> <span class="pl-c1">Object</span>.<span class="pl-c1">prototype</span>.<span class="pl-smi">hasOwnProperty</span>; <span class="pl-c">// cache the lookup once, in module scope.</span>
-<span class="pl-c">/* or */</span>
-<span class="pl-k">const</span> <span class="pl-c1">has</span> <span class="pl-k">=</span> <span class="pl-c1">require</span>(<span class="pl-s"><span class="pl-pds">'</span>has<span class="pl-pds">'</span></span>);
-…
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-smi">has</span>.<span class="pl-c1">call</span>(object, key));</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="arrays" class="anchor" href="#arrays" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Arrays</h2>
-
-<p><a name="arrays--literals"></a><a name="4.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#arrays--literals">4.1</a> Use the literal syntax for array creation. eslint: <a href="http://eslint.org/docs/rules/no-array-constructor.html"><code>no-array-constructor</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">items</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">Array</span>();
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">items</span> <span class="pl-k">=</span> [];</pre></div>
-
-<p><a name="arrays--push"></a><a name="4.2"></a></p>
-</li>
-<li>
-<p><a href="#arrays--push">4.2</a> Use <a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/push">Array#push</a> instead of direct assignment to add items to an array.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">someStack</span> <span class="pl-k">=</span> [];
-
-<span class="pl-c">// bad</span>
-someStack[<span class="pl-smi">someStack</span>.<span class="pl-c1">length</span>] <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>abracadabra<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-smi">someStack</span>.<span class="pl-c1">push</span>(<span class="pl-s"><span class="pl-pds">'</span>abracadabra<span class="pl-pds">'</span></span>);</pre></div>
-
-<p><a name="es6-array-spreads"></a><a name="4.3"></a></p>
-</li>
-<li>
-<p><a href="#es6-array-spreads">4.3</a> Use array spreads <code>...</code> to copy arrays.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">len</span> <span class="pl-k">=</span> <span class="pl-smi">items</span>.<span class="pl-c1">length</span>;
-<span class="pl-k">const</span> <span class="pl-c1">itemsCopy</span> <span class="pl-k">=</span> [];
-<span class="pl-k">let</span> i;
-
-<span class="pl-k">for</span> (i <span class="pl-k">=</span> <span class="pl-c1">0</span>; i <span class="pl-k">&lt;</span> len; i<span class="pl-k">++</span>) {
-  itemsCopy[i] <span class="pl-k">=</span> items[i];
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">itemsCopy</span> <span class="pl-k">=</span> [<span class="pl-k">...</span>items];</pre></div>
-
-<p><a name="arrays--from"></a><a name="4.4"></a></p>
-</li>
-<li>
-<p><a href="#arrays--from">4.4</a> To convert an array-like object to an array, use <a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/from">Array.from</a>.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-c1">document</span>.<span class="pl-c1">querySelectorAll</span>(<span class="pl-s"><span class="pl-pds">'</span>.foo<span class="pl-pds">'</span></span>);
-<span class="pl-k">const</span> <span class="pl-c1">nodes</span> <span class="pl-k">=</span> <span class="pl-c1">Array</span>.<span class="pl-en">from</span>(foo);</pre></div>
-
-<p><a name="arrays--callback-return"></a><a name="4.5"></a></p>
-</li>
-<li>
-<p><a href="#arrays--callback-return">4.5</a> Use return statements in array method callbacks. It's ok to omit the return if the function body consists of a single statement following <a href="#8.2">8.2</a>. eslint: <a href="http://eslint.org/docs/rules/array-callback-return"><code>array-callback-return</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>((<span class="pl-smi">x</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">y</span> <span class="pl-k">=</span> x <span class="pl-k">+</span> <span class="pl-c1">1</span>;
-  <span class="pl-k">return</span> x <span class="pl-k">*</span> y;
-});
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-smi">x</span> <span class="pl-k">=&gt;</span> x <span class="pl-k">+</span> <span class="pl-c1">1</span>);
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">flat</span> <span class="pl-k">=</span> {};
-[[<span class="pl-c1">0</span>, <span class="pl-c1">1</span>], [<span class="pl-c1">2</span>, <span class="pl-c1">3</span>], [<span class="pl-c1">4</span>, <span class="pl-c1">5</span>]].<span class="pl-en">reduce</span>((<span class="pl-smi">memo</span>, <span class="pl-smi">item</span>, <span class="pl-smi">index</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">flatten</span> <span class="pl-k">=</span> <span class="pl-smi">memo</span>.<span class="pl-c1">concat</span>(item);
-  flat[index] <span class="pl-k">=</span> flatten;
-});
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">flat</span> <span class="pl-k">=</span> {};
-[[<span class="pl-c1">0</span>, <span class="pl-c1">1</span>], [<span class="pl-c1">2</span>, <span class="pl-c1">3</span>], [<span class="pl-c1">4</span>, <span class="pl-c1">5</span>]].<span class="pl-en">reduce</span>((<span class="pl-smi">memo</span>, <span class="pl-smi">item</span>, <span class="pl-smi">index</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">flatten</span> <span class="pl-k">=</span> <span class="pl-smi">memo</span>.<span class="pl-c1">concat</span>(item);
-  flat[index] <span class="pl-k">=</span> flatten;
-  <span class="pl-k">return</span> flatten;
-});
-
-<span class="pl-c">// bad</span>
-<span class="pl-smi">inbox</span>.<span class="pl-en">filter</span>((<span class="pl-smi">msg</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> { <span class="pl-c1">subject</span>, <span class="pl-c1">author</span> } <span class="pl-k">=</span> msg;
-  <span class="pl-k">if</span> (subject <span class="pl-k">===</span> <span class="pl-s"><span class="pl-pds">'</span>Mockingbird<span class="pl-pds">'</span></span>) {
-    <span class="pl-k">return</span> author <span class="pl-k">===</span> <span class="pl-s"><span class="pl-pds">'</span>Harper Lee<span class="pl-pds">'</span></span>;
-  } <span class="pl-k">else</span> {
-    <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-  }
-});
-
-<span class="pl-c">// good</span>
-<span class="pl-smi">inbox</span>.<span class="pl-en">filter</span>((<span class="pl-smi">msg</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> { <span class="pl-c1">subject</span>, <span class="pl-c1">author</span> } <span class="pl-k">=</span> msg;
-  <span class="pl-k">if</span> (subject <span class="pl-k">===</span> <span class="pl-s"><span class="pl-pds">'</span>Mockingbird<span class="pl-pds">'</span></span>) {
-    <span class="pl-k">return</span> author <span class="pl-k">===</span> <span class="pl-s"><span class="pl-pds">'</span>Harper Lee<span class="pl-pds">'</span></span>;
-  }
-
-  <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-});</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="destructuring" class="anchor" href="#destructuring" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Destructuring</h2>
-
-<p><a name="destructuring--object"></a><a name="5.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#destructuring--object">5.1</a> Use object destructuring when accessing and using multiple properties of an object. jscs: <a href="http://jscs.info/rule/requireObjectDestructuring"><code>requireObjectDestructuring</code></a></p>
-
-<blockquote>
-<p>Why? Destructuring saves you from creating temporary references for those properties.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">getFullName</span>(<span class="pl-smi">user</span>) {
-  <span class="pl-k">const</span> <span class="pl-c1">firstName</span> <span class="pl-k">=</span> <span class="pl-smi">user</span>.<span class="pl-smi">firstName</span>;
-  <span class="pl-k">const</span> <span class="pl-c1">lastName</span> <span class="pl-k">=</span> <span class="pl-smi">user</span>.<span class="pl-smi">lastName</span>;
-
-  <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">`</span><span class="pl-s1"><span class="pl-pse">${</span>firstName<span class="pl-pse">}</span></span> <span class="pl-s1"><span class="pl-pse">${</span>lastName<span class="pl-pse">}</span></span><span class="pl-pds">`</span></span>;
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">getFullName</span>(<span class="pl-smi">user</span>) {
-  <span class="pl-k">const</span> { <span class="pl-c1">firstName</span>, <span class="pl-c1">lastName</span> } <span class="pl-k">=</span> user;
-  <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">`</span><span class="pl-s1"><span class="pl-pse">${</span>firstName<span class="pl-pse">}</span></span> <span class="pl-s1"><span class="pl-pse">${</span>lastName<span class="pl-pse">}</span></span><span class="pl-pds">`</span></span>;
-}
-
-<span class="pl-c">// best</span>
-<span class="pl-k">function</span> <span class="pl-en">getFullName</span>({ firstName, lastName }) {
-  <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">`</span><span class="pl-s1"><span class="pl-pse">${</span>firstName<span class="pl-pse">}</span></span> <span class="pl-s1"><span class="pl-pse">${</span>lastName<span class="pl-pse">}</span></span><span class="pl-pds">`</span></span>;
-}</pre></div>
-
-<p><a name="destructuring--array"></a><a name="5.2"></a></p>
-</li>
-<li>
-<p><a href="#destructuring--array">5.2</a> Use array destructuring. jscs: <a href="http://jscs.info/rule/requireArrayDestructuring"><code>requireArrayDestructuring</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">arr</span> <span class="pl-k">=</span> [<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>, <span class="pl-c1">4</span>];
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">first</span> <span class="pl-k">=</span> arr[<span class="pl-c1">0</span>];
-<span class="pl-k">const</span> <span class="pl-c1">second</span> <span class="pl-k">=</span> arr[<span class="pl-c1">1</span>];
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> [<span class="pl-c1">first</span>, <span class="pl-c1">second</span>] <span class="pl-k">=</span> arr;</pre></div>
-
-<p><a name="destructuring--object-over-array"></a><a name="5.3"></a></p>
-</li>
-<li>
-<p><a href="#destructuring--object-over-array">5.3</a> Use object destructuring for multiple return values, not array destructuring. jscs: <a href="http://jscs.info/rule/disallowArrayDestructuringReturn"><code>disallowArrayDestructuringReturn</code></a></p>
-
-<blockquote>
-<p>Why? You can add new properties over time or change the order of things without breaking call sites.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">processInput</span>(<span class="pl-smi">input</span>) {
-  <span class="pl-c">// then a miracle occurs</span>
-  <span class="pl-k">return</span> [left, right, top, bottom];
-}
-
-<span class="pl-c">// the caller needs to think about the order of return data</span>
-<span class="pl-k">const</span> [<span class="pl-c1">left</span>, <span class="pl-c1">__</span>, <span class="pl-c1">top</span>] <span class="pl-k">=</span> <span class="pl-en">processInput</span>(input);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">processInput</span>(<span class="pl-smi">input</span>) {
-  <span class="pl-c">// then a miracle occurs</span>
-  <span class="pl-k">return</span> { left, right, top, bottom };
-}
-
-<span class="pl-c">// the caller selects only the data they need</span>
-<span class="pl-k">const</span> { <span class="pl-c1">left</span>, <span class="pl-c1">top</span> } <span class="pl-k">=</span> <span class="pl-en">processInput</span>(input);</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="strings" class="anchor" href="#strings" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Strings</h2>
-
-<p><a name="strings--quotes"></a><a name="6.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#strings--quotes">6.1</a> Use single quotes <code>''</code> for strings. eslint: <a href="http://eslint.org/docs/rules/quotes.html"><code>quotes</code></a> jscs: <a href="http://jscs.info/rule/validateQuoteMarks"><code>validateQuoteMarks</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">"</span>Capt. Janeway<span class="pl-pds">"</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Capt. Janeway<span class="pl-pds">'</span></span>;</pre></div>
-
-<p><a name="strings--line-length"></a><a name="6.2"></a></p>
-</li>
-<li>
-<p><a href="#strings--line-length">6.2</a> Strings that cause the line to go over 100 characters should be written across multiple lines using string concatenation.</p>
-
-<p><a name="strings--concat-perf"></a><a name="6.3"></a></p>
-</li>
-<li>
-<p><a href="#strings--concat-perf">6.3</a> Note: If overused, long strings with concatenation could impact performance. <a href="http://jsperf.com/ya-string-concat">jsPerf</a> &amp; <a href="https://github.com/airbnb/javascript/issues/40">Discussion</a>.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">errorMessage</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>This is a super long error that was thrown because of Batman. When you stop to think about how Batman had anything to do with this, you would get nowhere fast.<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">errorMessage</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>This is a super long error that was thrown because \</span>
-<span class="pl-s">of Batman. When you stop to think about how Batman had anything to do \</span>
-<span class="pl-s">with this, you would get nowhere \</span>
-<span class="pl-s">fast.<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">errorMessage</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>This is a super long error that was thrown because <span class="pl-pds">'</span></span> <span class="pl-k">+</span>
-  <span class="pl-s"><span class="pl-pds">'</span>of Batman. When you stop to think about how Batman had anything to do <span class="pl-pds">'</span></span> <span class="pl-k">+</span>
-  <span class="pl-s"><span class="pl-pds">'</span>with this, you would get nowhere fast.<span class="pl-pds">'</span></span>;</pre></div>
-
-<p><a name="es6-template-literals"></a><a name="6.4"></a></p>
-</li>
-<li>
-<p><a href="#es6-template-literals">6.4</a> When programmatically building up strings, use template strings instead of concatenation. eslint: <a href="http://eslint.org/docs/rules/prefer-template.html"><code>prefer-template</code></a> <a href="http://eslint.org/docs/rules/template-curly-spacing"><code>template-curly-spacing</code></a> jscs: <a href="http://jscs.info/rule/requireTemplateStrings"><code>requireTemplateStrings</code></a></p>
-
-<blockquote>
-<p>Why? Template strings give you a readable, concise syntax with proper newlines and string interpolation features.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">sayHi</span>(<span class="pl-smi">name</span>) {
-  <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">'</span>How are you, <span class="pl-pds">'</span></span> <span class="pl-k">+</span> name <span class="pl-k">+</span> <span class="pl-s"><span class="pl-pds">'</span>?<span class="pl-pds">'</span></span>;
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">sayHi</span>(<span class="pl-smi">name</span>) {
-  <span class="pl-k">return</span> [<span class="pl-s"><span class="pl-pds">'</span>How are you, <span class="pl-pds">'</span></span>, name, <span class="pl-s"><span class="pl-pds">'</span>?<span class="pl-pds">'</span></span>].<span class="pl-c1">join</span>();
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">sayHi</span>(<span class="pl-smi">name</span>) {
-  <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">`</span>How are you, <span class="pl-s1"><span class="pl-pse">${</span> name <span class="pl-pse">}</span></span>?<span class="pl-pds">`</span></span>;
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">sayHi</span>(<span class="pl-smi">name</span>) {
-  <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">`</span>How are you, <span class="pl-s1"><span class="pl-pse">${</span>name<span class="pl-pse">}</span></span>?<span class="pl-pds">`</span></span>;
-}</pre></div>
-
-<p><a name="strings--eval"></a><a name="6.5"></a></p>
-</li>
-<li>
-<p><a href="#strings--eval">6.5</a> Never use <code>eval()</code> on a string, it opens too many vulnerabilities.</p>
-
-<p><a name="strings--escaping"></a></p>
-</li>
-<li>
-<p><a href="#strings--escaping">6.6</a> Do not unnecessarily escape characters in strings. eslint: <a href="http://eslint.org/docs/rules/no-useless-escape"><code>no-useless-escape</code></a></p>
-
-<blockquote>
-<p>Why? Backslashes harm readability, thus they should only be present when necessary.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span><span class="pl-cce">\'</span>this<span class="pl-cce">\'</span> <span class="pl-cce">\i\s</span> <span class="pl-cce">\"</span>quoted<span class="pl-cce">\"</span><span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span><span class="pl-cce">\'</span>this<span class="pl-cce">\'</span> is "quoted"<span class="pl-pds">'</span></span>;
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">`</span>'this' is "quoted"<span class="pl-pds">`</span></span>;</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="functions" class="anchor" href="#functions" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Functions</h2>
-
-<p><a name="functions--declarations"></a><a name="7.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#functions--declarations">7.1</a> Use function declarations instead of function expressions. jscs: <a href="http://jscs.info/rule/requireFunctionDeclarations"><code>requireFunctionDeclarations</code></a></p>
-
-<blockquote>
-<p>Why? Function declarations are named, so they're easier to identify in call stacks. Also, the whole body of a function declaration is hoisted, whereas only the reference of a function expression is hoisted. This rule makes it possible to always use <a href="#arrow-functions">Arrow Functions</a> in place of function expressions.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-k">function</span> () {
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">foo</span>() {
-}</pre></div>
-
-<p><a name="functions--iife"></a><a name="7.2"></a></p>
-</li>
-<li>
-<p><a href="#functions--iife">7.2</a> Wrap immediately invoked function expressions in parentheses. eslint: <a href="http://eslint.org/docs/rules/wrap-iife.html"><code>wrap-iife</code></a> jscs: <a href="http://jscs.info/rule/requireParenthesesAroundIIFE"><code>requireParenthesesAroundIIFE</code></a></p>
-
-<blockquote>
-<p>Why? An immediately invoked function expression is a single unit - wrapping both it, and its invocation parens, in parens, cleanly expresses this. Note that in a world with modules everywhere, you almost never need an IIFE.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// immediately-invoked function expression (IIFE)</span>
-(<span class="pl-k">function</span> () {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>Welcome to the Internet. Please follow me.<span class="pl-pds">'</span></span>);
-}());</pre></div>
-
-<p><a name="functions--in-blocks"></a><a name="7.3"></a></p>
-</li>
-<li>
-<p><a href="#functions--in-blocks">7.3</a> Never declare a function in a non-function block (if, while, etc). Assign the function to a variable instead. Browsers will allow you to do it, but they all interpret it differently, which is bad news bears. eslint: <a href="http://eslint.org/docs/rules/no-loop-func.html"><code>no-loop-func</code></a></p>
-
-<p><a name="functions--note-on-blocks"></a><a name="7.4"></a></p>
-</li>
-<li>
-<p><a href="#functions--note-on-blocks">7.4</a> <strong>Note:</strong> ECMA-262 defines a <code>block</code> as a list of statements. A function declaration is not a statement. <a href="http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf#page=97">Read ECMA-262's note on this issue</a>.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">if</span> (currentUser) {
-  <span class="pl-k">function</span> <span class="pl-en">test</span>() {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>Nope.<span class="pl-pds">'</span></span>);
-  }
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">let</span> test;
-<span class="pl-k">if</span> (currentUser) {
-  <span class="pl-en">test</span> <span class="pl-k">=</span> () <span class="pl-k">=&gt;</span> {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>Yup.<span class="pl-pds">'</span></span>);
-  };
-}</pre></div>
-
-<p><a name="functions--arguments-shadow"></a><a name="7.5"></a></p>
-</li>
-<li>
-<p><a href="#functions--arguments-shadow">7.5</a> Never name a parameter <code>arguments</code>. This will take precedence over the <code>arguments</code> object that is given to every function scope.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">nope</span>(<span class="pl-smi">name</span>, <span class="pl-smi">options</span>, <span class="pl-v">arguments</span>) {
-  <span class="pl-c">// ...stuff...</span>
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">yup</span>(<span class="pl-smi">name</span>, <span class="pl-smi">options</span>, <span class="pl-smi">args</span>) {
-  <span class="pl-c">// ...stuff...</span>
-}</pre></div>
-
-<p><a name="es6-rest"></a><a name="7.6"></a></p>
-</li>
-<li>
-<p><a href="#es6-rest">7.6</a> Never use <code>arguments</code>, opt to use rest syntax <code>...</code> instead. eslint: <a href="http://eslint.org/docs/rules/prefer-rest-params"><code>prefer-rest-params</code></a></p>
-
-<blockquote>
-<p>Why? <code>...</code> is explicit about which arguments you want pulled. Plus, rest arguments are a real Array, and not merely Array-like like <code>arguments</code>.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">concatenateAll</span>() {
-  <span class="pl-k">const</span> <span class="pl-c1">args</span> <span class="pl-k">=</span> <span class="pl-c1">Array</span>.<span class="pl-c1">prototype</span>.<span class="pl-smi">slice</span>.<span class="pl-c1">call</span>(<span class="pl-v">arguments</span>);
-  <span class="pl-k">return</span> <span class="pl-smi">args</span>.<span class="pl-c1">join</span>(<span class="pl-s"><span class="pl-pds">'</span><span class="pl-pds">'</span></span>);
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">concatenateAll</span>(<span class="pl-k">...</span><span class="pl-v">args</span>) {
-  <span class="pl-k">return</span> <span class="pl-smi">args</span>.<span class="pl-c1">join</span>(<span class="pl-s"><span class="pl-pds">'</span><span class="pl-pds">'</span></span>);
-}</pre></div>
-
-<p><a name="es6-default-parameters"></a><a name="7.7"></a></p>
-</li>
-<li>
-<p><a href="#es6-default-parameters">7.7</a> Use default parameter syntax rather than mutating function arguments.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// really bad</span>
-<span class="pl-k">function</span> <span class="pl-en">handleThings</span>(<span class="pl-smi">opts</span>) {
-  <span class="pl-c">// No! We shouldn't mutate function arguments.</span>
-  <span class="pl-c">// Double bad: if opts is falsy it'll be set to an object which may</span>
-  <span class="pl-c">// be what you want but it can introduce subtle bugs.</span>
-  opts <span class="pl-k">=</span> opts <span class="pl-k">||</span> {};
-  <span class="pl-c">// ...</span>
-}
-
-<span class="pl-c">// still bad</span>
-<span class="pl-k">function</span> <span class="pl-en">handleThings</span>(<span class="pl-smi">opts</span>) {
-  <span class="pl-k">if</span> (opts <span class="pl-k">===</span> <span class="pl-k">void</span> <span class="pl-c1">0</span>) {
-    opts <span class="pl-k">=</span> {};
-  }
-  <span class="pl-c">// ...</span>
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">handleThings</span>(<span class="pl-smi">opts</span> <span class="pl-k">=</span> {}) {
-  <span class="pl-c">// ...</span>
-}</pre></div>
-
-<p><a name="functions--default-side-effects"></a><a name="7.8"></a></p>
-</li>
-<li>
-<p><a href="#functions--default-side-effects">7.8</a> Avoid side effects with default parameters.</p>
-
-<blockquote>
-<p>Why? They are confusing to reason about.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">var</span> b <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-<span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">count</span>(<span class="pl-smi">a</span> <span class="pl-k">=</span> <span class="pl-smi">b</span><span class="pl-k">++</span>) {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(a);
-}
-<span class="pl-en">count</span>();  <span class="pl-c">// 1</span>
-<span class="pl-en">count</span>();  <span class="pl-c">// 2</span>
-<span class="pl-en">count</span>(<span class="pl-c1">3</span>); <span class="pl-c">// 3</span>
-<span class="pl-en">count</span>();  <span class="pl-c">// 3</span></pre></div>
-
-<p><a name="functions--defaults-last"></a><a name="7.9"></a></p>
-</li>
-<li>
-<p><a href="#functions--defaults-last">7.9</a> Always put default parameters last.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">handleThings</span>(<span class="pl-smi">opts</span> <span class="pl-k">=</span> {}, <span class="pl-smi">name</span>) {
-  <span class="pl-c">// ...</span>
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">handleThings</span>(<span class="pl-smi">name</span>, <span class="pl-smi">opts</span> <span class="pl-k">=</span> {}) {
-  <span class="pl-c">// ...</span>
-}</pre></div>
-
-<p><a name="functions--constructor"></a><a name="7.10"></a></p>
-</li>
-<li>
-<p><a href="#functions--constructor">7.10</a> Never use the Function constructor to create a new function.</p>
-
-<blockquote>
-<p>Why? Creating a function in this way evaluates a string similarly to eval(), which opens vulnerabilities.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">var</span> add <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">Function</span>(<span class="pl-s"><span class="pl-pds">'</span>a<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>b<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>return a + b<span class="pl-pds">'</span></span>);
-
-<span class="pl-c">// still bad</span>
-<span class="pl-k">var</span> subtract <span class="pl-k">=</span> <span class="pl-c1">Function</span>(<span class="pl-s"><span class="pl-pds">'</span>a<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>b<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>return a - b<span class="pl-pds">'</span></span>);</pre></div>
-
-<p><a name="functions--signature-spacing"></a><a name="7.11"></a></p>
-</li>
-<li>
-<p><a href="#functions--signature-spacing">7.11</a> Spacing in a function signature.</p>
-
-<blockquote>
-<p>Why? Consistency is good, and you shouldn’t have to add or remove a space when adding or removing a name.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">f</span> <span class="pl-k">=</span> <span class="pl-k">function</span>(){};
-<span class="pl-k">const</span> <span class="pl-c1">g</span> <span class="pl-k">=</span> <span class="pl-k">function</span> (){};
-<span class="pl-k">const</span> <span class="pl-c1">h</span> <span class="pl-k">=</span> <span class="pl-k">function</span>() {};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">x</span> <span class="pl-k">=</span> <span class="pl-k">function</span> () {};
-<span class="pl-k">const</span> <span class="pl-c1">y</span> <span class="pl-k">=</span> <span class="pl-k">function</span> <span class="pl-en">a</span>() {};</pre></div>
-
-<p><a name="functions--mutate-params"></a><a name="7.12"></a></p>
-</li>
-<li>
-<p><a href="#functions--mutate-params">7.12</a> Never mutate parameters. eslint: <a href="http://eslint.org/docs/rules/no-param-reassign.html"><code>no-param-reassign</code></a></p>
-
-<blockquote>
-<p>Why? Manipulating objects passed in as parameters can cause unwanted variable side effects in the original caller.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">f1</span>(<span class="pl-smi">obj</span>) {
-  <span class="pl-smi">obj</span>.<span class="pl-smi">key</span> <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">f2</span>(<span class="pl-smi">obj</span>) {
-  <span class="pl-k">const</span> <span class="pl-c1">key</span> <span class="pl-k">=</span> <span class="pl-c1">Object</span>.<span class="pl-c1">prototype</span>.<span class="pl-smi">hasOwnProperty</span>.<span class="pl-c1">call</span>(obj, <span class="pl-s"><span class="pl-pds">'</span>key<span class="pl-pds">'</span></span>) <span class="pl-k">?</span> <span class="pl-smi">obj</span>.<span class="pl-smi">key</span> <span class="pl-k">:</span> <span class="pl-c1">1</span>;
-};</pre></div>
-
-<p><a name="functions--reassign-params"></a><a name="7.13"></a></p>
-</li>
-<li>
-<p><a href="#functions--reassign-params">7.13</a> Never reassign parameters. eslint: <a href="http://eslint.org/docs/rules/no-param-reassign.html"><code>no-param-reassign</code></a></p>
-
-<blockquote>
-<p>Why? Reassigning parameters can lead to unexpected behavior, especially when accessing the <code>arguments</code> object. It can also cause optimization issues, especially in V8.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">f1</span>(<span class="pl-smi">a</span>) {
-  a <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-}
-
-<span class="pl-k">function</span> <span class="pl-en">f2</span>(<span class="pl-smi">a</span>) {
-  <span class="pl-k">if</span> (<span class="pl-k">!</span>a) { a <span class="pl-k">=</span> <span class="pl-c1">1</span>; }
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">f3</span>(<span class="pl-smi">a</span>) {
-  <span class="pl-k">const</span> <span class="pl-c1">b</span> <span class="pl-k">=</span> a <span class="pl-k">||</span> <span class="pl-c1">1</span>;
-}
-
-<span class="pl-k">function</span> <span class="pl-en">f4</span>(<span class="pl-smi">a</span> <span class="pl-k">=</span> <span class="pl-c1">1</span>) {
-}</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="arrow-functions" class="anchor" href="#arrow-functions" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Arrow Functions</h2>
-
-<p><a name="arrows--use-them"></a><a name="8.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#arrows--use-them">8.1</a> When you must use function expressions (as when passing an anonymous function), use arrow function notation. eslint: <a href="http://eslint.org/docs/rules/prefer-arrow-callback.html"><code>prefer-arrow-callback</code></a>, <a href="http://eslint.org/docs/rules/arrow-spacing.html"><code>arrow-spacing</code></a> jscs: <a href="http://jscs.info/rule/requireArrowFunctions"><code>requireArrowFunctions</code></a></p>
-
-<blockquote>
-<p>Why? It creates a version of the function that executes in the context of <code>this</code>, which is usually what you want, and is a more concise syntax.</p>
-
-<p>Why not? If you have a fairly complicated function, you might move that logic out into its own function declaration.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-k">function</span> (<span class="pl-smi">x</span>) {
-  <span class="pl-k">const</span> <span class="pl-c1">y</span> <span class="pl-k">=</span> x <span class="pl-k">+</span> <span class="pl-c1">1</span>;
-  <span class="pl-k">return</span> x <span class="pl-k">*</span> y;
-});
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>((<span class="pl-smi">x</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">y</span> <span class="pl-k">=</span> x <span class="pl-k">+</span> <span class="pl-c1">1</span>;
-  <span class="pl-k">return</span> x <span class="pl-k">*</span> y;
-});</pre></div>
-
-<p><a name="arrows--implicit-return"></a><a name="8.2"></a></p>
-</li>
-<li>
-<p><a href="#arrows--implicit-return">8.2</a> If the function body consists of a single expression, omit the braces and use the implicit return. Otherwise, keep the braces and use a <code>return</code> statement. eslint: <a href="http://eslint.org/docs/rules/arrow-parens.html"><code>arrow-parens</code></a>, <a href="http://eslint.org/docs/rules/arrow-body-style.html"><code>arrow-body-style</code></a> jscs:  <a href="http://jscs.info/rule/disallowParenthesesAroundArrowParam"><code>disallowParenthesesAroundArrowParam</code></a>, <a href="http://jscs.info/rule/requireShorthandArrowFunctions"><code>requireShorthandArrowFunctions</code></a></p>
-
-<blockquote>
-<p>Why? Syntactic sugar. It reads well when multiple functions are chained together.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-smi">number</span> <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">nextNumber</span> <span class="pl-k">=</span> number <span class="pl-k">+</span> <span class="pl-c1">1</span>;
-  <span class="pl-s"><span class="pl-pds">`</span>A string containing the <span class="pl-s1"><span class="pl-pse">${</span>nextNumber<span class="pl-pse">}</span></span>.<span class="pl-pds">`</span></span>;
-});
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-smi">number</span> <span class="pl-k">=&gt;</span> <span class="pl-s"><span class="pl-pds">`</span>A string containing the <span class="pl-s1"><span class="pl-pse">${</span>number<span class="pl-pse">}</span></span>.<span class="pl-pds">`</span></span>);
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>((<span class="pl-smi">number</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">nextNumber</span> <span class="pl-k">=</span> number <span class="pl-k">+</span> <span class="pl-c1">1</span>;
-  <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">`</span>A string containing the <span class="pl-s1"><span class="pl-pse">${</span>nextNumber<span class="pl-pse">}</span></span>.<span class="pl-pds">`</span></span>;
-});
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>((<span class="pl-smi">number</span>, <span class="pl-smi">index</span>) <span class="pl-k">=&gt;</span> ({
-  index<span class="pl-k">:</span> number
-}));</pre></div>
-
-<p><a name="arrows--paren-wrap"></a><a name="8.3"></a></p>
-</li>
-<li>
-<p><a href="#arrows--paren-wrap">8.3</a> In case the expression spans over multiple lines, wrap it in parentheses for better readability.</p>
-
-<blockquote>
-<p>Why? It shows clearly where the function starts and ends.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-smi">number</span> <span class="pl-k">=&gt;</span> <span class="pl-s"><span class="pl-pds">'</span>As time went by, the string containing the <span class="pl-pds">'</span></span> <span class="pl-k">+</span>
-  <span class="pl-s"><span class="pl-pds">`</span><span class="pl-s1"><span class="pl-pse">${</span>number<span class="pl-pse">}</span></span> became much longer. So we needed to break it over multiple <span class="pl-pds">`</span></span> <span class="pl-k">+</span>
-  <span class="pl-s"><span class="pl-pds">'</span>lines.<span class="pl-pds">'</span></span>
-);
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-smi">number</span> <span class="pl-k">=&gt;</span> (
-  <span class="pl-s"><span class="pl-pds">`</span>As time went by, the string containing the <span class="pl-s1"><span class="pl-pse">${</span>number<span class="pl-pse">}</span></span> became much <span class="pl-pds">`</span></span> <span class="pl-k">+</span>
-  <span class="pl-s"><span class="pl-pds">'</span>longer. So we needed to break it over multiple lines.<span class="pl-pds">'</span></span>
-));</pre></div>
-
-<p><a name="arrows--one-arg-parens"></a><a name="8.4"></a></p>
-</li>
-<li>
-<p><a href="#arrows--one-arg-parens">8.4</a> If your function takes a single argument and doesn’t use braces, omit the parentheses. Otherwise, always include parentheses around arguments. eslint: <a href="http://eslint.org/docs/rules/arrow-parens.html"><code>arrow-parens</code></a> jscs:  <a href="http://jscs.info/rule/disallowParenthesesAroundArrowParam"><code>disallowParenthesesAroundArrowParam</code></a></p>
-
-<blockquote>
-<p>Why? Less visual clutter.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>((<span class="pl-smi">x</span>) <span class="pl-k">=&gt;</span> x <span class="pl-k">*</span> x);
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-smi">x</span> <span class="pl-k">=&gt;</span> x <span class="pl-k">*</span> x);
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-smi">number</span> <span class="pl-k">=&gt;</span> (
-  <span class="pl-s"><span class="pl-pds">`</span>A long string with the <span class="pl-s1"><span class="pl-pse">${</span>number<span class="pl-pse">}</span></span>. It’s so long that we’ve broken it <span class="pl-pds">`</span></span> <span class="pl-k">+</span>
-  <span class="pl-s"><span class="pl-pds">'</span>over multiple lines!<span class="pl-pds">'</span></span>
-));
-
-<span class="pl-c">// bad</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>(<span class="pl-smi">x</span> <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">y</span> <span class="pl-k">=</span> x <span class="pl-k">+</span> <span class="pl-c1">1</span>;
-  <span class="pl-k">return</span> x <span class="pl-k">*</span> y;
-});
-
-<span class="pl-c">// good</span>
-[<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>].<span class="pl-en">map</span>((<span class="pl-smi">x</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">y</span> <span class="pl-k">=</span> x <span class="pl-k">+</span> <span class="pl-c1">1</span>;
-  <span class="pl-k">return</span> x <span class="pl-k">*</span> y;
-});</pre></div>
-
-<p><a name="arrows--confusing"></a><a name="8.5"></a></p>
-</li>
-<li>
-<p><a href="#arrows--confusing">8.5</a> Avoid confusing arrow function syntax (<code>=&gt;</code>) with comparison operators (<code>&lt;=</code>, <code>&gt;=</code>). eslint: <a href="http://eslint.org/docs/rules/no-confusing-arrow"><code>no-confusing-arrow</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">itemHeight</span> <span class="pl-k">=</span> <span class="pl-smi">item</span> <span class="pl-k">=&gt;</span> <span class="pl-smi">item</span>.<span class="pl-c1">height</span> <span class="pl-k">&gt;</span> <span class="pl-c1">256</span> <span class="pl-k">?</span> <span class="pl-smi">item</span>.<span class="pl-smi">largeSize</span> <span class="pl-k">:</span> <span class="pl-smi">item</span>.<span class="pl-smi">smallSize</span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">itemHeight</span> <span class="pl-k">=</span> (<span class="pl-smi">item</span>) <span class="pl-k">=&gt;</span> <span class="pl-smi">item</span>.<span class="pl-c1">height</span> <span class="pl-k">&gt;</span> <span class="pl-c1">256</span> <span class="pl-k">?</span> <span class="pl-smi">item</span>.<span class="pl-smi">largeSize</span> <span class="pl-k">:</span> <span class="pl-smi">item</span>.<span class="pl-smi">smallSize</span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">itemHeight</span> <span class="pl-k">=</span> (<span class="pl-smi">item</span>) <span class="pl-k">=&gt;</span> { <span class="pl-k">return</span> <span class="pl-smi">item</span>.<span class="pl-c1">height</span> <span class="pl-k">&gt;</span> <span class="pl-c1">256</span> <span class="pl-k">?</span> <span class="pl-smi">item</span>.<span class="pl-smi">largeSize</span> <span class="pl-k">:</span> <span class="pl-smi">item</span>.<span class="pl-smi">smallSize</span>; };</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="classes--constructors" class="anchor" href="#classes--constructors" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Classes &amp; Constructors</h2>
-
-<p><a name="constructors--use-class"></a><a name="9.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#constructors--use-class">9.1</a> Always use <code>class</code>. Avoid manipulating <code>prototype</code> directly.</p>
-
-<blockquote>
-<p>Why? <code>class</code> syntax is more concise and easier to reason about.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">Queue</span>(<span class="pl-smi">contents</span> <span class="pl-k">=</span> []) {
-  <span class="pl-v">this</span>.<span class="pl-smi">queue</span> <span class="pl-k">=</span> [<span class="pl-k">...</span>contents];
-}
-<span class="pl-smi">Queue</span>.<span class="pl-c1">prototype</span>.<span class="pl-en">pop</span> <span class="pl-k">=</span> <span class="pl-k">function</span> () {
-  <span class="pl-k">const</span> <span class="pl-c1">value</span> <span class="pl-k">=</span> <span class="pl-v">this</span>.<span class="pl-smi">queue</span>[<span class="pl-c1">0</span>];
-  <span class="pl-v">this</span>.<span class="pl-smi">queue</span>.<span class="pl-c1">splice</span>(<span class="pl-c1">0</span>, <span class="pl-c1">1</span>);
-  <span class="pl-k">return</span> value;
-};
-
-
-<span class="pl-c">// good</span>
-<span class="pl-k">class</span> <span class="pl-en">Queue</span> {
-  <span class="pl-en">constructor</span>(<span class="pl-smi">contents</span> <span class="pl-k">=</span> []) {
-    <span class="pl-v">this</span>.<span class="pl-smi">queue</span> <span class="pl-k">=</span> [<span class="pl-k">...</span>contents];
-  }
-  <span class="pl-en">pop</span>() {
-    <span class="pl-k">const</span> <span class="pl-c1">value</span> <span class="pl-k">=</span> <span class="pl-v">this</span>.<span class="pl-smi">queue</span>[<span class="pl-c1">0</span>];
-    <span class="pl-v">this</span>.<span class="pl-smi">queue</span>.<span class="pl-c1">splice</span>(<span class="pl-c1">0</span>, <span class="pl-c1">1</span>);
-    <span class="pl-k">return</span> value;
-  }
-}</pre></div>
-
-<p><a name="constructors--extends"></a><a name="9.2"></a></p>
-</li>
-<li>
-<p><a href="#constructors--extends">9.2</a> Use <code>extends</code> for inheritance.</p>
-
-<blockquote>
-<p>Why? It is a built-in way to inherit prototype functionality without breaking <code>instanceof</code>.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">inherits</span> <span class="pl-k">=</span> <span class="pl-c1">require</span>(<span class="pl-s"><span class="pl-pds">'</span>inherits<span class="pl-pds">'</span></span>);
-<span class="pl-k">function</span> <span class="pl-en">PeekableQueue</span>(<span class="pl-smi">contents</span>) {
-  <span class="pl-smi">Queue</span>.<span class="pl-c1">apply</span>(<span class="pl-v">this</span>, contents);
-}
-<span class="pl-en">inherits</span>(PeekableQueue, Queue);
-<span class="pl-smi">PeekableQueue</span>.<span class="pl-c1">prototype</span>.<span class="pl-en">peek</span> <span class="pl-k">=</span> <span class="pl-k">function</span> () {
-  <span class="pl-k">return</span> <span class="pl-v">this</span>.<span class="pl-smi">_queue</span>[<span class="pl-c1">0</span>];
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">class</span> <span class="pl-en">PeekableQueue</span> <span class="pl-k">extends</span> <span class="pl-e">Queue</span> {
-  <span class="pl-en">peek</span>() {
-    <span class="pl-k">return</span> <span class="pl-v">this</span>.<span class="pl-smi">_queue</span>[<span class="pl-c1">0</span>];
-  }
-}</pre></div>
-
-<p><a name="constructors--chaining"></a><a name="9.3"></a></p>
-</li>
-<li>
-<p><a href="#constructors--chaining">9.3</a> Methods can return <code>this</code> to help with method chaining.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-smi">Jedi</span>.<span class="pl-c1">prototype</span>.<span class="pl-en">jump</span> <span class="pl-k">=</span> <span class="pl-k">function</span> () {
-  <span class="pl-v">this</span>.<span class="pl-smi">jumping</span> <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-  <span class="pl-k">return</span> <span class="pl-c1">true</span>;
-};
-
-<span class="pl-smi">Jedi</span>.<span class="pl-c1">prototype</span>.<span class="pl-en">setHeight</span> <span class="pl-k">=</span> <span class="pl-k">function</span> (<span class="pl-smi">height</span>) {
-  <span class="pl-v">this</span>.<span class="pl-c1">height</span> <span class="pl-k">=</span> height;
-};
-
-<span class="pl-k">const</span> <span class="pl-c1">luke</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">Jedi</span>();
-<span class="pl-smi">luke</span>.<span class="pl-en">jump</span>(); <span class="pl-c">// =&gt; true</span>
-<span class="pl-smi">luke</span>.<span class="pl-en">setHeight</span>(<span class="pl-c1">20</span>); <span class="pl-c">// =&gt; undefined</span>
-
-<span class="pl-c">// good</span>
-<span class="pl-k">class</span> <span class="pl-en">Jedi</span> {
-  <span class="pl-en">jump</span>() {
-    <span class="pl-v">this</span>.<span class="pl-smi">jumping</span> <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-    <span class="pl-k">return</span> <span class="pl-v">this</span>;
-  }
-
-  <span class="pl-en">setHeight</span>(<span class="pl-smi">height</span>) {
-    <span class="pl-v">this</span>.<span class="pl-c1">height</span> <span class="pl-k">=</span> height;
-    <span class="pl-k">return</span> <span class="pl-v">this</span>;
-  }
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">luke</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">Jedi</span>();
-
-<span class="pl-smi">luke</span>.<span class="pl-en">jump</span>()
-  .<span class="pl-en">setHeight</span>(<span class="pl-c1">20</span>);</pre></div>
-
-<p><a name="constructors--tostring"></a><a name="9.4"></a></p>
-</li>
-<li>
-<p><a href="#constructors--tostring">9.4</a> It's okay to write a custom toString() method, just make sure it works successfully and causes no side effects.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">class</span> <span class="pl-en">Jedi</span> {
-  <span class="pl-en">constructor</span>(<span class="pl-smi">options</span> <span class="pl-k">=</span> {}) {
-    <span class="pl-v">this</span>.<span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-smi">options</span>.<span class="pl-c1">name</span> <span class="pl-k">||</span> <span class="pl-s"><span class="pl-pds">'</span>no name<span class="pl-pds">'</span></span>;
-  }
-
-  <span class="pl-en">getName</span>() {
-    <span class="pl-k">return</span> <span class="pl-v">this</span>.<span class="pl-c1">name</span>;
-  }
-
-  <span class="pl-en">toString</span>() {
-    <span class="pl-k">return</span> <span class="pl-s"><span class="pl-pds">`</span>Jedi - <span class="pl-s1"><span class="pl-pse">${</span><span class="pl-v">this</span>.<span class="pl-en">getName</span>()<span class="pl-pse">}</span></span><span class="pl-pds">`</span></span>;
-  }
-}</pre></div>
-
-<p><a name="constructors--no-useless"></a><a name="9.5"></a></p>
-</li>
-<li>
-<p><a href="#constructors--no-useless">9.5</a> Classes have a default constructor if one is not specified. An empty constructor function or one that just delegates to a parent class is unnecessary. eslint: <a href="http://eslint.org/docs/rules/no-useless-constructor"><code>no-useless-constructor</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">class</span> <span class="pl-en">Jedi</span> {
-  <span class="pl-en">constructor</span>() {}
-
-  <span class="pl-en">getName</span>() {
-    <span class="pl-k">return</span> <span class="pl-v">this</span>.<span class="pl-c1">name</span>;
-  }
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">class</span> <span class="pl-en">Rey</span> <span class="pl-k">extends</span> <span class="pl-e">Jedi</span> {
-  <span class="pl-en">constructor</span>(<span class="pl-k">...</span><span class="pl-v">args</span>) {
-    <span class="pl-v">super</span>(<span class="pl-k">...</span>args);
-  }
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">class</span> <span class="pl-en">Rey</span> <span class="pl-k">extends</span> <span class="pl-e">Jedi</span> {
-  <span class="pl-en">constructor</span>(<span class="pl-k">...</span><span class="pl-v">args</span>) {
-    <span class="pl-v">super</span>(<span class="pl-k">...</span>args);
-    <span class="pl-v">this</span>.<span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Rey<span class="pl-pds">'</span></span>;
-  }
-}</pre></div>
-
-<p><a name="classes--no-duplicate-members"></a></p>
-</li>
-<li>
-<p><a href="#classes--no-duplicate-members">9.6</a> Avoid duplicate class members. eslint: <a href="http://eslint.org/docs/rules/no-dupe-class-members"><code>no-dupe-class-members</code></a></p>
-
-<blockquote>
-<p>Why? Duplicate class member declarations will silently prefer the last one - having duplicates is almost certainly a bug.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">class</span> <span class="pl-en">Foo</span> {
-  <span class="pl-en">bar</span>() { <span class="pl-k">return</span> <span class="pl-c1">1</span>; }
-  <span class="pl-en">bar</span>() { <span class="pl-k">return</span> <span class="pl-c1">2</span>; }
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">class</span> <span class="pl-en">Foo</span> {
-  <span class="pl-en">bar</span>() { <span class="pl-k">return</span> <span class="pl-c1">1</span>; }
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">class</span> <span class="pl-en">Foo</span> {
-  <span class="pl-en">bar</span>() { <span class="pl-k">return</span> <span class="pl-c1">2</span>; }
-}</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="modules" class="anchor" href="#modules" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Modules</h2>
-
-<p><a name="modules--use-them"></a><a name="10.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#modules--use-them">10.1</a> Always use modules (<code>import</code>/<code>export</code>) over a non-standard module system. You can always transpile to your preferred module system.</p>
-
-<blockquote>
-<p>Why? Modules are the future, let's start using the future now.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">AirbnbStyleGuide</span> <span class="pl-k">=</span> <span class="pl-c1">require</span>(<span class="pl-s"><span class="pl-pds">'</span>./AirbnbStyleGuide<span class="pl-pds">'</span></span>);
-<span class="pl-c1">module</span>.<span class="pl-smi">exports</span> <span class="pl-k">=</span> <span class="pl-smi">AirbnbStyleGuide</span>.<span class="pl-smi">es6</span>;
-
-<span class="pl-c">// ok</span>
-<span class="pl-k">import</span> <span class="pl-smi">AirbnbStyleGuide</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./AirbnbStyleGuide<span class="pl-pds">'</span></span>;
-<span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-smi">AirbnbStyleGuide</span>.<span class="pl-smi">es6</span>;
-
-<span class="pl-c">// best</span>
-<span class="pl-k">import</span> { <span class="pl-smi">es6</span> } <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./AirbnbStyleGuide<span class="pl-pds">'</span></span>;
-<span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-smi">es6</span>;</pre></div>
-
-<p><a name="modules--no-wildcard"></a><a name="10.2"></a></p>
-</li>
-<li>
-<p><a href="#modules--no-wildcard">10.2</a> Do not use wildcard imports.</p>
-
-<blockquote>
-<p>Why? This makes sure you have a single default export.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">import</span> <span class="pl-v">*</span> <span class="pl-k">as</span> <span class="pl-smi">AirbnbStyleGuide</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./AirbnbStyleGuide<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">import</span> <span class="pl-smi">AirbnbStyleGuide</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./AirbnbStyleGuide<span class="pl-pds">'</span></span>;</pre></div>
-
-<p><a name="modules--no-export-from-import"></a><a name="10.3"></a></p>
-</li>
-<li>
-<p><a href="#modules--no-export-from-import">10.3</a> And do not export directly from an import.</p>
-
-<blockquote>
-<p>Why? Although the one-liner is concise, having one clear way to import and one clear way to export makes things consistent.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-c">// filename es6.js</span>
-<span class="pl-k">export</span> { <span class="pl-smi">es6</span> <span class="pl-k">as</span> <span class="pl-v">default</span> } <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./airbnbStyleGuide<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-c">// filename es6.js</span>
-<span class="pl-k">import</span> { <span class="pl-smi">es6</span> } <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./AirbnbStyleGuide<span class="pl-pds">'</span></span>;
-<span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-smi">es6</span>;</pre></div>
-
-<p><a name="modules--no-duplicate-imports"></a></p>
-</li>
-<li>
-<p><a href="#modules--no-duplicate-imports">10.4</a> Only import from a path in one place.
-eslint: <a href="http://eslint.org/docs/rules/no-duplicate-imports"><code>no-duplicate-imports</code></a></p>
-
-<blockquote>
-<p>Why? Having multiple lines that import from the same path can make code harder to maintain.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre>  <span class="pl-c">// bad</span>
-  <span class="pl-k">import</span> <span class="pl-smi">foo</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>foo<span class="pl-pds">'</span></span>;
-  <span class="pl-c">// … some other imports … //</span>
-  <span class="pl-k">import</span> { <span class="pl-smi">named1</span>, <span class="pl-smi">named2</span> } <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>foo<span class="pl-pds">'</span></span>;
-
-  <span class="pl-c">// good</span>
-  <span class="pl-k">import</span> <span class="pl-smi">foo</span>, { <span class="pl-smi">named1</span>, <span class="pl-smi">named2</span> } <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>foo<span class="pl-pds">'</span></span>;
-
-  <span class="pl-c">// good</span>
-  <span class="pl-k">import</span> foo, {
-    <span class="pl-smi">named1</span>,
-    <span class="pl-smi">named2</span>,
-  } <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>foo<span class="pl-pds">'</span></span>;</pre></div>
-
-<p><a name="modules--no-mutable-exports"></a></p>
-</li>
-<li>
-<p><a href="#modules--no-mutable-exports">10.5</a> Do not export mutable bindings.
-eslint: <a href="https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-mutable-exports.md"><code>import/no-mutable-exports</code></a></p>
-
-<blockquote>
-<p>Why? Mutation should be avoided in general, but in particular when exporting mutable bindings. While this technique may be needed for some special cases, in general, only constant references should be exported.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre>  <span class="pl-c">// bad</span>
-  <span class="pl-k">let</span> foo <span class="pl-k">=</span> <span class="pl-c1">3</span>;
-  <span class="pl-k">export</span> { <span class="pl-smi">foo</span> }
-
-  <span class="pl-c">// good</span>
-  <span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-c1">3</span>;
-  <span class="pl-k">export</span> { <span class="pl-smi">foo</span> }</pre></div>
-
-<p><a name="modules--prefer-default-export"></a></p>
-</li>
-<li>
-<p><a href="#modules--prefer-default-export">10.6</a> In modules with a single export, prefer default export over named export.
-eslint: <a href="https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/prefer-default-export.md"><code>import/prefer-default-export</code></a></p>
-
-<div class="highlight highlight-source-js"><pre>  <span class="pl-c">// bad</span>
-  <span class="pl-k">export</span> <span class="pl-k">function</span> <span class="pl-en">foo</span>() {}
-
-  <span class="pl-c">// good</span>
-  <span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-k">function</span> <span class="pl-en">foo</span>() {}</pre></div>
-
-<p><a name="modules--imports-first"></a></p>
-</li>
-<li>
-<p><a href="#modules--imports-first">10.7</a> Put all <code>import</code>s above non-import statements.
-eslint: <a href="https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/imports-first.md"><code>import/imports-first</code></a></p>
-
-<blockquote>
-<p>Why? Since <code>import</code>s are hoisted, keeping them all at the top prevents surprising behavior.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre>  <span class="pl-c">// bad</span>
-  <span class="pl-k">import</span> <span class="pl-smi">foo</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>foo<span class="pl-pds">'</span></span>;
-  <span class="pl-smi">foo</span>.<span class="pl-en">init</span>();
-
-  <span class="pl-k">import</span> <span class="pl-smi">bar</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>bar<span class="pl-pds">'</span></span>;
-
-  <span class="pl-c">// good</span>
-  <span class="pl-k">import</span> <span class="pl-smi">foo</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>foo<span class="pl-pds">'</span></span>;
-  <span class="pl-k">import</span> <span class="pl-smi">bar</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>bar<span class="pl-pds">'</span></span>;
-
-  <span class="pl-smi">foo</span>.<span class="pl-en">init</span>();</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="iterators-and-generators" class="anchor" href="#iterators-and-generators" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Iterators and Generators</h2>
-
-<p><a name="iterators--nope"></a><a name="11.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#iterators--nope">11.1</a> Don't use iterators. Prefer JavaScript's higher-order functions like <code>map()</code> and <code>reduce()</code> instead of loops like <code>for-of</code>. eslint: <a href="http://eslint.org/docs/rules/no-iterator.html"><code>no-iterator</code></a></p>
-
-<blockquote>
-<p>Why? This enforces our immutable rule. Dealing with pure functions that return values is easier to reason about than side effects.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">numbers</span> <span class="pl-k">=</span> [<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>, <span class="pl-c1">4</span>, <span class="pl-c1">5</span>];
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">let</span> sum <span class="pl-k">=</span> <span class="pl-c1">0</span>;
-<span class="pl-k">for</span> (<span class="pl-k">let</span> num <span class="pl-k">of</span> numbers) {
-  sum <span class="pl-k">+=</span> num;
-}
-
-sum <span class="pl-k">===</span> <span class="pl-c1">15</span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">let</span> sum <span class="pl-k">=</span> <span class="pl-c1">0</span>;
-<span class="pl-smi">numbers</span>.<span class="pl-c1">forEach</span>(<span class="pl-smi">num</span> <span class="pl-k">=&gt;</span> sum <span class="pl-k">+=</span> num);
-sum <span class="pl-k">===</span> <span class="pl-c1">15</span>;
-
-<span class="pl-c">// best (use the functional force)</span>
-<span class="pl-k">const</span> <span class="pl-c1">sum</span> <span class="pl-k">=</span> <span class="pl-smi">numbers</span>.<span class="pl-en">reduce</span>((<span class="pl-smi">total</span>, <span class="pl-smi">num</span>) <span class="pl-k">=&gt;</span> total <span class="pl-k">+</span> num, <span class="pl-c1">0</span>);
-sum <span class="pl-k">===</span> <span class="pl-c1">15</span>;</pre></div>
-
-<p><a name="generators--nope"></a><a name="11.2"></a></p>
-</li>
-<li>
-<p><a href="#generators--nope">11.2</a> Don't use generators for now.</p>
-
-<blockquote>
-<p>Why? They don't transpile well to ES5.</p>
-</blockquote>
-
-<p><a name="generators--spacing"></a></p>
-</li>
-<li>
-<p><a href="#generators--spacing">11.3</a> If you must use generators, or if you disregard <a href="#generators--nope">our advice</a>, make sure their function signature is spaced properly. eslint: <a href="http://eslint.org/docs/rules/generator-star-spacing"><code>generator-star-spacing</code></a></p>
-
-<blockquote>
-<p>Why? <code>function</code> and <code>*</code> are part of the same conceptual keyword - <code>*</code> is not a modifier for <code>function</code>, <code>function*</code> is a unique construct, different from <code>function</code>.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-k">*</span> <span class="pl-en">foo</span>() {
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">bar</span> <span class="pl-k">=</span> <span class="pl-k">function</span> <span class="pl-k">*</span> () {
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">baz</span> <span class="pl-k">=</span> <span class="pl-k">function</span> <span class="pl-k">*</span>() {
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">quux</span> <span class="pl-k">=</span> <span class="pl-k">function</span><span class="pl-k">*</span>() {
-}
-
-<span class="pl-k">function</span><span class="pl-k">*</span><span class="pl-en">foo</span>() {
-}
-
-<span class="pl-k">function</span> <span class="pl-k">*</span><span class="pl-en">foo</span>() {
-}
-
-<span class="pl-c">// very bad</span>
-<span class="pl-k">function</span>
-*
-<span class="pl-en">foo</span>() {
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">wat</span> <span class="pl-k">=</span> <span class="pl-k">function</span>
-*
-() {
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span><span class="pl-k">*</span> <span class="pl-en">foo</span>() {
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-k">function</span><span class="pl-k">*</span> () {
-}</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="properties" class="anchor" href="#properties" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Properties</h2>
-
-<p><a name="properties--dot"></a><a name="12.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#properties--dot">12.1</a> Use dot notation when accessing properties. eslint: <a href="http://eslint.org/docs/rules/dot-notation.html"><code>dot-notation</code></a> jscs: <a href="http://jscs.info/rule/requireDotNotation"><code>requireDotNotation</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">luke</span> <span class="pl-k">=</span> {
-  jedi<span class="pl-k">:</span> <span class="pl-c1">true</span>,
-  age<span class="pl-k">:</span> <span class="pl-c1">28</span>,
-};
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">isJedi</span> <span class="pl-k">=</span> luke[<span class="pl-s"><span class="pl-pds">'</span>jedi<span class="pl-pds">'</span></span>];
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">isJedi</span> <span class="pl-k">=</span> <span class="pl-smi">luke</span>.<span class="pl-smi">jedi</span>;</pre></div>
-
-<p><a name="properties--bracket"></a><a name="12.2"></a></p>
-</li>
-<li>
-<p><a href="#properties--bracket">12.2</a> Use bracket notation <code>[]</code> when accessing properties with a variable.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">luke</span> <span class="pl-k">=</span> {
-  jedi<span class="pl-k">:</span> <span class="pl-c1">true</span>,
-  age<span class="pl-k">:</span> <span class="pl-c1">28</span>,
-};
-
-<span class="pl-k">function</span> <span class="pl-en">getProp</span>(<span class="pl-smi">prop</span>) {
-  <span class="pl-k">return</span> luke[prop];
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">isJedi</span> <span class="pl-k">=</span> <span class="pl-en">getProp</span>(<span class="pl-s"><span class="pl-pds">'</span>jedi<span class="pl-pds">'</span></span>);</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="variables" class="anchor" href="#variables" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Variables</h2>
-
-<p><a name="variables--const"></a><a name="13.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#variables--const">13.1</a> Always use <code>const</code> to declare variables. Not doing so will result in global variables. We want to avoid polluting the global namespace. Captain Planet warned us of that.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-superPower <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">SuperPower</span>();
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">superPower</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">SuperPower</span>();</pre></div>
-
-<p><a name="variables--one-const"></a><a name="13.2"></a></p>
-</li>
-<li>
-<p><a href="#variables--one-const">13.2</a> Use one <code>const</code> declaration per variable. eslint: <a href="http://eslint.org/docs/rules/one-var.html"><code>one-var</code></a> jscs: <a href="http://jscs.info/rule/disallowMultipleVarDecl"><code>disallowMultipleVarDecl</code></a></p>
-
-<blockquote>
-<p>Why? It's easier to add new variable declarations this way, and you never have to worry about swapping out a <code>;</code> for a <code>,</code> or introducing punctuation-only diffs. You can also step through each declaration with the debugger, instead of jumping through all of them at once.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">items</span> <span class="pl-k">=</span> <span class="pl-en">getItems</span>(),
-    goSportsTeam <span class="pl-k">=</span> <span class="pl-c1">true</span>,
-    dragonball <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>z<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-c">// (compare to above, and try to spot the mistake)</span>
-<span class="pl-k">const</span> <span class="pl-c1">items</span> <span class="pl-k">=</span> <span class="pl-en">getItems</span>(),
-    goSportsTeam <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-    dragonball <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>z<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">items</span> <span class="pl-k">=</span> <span class="pl-en">getItems</span>();
-<span class="pl-k">const</span> <span class="pl-c1">goSportsTeam</span> <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-<span class="pl-k">const</span> <span class="pl-c1">dragonball</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>z<span class="pl-pds">'</span></span>;</pre></div>
-
-<p><a name="variables--const-let-group"></a><a name="13.3"></a></p>
-</li>
-<li>
-<p><a href="#variables--const-let-group">13.3</a> Group all your <code>const</code>s and then group all your <code>let</code>s.</p>
-
-<blockquote>
-<p>Why? This is helpful when later on you might need to assign a variable depending on one of the previous assigned variables.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">let</span> i, len, dragonball,
-    items <span class="pl-k">=</span> <span class="pl-en">getItems</span>(),
-    goSportsTeam <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">let</span> i;
-<span class="pl-k">const</span> <span class="pl-c1">items</span> <span class="pl-k">=</span> <span class="pl-en">getItems</span>();
-<span class="pl-k">let</span> dragonball;
-<span class="pl-k">const</span> <span class="pl-c1">goSportsTeam</span> <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-<span class="pl-k">let</span> len;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">goSportsTeam</span> <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-<span class="pl-k">const</span> <span class="pl-c1">items</span> <span class="pl-k">=</span> <span class="pl-en">getItems</span>();
-<span class="pl-k">let</span> dragonball;
-<span class="pl-k">let</span> i;
-<span class="pl-k">let</span> length;</pre></div>
-
-<p><a name="variables--define-where-used"></a><a name="13.4"></a></p>
-</li>
-<li>
-<p><a href="#variables--define-where-used">13.4</a> Assign variables where you need them, but place them in a reasonable place.</p>
-
-<blockquote>
-<p>Why? <code>let</code> and <code>const</code> are block scoped and not function scoped.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad - unnecessary function call</span>
-<span class="pl-k">function</span> <span class="pl-en">checkName</span>(<span class="pl-smi">hasName</span>) {
-  <span class="pl-k">const</span> <span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-en">getName</span>();
-
-  <span class="pl-k">if</span> (hasName <span class="pl-k">===</span> <span class="pl-s"><span class="pl-pds">'</span>test<span class="pl-pds">'</span></span>) {
-    <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-  }
-
-  <span class="pl-k">if</span> (name <span class="pl-k">===</span> <span class="pl-s"><span class="pl-pds">'</span>test<span class="pl-pds">'</span></span>) {
-    <span class="pl-v">this</span>.<span class="pl-en">setName</span>(<span class="pl-s"><span class="pl-pds">'</span><span class="pl-pds">'</span></span>);
-    <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-  }
-
-  <span class="pl-k">return</span> name;
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">checkName</span>(<span class="pl-smi">hasName</span>) {
-  <span class="pl-k">if</span> (hasName <span class="pl-k">===</span> <span class="pl-s"><span class="pl-pds">'</span>test<span class="pl-pds">'</span></span>) {
-    <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-  }
-
-  <span class="pl-k">const</span> <span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-en">getName</span>();
-
-  <span class="pl-k">if</span> (name <span class="pl-k">===</span> <span class="pl-s"><span class="pl-pds">'</span>test<span class="pl-pds">'</span></span>) {
-    <span class="pl-v">this</span>.<span class="pl-en">setName</span>(<span class="pl-s"><span class="pl-pds">'</span><span class="pl-pds">'</span></span>);
-    <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-  }
-
-  <span class="pl-k">return</span> name;
-}</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="hoisting" class="anchor" href="#hoisting" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Hoisting</h2>
-
-<p><a name="hoisting--about"></a><a name="14.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#hoisting--about">14.1</a> <code>var</code> declarations get hoisted to the top of their scope, their assignment does not. <code>const</code> and <code>let</code> declarations are blessed with a new concept called <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let#Temporal_dead_zone_and_errors_with_let">Temporal Dead Zones (TDZ)</a>. It's important to know why <a href="http://es-discourse.com/t/why-typeof-is-no-longer-safe/15">typeof is no longer safe</a>.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// we know this wouldn't work (assuming there</span>
-<span class="pl-c">// is no notDefined global variable)</span>
-<span class="pl-k">function</span> <span class="pl-en">example</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(notDefined); <span class="pl-c">// =&gt; throws a ReferenceError</span>
-}
-
-<span class="pl-c">// creating a variable declaration after you</span>
-<span class="pl-c">// reference the variable will work due to</span>
-<span class="pl-c">// variable hoisting. Note: the assignment</span>
-<span class="pl-c">// value of `true` is not hoisted.</span>
-<span class="pl-k">function</span> <span class="pl-en">example</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(declaredButNotAssigned); <span class="pl-c">// =&gt; undefined</span>
-  <span class="pl-k">var</span> declaredButNotAssigned <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-}
-
-<span class="pl-c">// the interpreter is hoisting the variable</span>
-<span class="pl-c">// declaration to the top of the scope,</span>
-<span class="pl-c">// which means our example could be rewritten as:</span>
-<span class="pl-k">function</span> <span class="pl-en">example</span>() {
-  <span class="pl-k">let</span> declaredButNotAssigned;
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(declaredButNotAssigned); <span class="pl-c">// =&gt; undefined</span>
-  declaredButNotAssigned <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-}
-
-<span class="pl-c">// using const and let</span>
-<span class="pl-k">function</span> <span class="pl-en">example</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(declaredButNotAssigned); <span class="pl-c">// =&gt; throws a ReferenceError</span>
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-k">typeof</span> declaredButNotAssigned); <span class="pl-c">// =&gt; throws a ReferenceError</span>
-  <span class="pl-k">const</span> <span class="pl-c1">declaredButNotAssigned</span> <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-}</pre></div>
-
-<p><a name="hoisting--anon-expressions"></a><a name="14.2"></a></p>
-</li>
-<li>
-<p><a href="#hoisting--anon-expressions">14.2</a> Anonymous function expressions hoist their variable name, but not the function assignment.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">function</span> <span class="pl-en">example</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(anonymous); <span class="pl-c">// =&gt; undefined</span>
-
-  <span class="pl-en">anonymous</span>(); <span class="pl-c">// =&gt; TypeError anonymous is not a function</span>
-
-  <span class="pl-k">var</span> <span class="pl-en">anonymous</span> <span class="pl-k">=</span> <span class="pl-k">function</span> () {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>anonymous function expression<span class="pl-pds">'</span></span>);
-  };
-}</pre></div>
-
-<p><a name="hoisting--named-expresions"></a><a name="14.3"></a></p>
-</li>
-<li>
-<p><a href="#hoisting--named-expresions">14.3</a> Named function expressions hoist the variable name, not the function name or the function body.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">function</span> <span class="pl-en">example</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(named); <span class="pl-c">// =&gt; undefined</span>
-
-  <span class="pl-en">named</span>(); <span class="pl-c">// =&gt; TypeError named is not a function</span>
-
-  <span class="pl-en">superPower</span>(); <span class="pl-c">// =&gt; ReferenceError superPower is not defined</span>
-
-  <span class="pl-k">var</span> <span class="pl-en">named</span> <span class="pl-k">=</span> <span class="pl-k">function</span> <span class="pl-en">superPower</span>() {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>Flying<span class="pl-pds">'</span></span>);
-  };
-}
-
-<span class="pl-c">// the same is true when the function name</span>
-<span class="pl-c">// is the same as the variable name.</span>
-<span class="pl-k">function</span> <span class="pl-en">example</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(named); <span class="pl-c">// =&gt; undefined</span>
-
-  <span class="pl-en">named</span>(); <span class="pl-c">// =&gt; TypeError named is not a function</span>
-
-  <span class="pl-k">var</span> <span class="pl-en">named</span> <span class="pl-k">=</span> <span class="pl-k">function</span> <span class="pl-en">named</span>() {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>named<span class="pl-pds">'</span></span>);
-  }
-}</pre></div>
-
-<p><a name="hoisting--declarations"></a><a name="14.4"></a></p>
-</li>
-<li>
-<p><a href="#hoisting--declarations">14.4</a> Function declarations hoist their name and the function body.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">function</span> <span class="pl-en">example</span>() {
-  <span class="pl-en">superPower</span>(); <span class="pl-c">// =&gt; Flying</span>
-
-  <span class="pl-k">function</span> <span class="pl-en">superPower</span>() {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>Flying<span class="pl-pds">'</span></span>);
-  }
-}</pre></div>
-</li>
-<li><p>For more information refer to <a href="http://www.adequatelygood.com/2010/2/JavaScript-Scoping-and-Hoisting/">JavaScript Scoping &amp; Hoisting</a> by <a href="http://www.adequatelygood.com/">Ben Cherry</a>.</p></li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="comparison-operators--equality" class="anchor" href="#comparison-operators--equality" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Comparison Operators &amp; Equality</h2>
-
-<p><a name="comparison--eqeqeq"></a><a name="15.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#comparison--eqeqeq">15.1</a> Use <code>===</code> and <code>!==</code> over <code>==</code> and <code>!=</code>. eslint: <a href="http://eslint.org/docs/rules/eqeqeq.html"><code>eqeqeq</code></a></p>
-
-<p><a name="comparison--if"></a><a name="15.2"></a></p>
-</li>
-<li>
-<p><a href="#comparison--if">15.2</a> Conditional statements such as the <code>if</code> statement evaluate their expression using coercion with the <code>ToBoolean</code> abstract method and always follow these simple rules:</p>
-
-<ul>
-<li>
-<strong>Objects</strong> evaluate to <strong>true</strong>
-</li>
-<li>
-<strong>Undefined</strong> evaluates to <strong>false</strong>
-</li>
-<li>
-<strong>Null</strong> evaluates to <strong>false</strong>
-</li>
-<li>
-<strong>Booleans</strong> evaluate to <strong>the value of the boolean</strong>
-</li>
-<li>
-<strong>Numbers</strong> evaluate to <strong>false</strong> if <strong>+0, -0, or NaN</strong>, otherwise <strong>true</strong>
-</li>
-<li>
-<strong>Strings</strong> evaluate to <strong>false</strong> if an empty string <code>''</code>, otherwise <strong>true</strong>
-</li>
-</ul>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">if</span> ([<span class="pl-c1">0</span>] <span class="pl-k">&amp;&amp;</span> []) {
-  <span class="pl-c">// true</span>
-  <span class="pl-c">// an array (even an empty one) is an object, objects will evaluate to true</span>
-}</pre></div>
-
-<p><a name="comparison--shortcuts"></a><a name="15.3"></a></p>
-</li>
-<li>
-<p><a href="#comparison--shortcuts">15.3</a> Use shortcuts.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">if</span> (name <span class="pl-k">!==</span> <span class="pl-s"><span class="pl-pds">'</span><span class="pl-pds">'</span></span>) {
-  <span class="pl-c">// ...stuff...</span>
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (name) {
-  <span class="pl-c">// ...stuff...</span>
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">if</span> (<span class="pl-smi">collection</span>.<span class="pl-c1">length</span> <span class="pl-k">&gt;</span> <span class="pl-c1">0</span>) {
-  <span class="pl-c">// ...stuff...</span>
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (<span class="pl-smi">collection</span>.<span class="pl-c1">length</span>) {
-  <span class="pl-c">// ...stuff...</span>
-}</pre></div>
-
-<p><a name="comparison--moreinfo"></a><a name="15.4"></a></p>
-</li>
-<li>
-<p><a href="#comparison--moreinfo">15.4</a> For more information see <a href="http://javascriptweblog.wordpress.com/2011/02/07/truth-equality-and-javascript/#more-2108">Truth Equality and JavaScript</a> by Angus Croll.</p>
-
-<p><a name="comparison--switch-blocks"></a><a name="15.5"></a></p>
-</li>
-<li>
-<p><a href="#comparison--switch-blocks">15.5</a> Use braces to create blocks in <code>case</code> and <code>default</code> clauses that contain lexical declarations (e.g. <code>let</code>, <code>const</code>, <code>function</code>, and <code>class</code>).</p>
-
-<blockquote>
-<p>Why? Lexical declarations are visible in the entire <code>switch</code> block but only get initialized when assigned, which only happens when its <code>case</code> is reached. This causes problems when multiple <code>case</code> clauses attempt to define the same thing.</p>
-</blockquote>
-
-<p>eslint rules: <a href="http://eslint.org/docs/rules/no-case-declarations.html"><code>no-case-declarations</code></a>.</p>
-
-<div class="highlight highlight-source-js"><pre>  <span class="pl-c">// bad</span>
-  <span class="pl-k">switch</span> (foo) {
-    <span class="pl-k">case</span> <span class="pl-c1">1</span>:
-      <span class="pl-k">let</span> x <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-      <span class="pl-k">break</span>;
-    <span class="pl-k">case</span> <span class="pl-c1">2</span>:
-      <span class="pl-k">const</span> <span class="pl-c1">y</span> <span class="pl-k">=</span> <span class="pl-c1">2</span>;
-      <span class="pl-k">break</span>;
-    <span class="pl-k">case</span> <span class="pl-c1">3</span>:
-      <span class="pl-k">function</span> <span class="pl-en">f</span>() {}
-      <span class="pl-k">break</span>;
-    <span class="pl-k">default</span>:
-      <span class="pl-k">class</span> <span class="pl-en">C</span> {}
-  }
-
-  <span class="pl-c">// good</span>
-  <span class="pl-k">switch</span> (foo) {
-    <span class="pl-k">case</span> <span class="pl-c1">1</span>: {
-      <span class="pl-k">let</span> x <span class="pl-k">=</span> <span class="pl-c1">1</span>;
-      <span class="pl-k">break</span>;
-    }
-    <span class="pl-k">case</span> <span class="pl-c1">2</span>: {
-      <span class="pl-k">const</span> <span class="pl-c1">y</span> <span class="pl-k">=</span> <span class="pl-c1">2</span>;
-      <span class="pl-k">break</span>;
-    }
-    <span class="pl-k">case</span> <span class="pl-c1">3</span>: {
-      <span class="pl-k">function</span> <span class="pl-en">f</span>() {}
-      <span class="pl-k">break</span>;
-    }
-    <span class="pl-k">case</span> <span class="pl-c1">4</span>:
-      <span class="pl-en">bar</span>();
-      <span class="pl-k">break</span>;
-    <span class="pl-k">default</span>: {
-      <span class="pl-k">class</span> <span class="pl-en">C</span> {}
-    }
-  }</pre></div>
-
-<p><a name="comparison--nested-ternaries"></a><a name="15.6"></a></p>
-</li>
-<li>
-<p><a href="#comparison--nested-ternaries">15.6</a> Ternaries should not be nested and generally be single line expressions.</p>
-
-<p>eslint rules: <a href="http://eslint.org/docs/rules/no-nested-ternary.html"><code>no-nested-ternary</code></a>.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> maybe1 <span class="pl-k">&gt;</span> maybe2
-  <span class="pl-k">?</span> <span class="pl-s"><span class="pl-pds">"</span>bar<span class="pl-pds">"</span></span>
-  <span class="pl-k">:</span> value1 <span class="pl-k">&gt;</span> value2 <span class="pl-k">?</span> <span class="pl-s"><span class="pl-pds">"</span>baz<span class="pl-pds">"</span></span> <span class="pl-k">:</span> <span class="pl-c1">null</span>;
-
-<span class="pl-c">// better</span>
-<span class="pl-k">const</span> <span class="pl-c1">maybeNull</span> <span class="pl-k">=</span> value1 <span class="pl-k">&gt;</span> value2 <span class="pl-k">?</span> <span class="pl-s"><span class="pl-pds">'</span>baz<span class="pl-pds">'</span></span> <span class="pl-k">:</span> <span class="pl-c1">null</span>;
-
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> maybe1 <span class="pl-k">&gt;</span> maybe2
-  <span class="pl-k">?</span> <span class="pl-s"><span class="pl-pds">'</span>bar<span class="pl-pds">'</span></span>
-  <span class="pl-k">:</span> maybeNull;
-
-<span class="pl-c">// best</span>
-<span class="pl-k">const</span> <span class="pl-c1">maybeNull</span> <span class="pl-k">=</span> value1 <span class="pl-k">&gt;</span> value2 <span class="pl-k">?</span> <span class="pl-s"><span class="pl-pds">'</span>baz<span class="pl-pds">'</span></span> <span class="pl-k">:</span> <span class="pl-c1">null</span>;
-
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> maybe1 <span class="pl-k">&gt;</span> maybe2 <span class="pl-k">?</span> <span class="pl-s"><span class="pl-pds">'</span>bar<span class="pl-pds">'</span></span> <span class="pl-k">:</span> maybeNull;</pre></div>
-
-<p><a name="comparison--unneeded-ternary"></a><a name="15.7"></a></p>
-</li>
-<li>
-<p><a href="#comparison--unneeded-ternary">15.7</a> Avoid unneeded ternary statements.</p>
-
-<p>eslint rules: <a href="http://eslint.org/docs/rules/no-unneeded-ternary.html"><code>no-unneeded-ternary</code></a>.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> a <span class="pl-k">?</span> a <span class="pl-k">:</span> b;
-<span class="pl-k">const</span> <span class="pl-c1">bar</span> <span class="pl-k">=</span> c <span class="pl-k">?</span> <span class="pl-c1">true</span> <span class="pl-k">:</span> <span class="pl-c1">false</span>;
-<span class="pl-k">const</span> <span class="pl-c1">baz</span> <span class="pl-k">=</span> c <span class="pl-k">?</span> <span class="pl-c1">false</span> <span class="pl-k">:</span> <span class="pl-c1">true</span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> a <span class="pl-k">||</span> b;
-<span class="pl-k">const</span> <span class="pl-c1">bar</span> <span class="pl-k">=</span> <span class="pl-k">!!</span>c;
-<span class="pl-k">const</span> <span class="pl-c1">baz</span> <span class="pl-k">=</span> <span class="pl-k">!</span>c;</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="blocks" class="anchor" href="#blocks" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Blocks</h2>
-
-<p><a name="blocks--braces"></a><a name="16.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#blocks--braces">16.1</a> Use braces with all multi-line blocks.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">if</span> (test)
-  <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (test) <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (test) {
-  <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">foo</span>() { <span class="pl-k">return</span> <span class="pl-c1">false</span>; }
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">bar</span>() {
-  <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-}</pre></div>
-
-<p><a name="blocks--cuddled-elses"></a><a name="16.2"></a></p>
-</li>
-<li>
-<p><a href="#blocks--cuddled-elses">16.2</a> If you're using multi-line blocks with <code>if</code> and <code>else</code>, put <code>else</code> on the same line as your <code>if</code> block's closing brace. eslint: <a href="http://eslint.org/docs/rules/brace-style.html"><code>brace-style</code></a> jscs:  <a href="http://jscs.info/rule/disallowNewlineBeforeBlockStatements"><code>disallowNewlineBeforeBlockStatements</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">if</span> (test) {
-  <span class="pl-en">thing1</span>();
-  <span class="pl-en">thing2</span>();
-}
-<span class="pl-k">else</span> {
-  <span class="pl-en">thing3</span>();
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (test) {
-  <span class="pl-en">thing1</span>();
-  <span class="pl-en">thing2</span>();
-} <span class="pl-k">else</span> {
-  <span class="pl-en">thing3</span>();
-}</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="comments" class="anchor" href="#comments" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Comments</h2>
-
-<p><a name="comments--multiline"></a><a name="17.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#comments--multiline">17.1</a> Use <code>/** ... */</code> for multi-line comments. Include a description, specify types and values for all parameters and return values.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-c">// make() returns a new element</span>
-<span class="pl-c">// based on the passed in tag name</span>
-<span class="pl-c">//</span>
-<span class="pl-c">// @param {String} tag</span>
-<span class="pl-c">// @return {Element} element</span>
-<span class="pl-k">function</span> <span class="pl-en">make</span>(<span class="pl-smi">tag</span>) {
-
-  <span class="pl-c">// ...stuff...</span>
-
-  <span class="pl-k">return</span> element;
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-c">/**</span>
-<span class="pl-c"> * make() returns a new element</span>
-<span class="pl-c"> * based on the passed in tag name</span>
-<span class="pl-c"> *</span>
-<span class="pl-c"> * <span class="pl-k">@param</span> <span class="pl-en">{String}</span> <span class="pl-smi">tag</span></span>
-<span class="pl-c"> * <span class="pl-k">@return</span> <span class="pl-en">{Element}</span> element</span>
-<span class="pl-c"> */</span>
-<span class="pl-k">function</span> <span class="pl-en">make</span>(<span class="pl-smi">tag</span>) {
-
-  <span class="pl-c">// ...stuff...</span>
-
-  <span class="pl-k">return</span> element;
-}</pre></div>
-
-<p><a name="comments--singleline"></a><a name="17.2"></a></p>
-</li>
-<li>
-<p><a href="#comments--singleline">17.2</a> Use <code>//</code> for single line comments. Place single line comments on a newline above the subject of the comment. Put an empty line before the comment unless it's on the first line of a block.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">active</span> <span class="pl-k">=</span> <span class="pl-c1">true</span>;  <span class="pl-c">// is current tab</span>
-
-<span class="pl-c">// good</span>
-<span class="pl-c">// is current tab</span>
-<span class="pl-k">const</span> <span class="pl-c1">active</span> <span class="pl-k">=</span> <span class="pl-c1">true</span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">getType</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>fetching type...<span class="pl-pds">'</span></span>);
-  <span class="pl-c">// set the default type to 'no type'</span>
-  <span class="pl-k">const</span> <span class="pl-c1">type</span> <span class="pl-k">=</span> <span class="pl-v">this</span>.<span class="pl-smi">_type</span> <span class="pl-k">||</span> <span class="pl-s"><span class="pl-pds">'</span>no type<span class="pl-pds">'</span></span>;
-
-  <span class="pl-k">return</span> type;
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">getType</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>fetching type...<span class="pl-pds">'</span></span>);
-
-  <span class="pl-c">// set the default type to 'no type'</span>
-  <span class="pl-k">const</span> <span class="pl-c1">type</span> <span class="pl-k">=</span> <span class="pl-v">this</span>.<span class="pl-smi">_type</span> <span class="pl-k">||</span> <span class="pl-s"><span class="pl-pds">'</span>no type<span class="pl-pds">'</span></span>;
-
-  <span class="pl-k">return</span> type;
-}
-
-<span class="pl-c">// also good</span>
-<span class="pl-k">function</span> <span class="pl-en">getType</span>() {
-  <span class="pl-c">// set the default type to 'no type'</span>
-  <span class="pl-k">const</span> <span class="pl-c1">type</span> <span class="pl-k">=</span> <span class="pl-v">this</span>.<span class="pl-smi">_type</span> <span class="pl-k">||</span> <span class="pl-s"><span class="pl-pds">'</span>no type<span class="pl-pds">'</span></span>;
-
-  <span class="pl-k">return</span> type;
-}</pre></div>
-
-<p><a name="comments--actionitems"></a><a name="17.3"></a></p>
-</li>
-<li>
-<p><a href="#comments--actionitems">17.3</a> Prefixing your comments with <code>FIXME</code> or <code>TODO</code> helps other developers quickly understand if you're pointing out a problem that needs to be revisited, or if you're suggesting a solution to the problem that needs to be implemented. These are different than regular comments because they are actionable. The actions are <code>FIXME: -- need to figure this out</code> or <code>TODO: -- need to implement</code>.</p>
-
-<p><a name="comments--fixme"></a><a name="17.4"></a></p>
-</li>
-<li>
-<p><a href="#comments--fixme">17.4</a> Use <code>// FIXME:</code> to annotate problems.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">class</span> <span class="pl-en">Calculator</span> <span class="pl-k">extends</span> <span class="pl-e">Abacus</span> {
-  <span class="pl-en">constructor</span>() {
-    <span class="pl-v">super</span>();
-
-    <span class="pl-c">// FIXME: shouldn't use a global here</span>
-    total <span class="pl-k">=</span> <span class="pl-c1">0</span>;
-  }
-}</pre></div>
-
-<p><a name="comments--todo"></a><a name="17.5"></a></p>
-</li>
-<li>
-<p><a href="#comments--todo">17.5</a> Use <code>// TODO:</code> to annotate solutions to problems.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">class</span> <span class="pl-en">Calculator</span> <span class="pl-k">extends</span> <span class="pl-e">Abacus</span> {
-  <span class="pl-en">constructor</span>() {
-    <span class="pl-v">super</span>();
-
-    <span class="pl-c">// TODO: total should be configurable by an options param</span>
-    <span class="pl-v">this</span>.<span class="pl-smi">total</span> <span class="pl-k">=</span> <span class="pl-c1">0</span>;
-  }
-}</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="whitespace" class="anchor" href="#whitespace" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Whitespace</h2>
-
-<p><a name="whitespace--spaces"></a><a name="18.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#whitespace--spaces">18.1</a> Use soft tabs set to 2 spaces. eslint: <a href="http://eslint.org/docs/rules/indent.html"><code>indent</code></a> jscs: <a href="http://jscs.info/rule/validateIndentation"><code>validateIndentation</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">foo</span>() {
-∙∙∙∙<span class="pl-k">const</span> <span class="pl-c1">name</span>;
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">bar</span>() {
-∙<span class="pl-k">const</span> <span class="pl-c1">name</span>;
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">baz</span>() {
-∙∙<span class="pl-k">const</span> <span class="pl-c1">name</span>;
-}</pre></div>
-
-<p><a name="whitespace--before-blocks"></a><a name="18.2"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--before-blocks">18.2</a> Place 1 space before the leading brace. eslint: <a href="http://eslint.org/docs/rules/space-before-blocks.html"><code>space-before-blocks</code></a> jscs: <a href="http://jscs.info/rule/requireSpaceBeforeBlockStatements"><code>requireSpaceBeforeBlockStatements</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">test</span>(){
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>test<span class="pl-pds">'</span></span>);
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">test</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>test<span class="pl-pds">'</span></span>);
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-smi">dog</span>.<span class="pl-c1">set</span>(<span class="pl-s"><span class="pl-pds">'</span>attr<span class="pl-pds">'</span></span>,{
-  age<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>1 year<span class="pl-pds">'</span></span>,
-  breed<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Bernese Mountain Dog<span class="pl-pds">'</span></span>,
-});
-
-<span class="pl-c">// good</span>
-<span class="pl-smi">dog</span>.<span class="pl-c1">set</span>(<span class="pl-s"><span class="pl-pds">'</span>attr<span class="pl-pds">'</span></span>, {
-  age<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>1 year<span class="pl-pds">'</span></span>,
-  breed<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Bernese Mountain Dog<span class="pl-pds">'</span></span>,
-});</pre></div>
-
-<p><a name="whitespace--around-keywords"></a><a name="18.3"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--around-keywords">18.3</a> Place 1 space before the opening parenthesis in control statements (<code>if</code>, <code>while</code> etc.). Place no space between the argument list and the function name in function calls and declarations. eslint: <a href="http://eslint.org/docs/rules/keyword-spacing.html"><code>keyword-spacing</code></a> jscs: <a href="http://jscs.info/rule/requireSpaceAfterKeywords"><code>requireSpaceAfterKeywords</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">if</span>(isJedi) {
-  <span class="pl-en">fight</span> ();
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (isJedi) {
-  <span class="pl-en">fight</span>();
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">fight</span> () {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span> (<span class="pl-s"><span class="pl-pds">'</span>Swooosh!<span class="pl-pds">'</span></span>);
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">fight</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>Swooosh!<span class="pl-pds">'</span></span>);
-}</pre></div>
-
-<p><a name="whitespace--infix-ops"></a><a name="18.4"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--infix-ops">18.4</a> Set off operators with spaces. eslint: <a href="http://eslint.org/docs/rules/space-infix-ops.html"><code>space-infix-ops</code></a> jscs: <a href="http://jscs.info/rule/requireSpaceBeforeBinaryOperators"><code>requireSpaceBeforeBinaryOperators</code></a>, <a href="http://jscs.info/rule/requireSpaceAfterBinaryOperators"><code>requireSpaceAfterBinaryOperators</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">x</span><span class="pl-k">=</span>y<span class="pl-k">+</span><span class="pl-c1">5</span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">x</span> <span class="pl-k">=</span> y <span class="pl-k">+</span> <span class="pl-c1">5</span>;</pre></div>
-
-<p><a name="whitespace--newline-at-end"></a><a name="18.5"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--newline-at-end">18.5</a> End files with a single newline character.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-(<span class="pl-k">function</span> (<span class="pl-c1">global</span>) {
-  <span class="pl-c">// ...stuff...</span>
-})(<span class="pl-v">this</span>);</pre></div>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-(<span class="pl-k">function</span> (<span class="pl-c1">global</span>) {
-  <span class="pl-c">// ...stuff...</span>
-})(<span class="pl-v">this</span>);↵
-↵</pre></div>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// good</span>
-(<span class="pl-k">function</span> (<span class="pl-c1">global</span>) {
-  <span class="pl-c">// ...stuff...</span>
-})(<span class="pl-v">this</span>);↵</pre></div>
-
-<p><a name="whitespace--chains"></a><a name="18.6"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--chains">18.6</a> Use indentation when making long method chains (more than 2 method chains). Use a leading dot, which
-emphasizes that the line is a method call, not a new statement. eslint: <a href="http://eslint.org/docs/rules/newline-per-chained-call"><code>newline-per-chained-call</code></a> <a href="http://eslint.org/docs/rules/no-whitespace-before-property"><code>no-whitespace-before-property</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>#items<span class="pl-pds">'</span></span>).<span class="pl-c1">find</span>(<span class="pl-s"><span class="pl-pds">'</span>.selected<span class="pl-pds">'</span></span>).<span class="pl-en">highlight</span>().<span class="pl-en">end</span>().<span class="pl-c1">find</span>(<span class="pl-s"><span class="pl-pds">'</span>.open<span class="pl-pds">'</span></span>).<span class="pl-en">updateCount</span>();
-
-<span class="pl-c">// bad</span>
-<span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>#items<span class="pl-pds">'</span></span>).
-  <span class="pl-en">find</span>(<span class="pl-s"><span class="pl-pds">'</span>.selected<span class="pl-pds">'</span></span>).
-    <span class="pl-en">highlight</span>().
-    <span class="pl-en">end</span>().
-  <span class="pl-en">find</span>(<span class="pl-s"><span class="pl-pds">'</span>.open<span class="pl-pds">'</span></span>).
-    <span class="pl-en">updateCount</span>();
-
-<span class="pl-c">// good</span>
-<span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>#items<span class="pl-pds">'</span></span>)
-  .<span class="pl-c1">find</span>(<span class="pl-s"><span class="pl-pds">'</span>.selected<span class="pl-pds">'</span></span>)
-    .<span class="pl-en">highlight</span>()
-    .<span class="pl-en">end</span>()
-  .<span class="pl-c1">find</span>(<span class="pl-s"><span class="pl-pds">'</span>.open<span class="pl-pds">'</span></span>)
-    .<span class="pl-en">updateCount</span>();
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">leds</span> <span class="pl-k">=</span> <span class="pl-smi">stage</span>.<span class="pl-en">selectAll</span>(<span class="pl-s"><span class="pl-pds">'</span>.led<span class="pl-pds">'</span></span>).<span class="pl-c1">data</span>(data).<span class="pl-en">enter</span>().<span class="pl-c1">append</span>(<span class="pl-s"><span class="pl-pds">'</span>svg:svg<span class="pl-pds">'</span></span>).<span class="pl-en">classed</span>(<span class="pl-s"><span class="pl-pds">'</span>led<span class="pl-pds">'</span></span>, <span class="pl-c1">true</span>)
-    .<span class="pl-en">attr</span>(<span class="pl-s"><span class="pl-pds">'</span>width<span class="pl-pds">'</span></span>, (radius <span class="pl-k">+</span> margin) <span class="pl-k">*</span> <span class="pl-c1">2</span>).<span class="pl-c1">append</span>(<span class="pl-s"><span class="pl-pds">'</span>svg:g<span class="pl-pds">'</span></span>)
-    .<span class="pl-en">attr</span>(<span class="pl-s"><span class="pl-pds">'</span>transform<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>translate(<span class="pl-pds">'</span></span> <span class="pl-k">+</span> (radius <span class="pl-k">+</span> margin) <span class="pl-k">+</span> <span class="pl-s"><span class="pl-pds">'</span>,<span class="pl-pds">'</span></span> <span class="pl-k">+</span> (radius <span class="pl-k">+</span> margin) <span class="pl-k">+</span> <span class="pl-s"><span class="pl-pds">'</span>)<span class="pl-pds">'</span></span>)
-    .<span class="pl-c1">call</span>(<span class="pl-smi">tron</span>.<span class="pl-smi">led</span>);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">leds</span> <span class="pl-k">=</span> <span class="pl-smi">stage</span>.<span class="pl-en">selectAll</span>(<span class="pl-s"><span class="pl-pds">'</span>.led<span class="pl-pds">'</span></span>)
-    .<span class="pl-c1">data</span>(data)
-  .<span class="pl-en">enter</span>().<span class="pl-c1">append</span>(<span class="pl-s"><span class="pl-pds">'</span>svg:svg<span class="pl-pds">'</span></span>)
-    .<span class="pl-en">classed</span>(<span class="pl-s"><span class="pl-pds">'</span>led<span class="pl-pds">'</span></span>, <span class="pl-c1">true</span>)
-    .<span class="pl-en">attr</span>(<span class="pl-s"><span class="pl-pds">'</span>width<span class="pl-pds">'</span></span>, (radius <span class="pl-k">+</span> margin) <span class="pl-k">*</span> <span class="pl-c1">2</span>)
-  .<span class="pl-c1">append</span>(<span class="pl-s"><span class="pl-pds">'</span>svg:g<span class="pl-pds">'</span></span>)
-    .<span class="pl-en">attr</span>(<span class="pl-s"><span class="pl-pds">'</span>transform<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>translate(<span class="pl-pds">'</span></span> <span class="pl-k">+</span> (radius <span class="pl-k">+</span> margin) <span class="pl-k">+</span> <span class="pl-s"><span class="pl-pds">'</span>,<span class="pl-pds">'</span></span> <span class="pl-k">+</span> (radius <span class="pl-k">+</span> margin) <span class="pl-k">+</span> <span class="pl-s"><span class="pl-pds">'</span>)<span class="pl-pds">'</span></span>)
-    .<span class="pl-c1">call</span>(<span class="pl-smi">tron</span>.<span class="pl-smi">led</span>);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">leds</span> <span class="pl-k">=</span> <span class="pl-smi">stage</span>.<span class="pl-en">selectAll</span>(<span class="pl-s"><span class="pl-pds">'</span>.led<span class="pl-pds">'</span></span>).<span class="pl-c1">data</span>(data);</pre></div>
-
-<p><a name="whitespace--after-blocks"></a><a name="18.7"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--after-blocks">18.7</a> Leave a blank line after blocks and before the next statement. jscs: <a href="http://jscs.info/rule/requirePaddingNewLinesAfterBlocks"><code>requirePaddingNewLinesAfterBlocks</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">if</span> (foo) {
-  <span class="pl-k">return</span> bar;
-}
-<span class="pl-k">return</span> baz;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (foo) {
-  <span class="pl-k">return</span> bar;
-}
-
-<span class="pl-k">return</span> baz;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">obj</span> <span class="pl-k">=</span> {
-  <span class="pl-en">foo</span>() {
-  },
-  <span class="pl-en">bar</span>() {
-  },
-};
-<span class="pl-k">return</span> obj;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">obj</span> <span class="pl-k">=</span> {
-  <span class="pl-en">foo</span>() {
-  },
-
-  <span class="pl-en">bar</span>() {
-  },
-};
-
-<span class="pl-k">return</span> obj;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">arr</span> <span class="pl-k">=</span> [
-  <span class="pl-k">function</span> <span class="pl-en">foo</span>() {
-  },
-  <span class="pl-k">function</span> <span class="pl-en">bar</span>() {
-  },
-];
-<span class="pl-k">return</span> arr;
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">arr</span> <span class="pl-k">=</span> [
-  <span class="pl-k">function</span> <span class="pl-en">foo</span>() {
-  },
-
-  <span class="pl-k">function</span> <span class="pl-en">bar</span>() {
-  },
-];
-
-<span class="pl-k">return</span> arr;</pre></div>
-
-<p><a name="whitespace--padded-blocks"></a><a name="18.8"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--padded-blocks">18.8</a> Do not pad your blocks with blank lines. eslint: <a href="http://eslint.org/docs/rules/padded-blocks.html"><code>padded-blocks</code></a> jscs:  <a href="http://jscs.info/rule/disallowPaddingNewlinesInBlocks"><code>disallowPaddingNewlinesInBlocks</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">bar</span>() {
-
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo);
-
-}
-
-<span class="pl-c">// also bad</span>
-<span class="pl-k">if</span> (baz) {
-
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(qux);
-} <span class="pl-k">else</span> {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo);
-
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">bar</span>() {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo);
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (baz) {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(qux);
-} <span class="pl-k">else</span> {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo);
-}</pre></div>
-
-<p><a name="whitespace--in-parens"></a><a name="18.9"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--in-parens">18.9</a> Do not add spaces inside parentheses. eslint: <a href="http://eslint.org/docs/rules/space-in-parens.html"><code>space-in-parens</code></a> jscs: <a href="http://jscs.info/rule/disallowSpacesInsideParentheses"><code>disallowSpacesInsideParentheses</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">bar</span>( <span class="pl-smi">foo</span> ) {
-  <span class="pl-k">return</span> foo;
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">bar</span>(<span class="pl-smi">foo</span>) {
-  <span class="pl-k">return</span> foo;
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">if</span> ( foo ) {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo);
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (foo) {
-  <span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo);
-}</pre></div>
-
-<p><a name="whitespace--in-brackets"></a><a name="18.10"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--in-brackets">18.10</a> Do not add spaces inside brackets. eslint: <a href="http://eslint.org/docs/rules/array-bracket-spacing.html"><code>array-bracket-spacing</code></a> jscs: <a href="http://jscs.info/rule/disallowSpacesInsideArrayBrackets"><code>disallowSpacesInsideArrayBrackets</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> [ <span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span> ];
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo[ <span class="pl-c1">0</span> ]);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> [<span class="pl-c1">1</span>, <span class="pl-c1">2</span>, <span class="pl-c1">3</span>];
-<span class="pl-en">console</span>.<span class="pl-c1">log</span>(foo[<span class="pl-c1">0</span>]);</pre></div>
-
-<p><a name="whitespace--in-braces"></a><a name="18.11"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--in-braces">18.11</a> Add spaces inside curly braces. eslint: <a href="http://eslint.org/docs/rules/object-curly-spacing.html"><code>object-curly-spacing</code></a> jscs: <a href="http://jscs.info/rule/requireSpacesInsideObjectBrackets"><code>requireSpacesInsideObjectBrackets</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> {clark<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>kent<span class="pl-pds">'</span></span>};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> { clark<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>kent<span class="pl-pds">'</span></span> };</pre></div>
-
-<p><a name="whitespace--max-len"></a><a name="18.12"></a></p>
-</li>
-<li>
-<p><a href="#whitespace--max-len">18.12</a> Avoid having lines of code that are longer than 100 characters (including whitespace). eslint: <a href="http://eslint.org/docs/rules/max-len.html"><code>max-len</code></a> jscs: <a href="http://jscs.info/rule/maximumLineLength"><code>maximumLineLength</code></a></p>
-
-<blockquote>
-<p>Why? This ensures readability and maintainability.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Whatever national crop flips the window. The cartoon reverts within the screw. Whatever wizard constrains a helpful ally. The counterpart ascends!<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-smi">$</span>.<span class="pl-en">ajax</span>({ method<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>POST<span class="pl-pds">'</span></span>, url<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>https://airbnb.com/<span class="pl-pds">'</span></span>, data<span class="pl-k">:</span> { name<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>John<span class="pl-pds">'</span></span> } }).<span class="pl-en">done</span>(() <span class="pl-k">=&gt;</span> <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>Congratulations!<span class="pl-pds">'</span></span>)).<span class="pl-en">fail</span>(() <span class="pl-k">=&gt;</span> <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>You have failed this city.<span class="pl-pds">'</span></span>));
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">foo</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Whatever national crop flips the window. The cartoon reverts within the screw. <span class="pl-pds">'</span></span> <span class="pl-k">+</span>
-  <span class="pl-s"><span class="pl-pds">'</span>Whatever wizard constrains a helpful ally. The counterpart ascends!<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-smi">$</span>.<span class="pl-en">ajax</span>({
-  method<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>POST<span class="pl-pds">'</span></span>,
-  url<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>https://airbnb.com/<span class="pl-pds">'</span></span>,
-  data<span class="pl-k">:</span> { name<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>John<span class="pl-pds">'</span></span> },
-})
-  .<span class="pl-en">done</span>(() <span class="pl-k">=&gt;</span> <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>Congratulations!<span class="pl-pds">'</span></span>))
-  .<span class="pl-en">fail</span>(() <span class="pl-k">=&gt;</span> <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-s"><span class="pl-pds">'</span>You have failed this city.<span class="pl-pds">'</span></span>));</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="commas" class="anchor" href="#commas" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Commas</h2>
-
-<p><a name="commas--leading-trailing"></a><a name="19.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#commas--leading-trailing">19.1</a> Leading commas: <strong>Nope.</strong> eslint: <a href="http://eslint.org/docs/rules/comma-style.html"><code>comma-style</code></a> jscs: <a href="http://jscs.info/rule/requireCommaBeforeLineBreak"><code>requireCommaBeforeLineBreak</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">story</span> <span class="pl-k">=</span> [
-    once
-  , upon
-  , aTime
-];
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">story</span> <span class="pl-k">=</span> [
-  once,
-  upon,
-  aTime,
-];
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">hero</span> <span class="pl-k">=</span> {
-    firstName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Ada<span class="pl-pds">'</span></span>
-  , lastName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Lovelace<span class="pl-pds">'</span></span>
-  , birthYear<span class="pl-k">:</span> <span class="pl-c1">1815</span>
-  , superPower<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>computers<span class="pl-pds">'</span></span>
-};
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">hero</span> <span class="pl-k">=</span> {
-  firstName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Ada<span class="pl-pds">'</span></span>,
-  lastName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Lovelace<span class="pl-pds">'</span></span>,
-  birthYear<span class="pl-k">:</span> <span class="pl-c1">1815</span>,
-  superPower<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>computers<span class="pl-pds">'</span></span>,
-};</pre></div>
-
-<p><a name="commas--dangling"></a><a name="19.2"></a></p>
-</li>
-<li>
-<p><a href="#commas--dangling">19.2</a> Additional trailing comma: <strong>Yup.</strong> eslint: <a href="http://eslint.org/docs/rules/comma-dangle.html"><code>comma-dangle</code></a> jscs: <a href="http://jscs.info/rule/requireTrailingComma"><code>requireTrailingComma</code></a></p>
-
-<blockquote>
-<p>Why? This leads to cleaner git diffs. Also, transpilers like Babel will remove the additional trailing comma in the transpiled code which means you don't have to worry about the <a href="es5/README.md#commas">trailing comma problem</a> in legacy browsers.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad - git diff without trailing comma</span>
-<span class="pl-k">const</span> <span class="pl-c1">hero</span> <span class="pl-k">=</span> {
-     firstName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Florence<span class="pl-pds">'</span></span>,
-<span class="pl-k">-</span>    lastName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Nightingale<span class="pl-pds">'</span></span>
-<span class="pl-k">+</span>    lastName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Nightingale<span class="pl-pds">'</span></span>,
-<span class="pl-k">+</span>    inventorOf<span class="pl-k">:</span> [<span class="pl-s"><span class="pl-pds">'</span>coxcomb graph<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>modern nursing<span class="pl-pds">'</span></span>]
-};
-
-<span class="pl-c">// good - git diff with trailing comma</span>
-<span class="pl-k">const</span> <span class="pl-c1">hero</span> <span class="pl-k">=</span> {
-     firstName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Florence<span class="pl-pds">'</span></span>,
-     lastName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Nightingale<span class="pl-pds">'</span></span>,
-<span class="pl-k">+</span>    inventorOf<span class="pl-k">:</span> [<span class="pl-s"><span class="pl-pds">'</span>coxcomb chart<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>modern nursing<span class="pl-pds">'</span></span>],
-};
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">hero</span> <span class="pl-k">=</span> {
-  firstName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Dana<span class="pl-pds">'</span></span>,
-  lastName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Scully<span class="pl-pds">'</span></span>
-};
-
-<span class="pl-k">const</span> <span class="pl-c1">heroes</span> <span class="pl-k">=</span> [
-  <span class="pl-s"><span class="pl-pds">'</span>Batman<span class="pl-pds">'</span></span>,
-  <span class="pl-s"><span class="pl-pds">'</span>Superman<span class="pl-pds">'</span></span>
-];
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">hero</span> <span class="pl-k">=</span> {
-  firstName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Dana<span class="pl-pds">'</span></span>,
-  lastName<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>Scully<span class="pl-pds">'</span></span>,
-};
-
-<span class="pl-k">const</span> <span class="pl-c1">heroes</span> <span class="pl-k">=</span> [
-  <span class="pl-s"><span class="pl-pds">'</span>Batman<span class="pl-pds">'</span></span>,
-  <span class="pl-s"><span class="pl-pds">'</span>Superman<span class="pl-pds">'</span></span>,
-];</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="semicolons" class="anchor" href="#semicolons" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Semicolons</h2>
-
-<p><a name="semicolons--required"></a><a name="20.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#20.1">20.1</a> <strong>Yup.</strong> eslint: <a href="http://eslint.org/docs/rules/semi.html"><code>semi</code></a> jscs: <a href="http://jscs.info/rule/requireSemicolons"><code>requireSemicolons</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-(<span class="pl-k">function</span> () {
-  <span class="pl-k">const</span> <span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Skywalker<span class="pl-pds">'</span></span>
-  <span class="pl-k">return</span> name
-})()
-
-<span class="pl-c">// good</span>
-(<span class="pl-k">function</span> () {
-  <span class="pl-k">const</span> <span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Skywalker<span class="pl-pds">'</span></span>;
-  <span class="pl-k">return</span> name;
-}());
-
-<span class="pl-c">// good, but legacy (guards against the function becoming an argument when two files with IIFEs are concatenated)</span>
-;(() <span class="pl-k">=&gt;</span> {
-  <span class="pl-k">const</span> <span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Skywalker<span class="pl-pds">'</span></span>;
-  <span class="pl-k">return</span> name;
-}());</pre></div>
-
-<p><a href="http://stackoverflow.com/questions/7365172/semicolon-before-self-invoking-function/7365214%237365214">Read more</a>.</p>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="type-casting--coercion" class="anchor" href="#type-casting--coercion" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Type Casting &amp; Coercion</h2>
-
-<p><a name="coercion--explicit"></a><a name="21.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#coercion--explicit">21.1</a> Perform type coercion at the beginning of the statement.</p>
-
-<p><a name="coercion--strings"></a><a name="21.2"></a></p>
-</li>
-<li>
-<p><a href="#coercion--strings">21.2</a>  Strings:</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// =&gt; this.reviewScore = 9;</span>
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">totalScore</span> <span class="pl-k">=</span> <span class="pl-v">this</span>.<span class="pl-smi">reviewScore</span> <span class="pl-k">+</span> <span class="pl-s"><span class="pl-pds">'</span><span class="pl-pds">'</span></span>; <span class="pl-c">// invokes this.reviewScore.valueOf()</span>
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">totalScore</span> <span class="pl-k">=</span> <span class="pl-v">this</span>.<span class="pl-smi">reviewScore</span>.<span class="pl-c1">toString</span>(); <span class="pl-c">// isn't guaranteed to return a string</span>
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">totalScore</span> <span class="pl-k">=</span> <span class="pl-c1">String</span>(<span class="pl-v">this</span>.<span class="pl-smi">reviewScore</span>);</pre></div>
-
-<p><a name="coercion--numbers"></a><a name="21.3"></a></p>
-</li>
-<li>
-<p><a href="#coercion--numbers">21.3</a> Numbers: Use <code>Number</code> for type casting and <code>parseInt</code> always with a radix for parsing strings. eslint: <a href="http://eslint.org/docs/rules/radix"><code>radix</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">inputValue</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>4<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">val</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">Number</span>(inputValue);
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">val</span> <span class="pl-k">=</span> <span class="pl-k">+</span>inputValue;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">val</span> <span class="pl-k">=</span> inputValue <span class="pl-k">&gt;&gt;</span> <span class="pl-c1">0</span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">val</span> <span class="pl-k">=</span> <span class="pl-c1">parseInt</span>(inputValue);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">val</span> <span class="pl-k">=</span> <span class="pl-c1">Number</span>(inputValue);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">val</span> <span class="pl-k">=</span> <span class="pl-c1">parseInt</span>(inputValue, <span class="pl-c1">10</span>);</pre></div>
-
-<p><a name="coercion--comment-deviations"></a><a name="21.4"></a></p>
-</li>
-<li>
-<p><a href="#coercion--comment-deviations">21.4</a> If for whatever reason you are doing something wild and <code>parseInt</code> is your bottleneck and need to use Bitshift for <a href="http://jsperf.com/coercion-vs-casting/3">performance reasons</a>, leave a comment explaining why and what you're doing.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// good</span>
-<span class="pl-c">/**</span>
-<span class="pl-c"> * parseInt was the reason my code was slow.</span>
-<span class="pl-c"> * Bitshifting the String to coerce it to a</span>
-<span class="pl-c"> * Number made it a lot faster.</span>
-<span class="pl-c"> */</span>
-<span class="pl-k">const</span> <span class="pl-c1">val</span> <span class="pl-k">=</span> inputValue <span class="pl-k">&gt;&gt;</span> <span class="pl-c1">0</span>;</pre></div>
-
-<p><a name="coercion--bitwise"></a><a name="21.5"></a></p>
-</li>
-<li>
-<p><a href="#coercion--bitwise">21.5</a> <strong>Note:</strong> Be careful when using bitshift operations. Numbers are represented as <a href="http://es5.github.io/#x4.3.19">64-bit values</a>, but bitshift operations always return a 32-bit integer (<a href="http://es5.github.io/#x11.7">source</a>). Bitshift can lead to unexpected behavior for integer values larger than 32 bits. <a href="https://github.com/airbnb/javascript/issues/109">Discussion</a>. Largest signed 32-bit Int is 2,147,483,647:</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c1">2147483647</span> <span class="pl-k">&gt;&gt;</span> <span class="pl-c1">0</span> <span class="pl-c">//=&gt; 2147483647</span>
-<span class="pl-c1">2147483648</span> <span class="pl-k">&gt;&gt;</span> <span class="pl-c1">0</span> <span class="pl-c">//=&gt; -2147483648</span>
-<span class="pl-c1">2147483649</span> <span class="pl-k">&gt;&gt;</span> <span class="pl-c1">0</span> <span class="pl-c">//=&gt; -2147483647</span></pre></div>
-
-<p><a name="coercion--booleans"></a><a name="21.6"></a></p>
-</li>
-<li>
-<p><a href="#coercion--booleans">21.6</a> Booleans:</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">age</span> <span class="pl-k">=</span> <span class="pl-c1">0</span>;
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">hasAge</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">Boolean</span>(age);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">hasAge</span> <span class="pl-k">=</span> <span class="pl-c1">Boolean</span>(age);
-
-<span class="pl-c">// best</span>
-<span class="pl-k">const</span> <span class="pl-c1">hasAge</span> <span class="pl-k">=</span> <span class="pl-k">!!</span>age;</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="naming-conventions" class="anchor" href="#naming-conventions" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Naming Conventions</h2>
-
-<p><a name="naming--descriptive"></a><a name="22.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#naming--descriptive">22.1</a> Avoid single letter names. Be descriptive with your naming.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">q</span>() {
-  <span class="pl-c">// ...stuff...</span>
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">query</span>() {
-  <span class="pl-c">// ..stuff..</span>
-}</pre></div>
-
-<p><a name="naming--camelCase"></a><a name="22.2"></a></p>
-</li>
-<li>
-<p><a href="#naming--camelCase">22.2</a> Use camelCase when naming objects, functions, and instances. eslint: <a href="http://eslint.org/docs/rules/camelcase.html"><code>camelcase</code></a> jscs: <a href="http://jscs.info/rule/requireCamelCaseOrUpperCaseIdentifiers"><code>requireCamelCaseOrUpperCaseIdentifiers</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">OBJEcttsssss</span> <span class="pl-k">=</span> {};
-<span class="pl-k">const</span> <span class="pl-c1">this_is_my_object</span> <span class="pl-k">=</span> {};
-<span class="pl-k">function</span> <span class="pl-en">c</span>() {}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">thisIsMyObject</span> <span class="pl-k">=</span> {};
-<span class="pl-k">function</span> <span class="pl-en">thisIsMyFunction</span>() {}</pre></div>
-
-<p><a name="naming--PascalCase"></a><a name="22.3"></a></p>
-</li>
-<li>
-<p><a href="#naming--PascalCase">22.3</a> Use PascalCase only when naming constructors or classes. eslint: <a href="http://eslint.org/docs/rules/new-cap.html"><code>new-cap</code></a> jscs: <a href="http://jscs.info/rule/requireCapitalizedConstructors"><code>requireCapitalizedConstructors</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">user</span>(<span class="pl-smi">options</span>) {
-  <span class="pl-v">this</span>.<span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-smi">options</span>.<span class="pl-c1">name</span>;
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">bad</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">user</span>({
-  name<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>nope<span class="pl-pds">'</span></span>,
-});
-
-<span class="pl-c">// good</span>
-<span class="pl-k">class</span> <span class="pl-en">User</span> {
-  <span class="pl-en">constructor</span>(<span class="pl-smi">options</span>) {
-    <span class="pl-v">this</span>.<span class="pl-c1">name</span> <span class="pl-k">=</span> <span class="pl-smi">options</span>.<span class="pl-c1">name</span>;
-  }
-}
-
-<span class="pl-k">const</span> <span class="pl-c1">good</span> <span class="pl-k">=</span> <span class="pl-k">new</span> <span class="pl-en">User</span>({
-  name<span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>yup<span class="pl-pds">'</span></span>,
-});</pre></div>
-
-<p><a name="naming--leading-underscore"></a><a name="22.4"></a></p>
-</li>
-<li>
-<p><a href="#naming--leading-underscore">22.4</a> Do not use trailing or leading underscores. eslint: <a href="http://eslint.org/docs/rules/no-underscore-dangle.html"><code>no-underscore-dangle</code></a> jscs: <a href="http://jscs.info/rule/disallowDanglingUnderscores"><code>disallowDanglingUnderscores</code></a></p>
-
-<blockquote>
-<p>Why? JavaScript does not have the concept of privacy in terms of properties or methods. Although a leading underscore is a common convention to mean “private”, in fact, these properties are fully public, and as such, are part of your public API contract. This convention might lead developers to wrongly think that a change won't count as breaking, or that tests aren't needed. tl;dr: if you want something to be “private”, it must not be observably present.</p>
-</blockquote>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-v">this</span>.<span class="pl-smi">__firstName__</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Panda<span class="pl-pds">'</span></span>;
-<span class="pl-v">this</span>.<span class="pl-smi">firstName_</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Panda<span class="pl-pds">'</span></span>;
-<span class="pl-v">this</span>.<span class="pl-smi">_firstName</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Panda<span class="pl-pds">'</span></span>;
-
-<span class="pl-c">// good</span>
-<span class="pl-v">this</span>.<span class="pl-smi">firstName</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">'</span>Panda<span class="pl-pds">'</span></span>;</pre></div>
-
-<p><a name="naming--self-this"></a><a name="22.5"></a></p>
-</li>
-<li>
-<p><a href="#naming--self-this">22.5</a> Don't save references to <code>this</code>. Use arrow functions or Function#bind. jscs: <a href="http://jscs.info/rule/disallowNodeTypes"><code>disallowNodeTypes</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">foo</span>() {
-  <span class="pl-k">const</span> <span class="pl-c1">self</span> <span class="pl-k">=</span> <span class="pl-v">this</span>;
-  <span class="pl-k">return</span> <span class="pl-k">function</span> () {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(self);
-  };
-}
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">foo</span>() {
-  <span class="pl-k">const</span> <span class="pl-c1">that</span> <span class="pl-k">=</span> <span class="pl-v">this</span>;
-  <span class="pl-k">return</span> <span class="pl-k">function</span> () {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(that);
-  };
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">foo</span>() {
-  <span class="pl-k">return</span> () <span class="pl-k">=&gt;</span> {
-    <span class="pl-en">console</span>.<span class="pl-c1">log</span>(<span class="pl-v">this</span>);
-  };
-}</pre></div>
-
-<p><a name="naming--filename-matches-export"></a><a name="22.6"></a></p>
-</li>
-<li>
-<p><a href="#naming--filename-matches-export">22.6</a> A base filename should exactly match the name of its default export.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// file 1 contents</span>
-<span class="pl-k">class</span> <span class="pl-en">CheckBox</span> {
-  <span class="pl-c">// ...</span>
-}
-<span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-smi">CheckBox</span>;
-
-<span class="pl-c">// file 2 contents</span>
-<span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-k">function</span> <span class="pl-en">fortyTwo</span>() { <span class="pl-k">return</span> <span class="pl-c1">42</span>; }
-
-<span class="pl-c">// file 3 contents</span>
-<span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-k">function</span> <span class="pl-en">insideDirectory</span>() {}
-
-<span class="pl-c">// in some other file</span>
-<span class="pl-c">// bad</span>
-<span class="pl-k">import</span> <span class="pl-smi">CheckBox</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./checkBox<span class="pl-pds">'</span></span>; <span class="pl-c">// PascalCase import/export, camelCase filename</span>
-<span class="pl-k">import</span> <span class="pl-smi">FortyTwo</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./FortyTwo<span class="pl-pds">'</span></span>; <span class="pl-c">// PascalCase import/filename, camelCase export</span>
-<span class="pl-k">import</span> <span class="pl-smi">InsideDirectory</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./InsideDirectory<span class="pl-pds">'</span></span>; <span class="pl-c">// PascalCase import/filename, camelCase export</span>
-
-<span class="pl-c">// bad</span>
-<span class="pl-k">import</span> <span class="pl-smi">CheckBox</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./check_box<span class="pl-pds">'</span></span>; <span class="pl-c">// PascalCase import/export, snake_case filename</span>
-<span class="pl-k">import</span> <span class="pl-smi">forty_two</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./forty_two<span class="pl-pds">'</span></span>; <span class="pl-c">// snake_case import/filename, camelCase export</span>
-<span class="pl-k">import</span> <span class="pl-smi">inside_directory</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./inside_directory<span class="pl-pds">'</span></span>; <span class="pl-c">// snake_case import, camelCase export</span>
-<span class="pl-k">import</span> <span class="pl-smi">index</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./inside_directory/index<span class="pl-pds">'</span></span>; <span class="pl-c">// requiring the index file explicitly</span>
-<span class="pl-k">import</span> <span class="pl-smi">insideDirectory</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./insideDirectory/index<span class="pl-pds">'</span></span>; <span class="pl-c">// requiring the index file explicitly</span>
-
-<span class="pl-c">// good</span>
-<span class="pl-k">import</span> <span class="pl-smi">CheckBox</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./CheckBox<span class="pl-pds">'</span></span>; <span class="pl-c">// PascalCase export/import/filename</span>
-<span class="pl-k">import</span> <span class="pl-smi">fortyTwo</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./fortyTwo<span class="pl-pds">'</span></span>; <span class="pl-c">// camelCase export/import/filename</span>
-<span class="pl-k">import</span> <span class="pl-smi">insideDirectory</span> <span class="pl-k">from</span> <span class="pl-s"><span class="pl-pds">'</span>./insideDirectory<span class="pl-pds">'</span></span>; <span class="pl-c">// camelCase export/import/directory name/implicit "index"</span>
-<span class="pl-c">// ^ supports both insideDirectory.js and insideDirectory/index.js</span></pre></div>
-
-<p><a name="naming--camelCase-default-export"></a><a name="22.7"></a></p>
-</li>
-<li>
-<p><a href="#naming--camelCase-default-export">22.7</a> Use camelCase when you export-default a function. Your filename should be identical to your function's name.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">function</span> <span class="pl-en">makeStyleGuide</span>() {
-}
-
-<span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-smi">makeStyleGuide</span>;</pre></div>
-
-<p><a name="naming--PascalCase-singleton"></a><a name="22.8"></a></p>
-</li>
-<li>
-<p><a href="#naming--PascalCase-singleton">22.8</a> Use PascalCase when you export a constructor / class / singleton / function library / bare object.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">const</span> <span class="pl-c1">AirbnbStyleGuide</span> <span class="pl-k">=</span> {
-  es6<span class="pl-k">:</span> {
-  }
-};
-
-<span class="pl-k">export</span> <span class="pl-v">default</span> <span class="pl-smi">AirbnbStyleGuide</span>;</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="accessors" class="anchor" href="#accessors" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Accessors</h2>
-
-<p><a name="accessors--not-required"></a><a name="23.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#accessors--not-required">23.1</a> Accessor functions for properties are not required.</p>
-
-<p><a name="accessors--no-getters-setters"></a><a name="23.2"></a></p>
-</li>
-<li>
-<p><a href="#accessors--no-getters-setters">23.2</a> Do not use JavaScript getters/setters as they cause unexpected side effects and are harder to test, maintain, and reason about. Instead, if you do make accessor functions, use getVal() and setVal('hello').</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">class</span> <span class="pl-en">Dragon</span> {
-  <span class="pl-k">get</span> <span class="pl-en">age</span>() {
-    <span class="pl-c">// ...</span>
-  }
-
-  <span class="pl-k">set</span> <span class="pl-en">age</span>(<span class="pl-smi">value</span>) {
-    <span class="pl-c">// ...</span>
-  }
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">class</span> <span class="pl-en">Dragon</span> {
-  <span class="pl-en">getAge</span>() {
-    <span class="pl-c">// ...</span>
-  }
-
-  <span class="pl-en">setAge</span>(<span class="pl-smi">value</span>) {
-    <span class="pl-c">// ...</span>
-  }
-}</pre></div>
-
-<p><a name="accessors--boolean-prefix"></a><a name="23.3"></a></p>
-</li>
-<li>
-<p><a href="#accessors--boolean-prefix">23.3</a> If the property/method is a <code>boolean</code>, use <code>isVal()</code> or <code>hasVal()</code>.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">if</span> (<span class="pl-k">!</span><span class="pl-smi">dragon</span>.<span class="pl-en">age</span>()) {
-  <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">if</span> (<span class="pl-k">!</span><span class="pl-smi">dragon</span>.<span class="pl-en">hasAge</span>()) {
-  <span class="pl-k">return</span> <span class="pl-c1">false</span>;
-}</pre></div>
-
-<p><a name="accessors--consistent"></a><a name="23.4"></a></p>
-</li>
-<li>
-<p><a href="#accessors--consistent">23.4</a> It's okay to create get() and set() functions, but be consistent.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">class</span> <span class="pl-en">Jedi</span> {
-  <span class="pl-en">constructor</span>(<span class="pl-smi">options</span> <span class="pl-k">=</span> {}) {
-    <span class="pl-k">const</span> <span class="pl-c1">lightsaber</span> <span class="pl-k">=</span> <span class="pl-smi">options</span>.<span class="pl-smi">lightsaber</span> <span class="pl-k">||</span> <span class="pl-s"><span class="pl-pds">'</span>blue<span class="pl-pds">'</span></span>;
-    <span class="pl-v">this</span>.<span class="pl-c1">set</span>(<span class="pl-s"><span class="pl-pds">'</span>lightsaber<span class="pl-pds">'</span></span>, lightsaber);
-  }
-
-  <span class="pl-en">set</span>(<span class="pl-smi">key</span>, <span class="pl-smi">val</span>) {
-    <span class="pl-v">this</span>[key] <span class="pl-k">=</span> val;
-  }
-
-  <span class="pl-en">get</span>(<span class="pl-smi">key</span>) {
-    <span class="pl-k">return</span> <span class="pl-v">this</span>[key];
-  }
-}</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="events" class="anchor" href="#events" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Events</h2>
-
-<p><a name="events--hash"></a><a name="24.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#events--hash">24.1</a> When attaching data payloads to events (whether DOM events or something more proprietary like Backbone events), pass a hash instead of a raw value. This allows a subsequent contributor to add more data to the event payload without finding and updating every handler for the event. For example, instead of:</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-en">$</span>(<span class="pl-v">this</span>).<span class="pl-en">trigger</span>(<span class="pl-s"><span class="pl-pds">'</span>listingUpdated<span class="pl-pds">'</span></span>, <span class="pl-smi">listing</span>.<span class="pl-c1">id</span>);
-
-<span class="pl-k">...</span>
-
-<span class="pl-en">$</span>(<span class="pl-v">this</span>).<span class="pl-en">on</span>(<span class="pl-s"><span class="pl-pds">'</span>listingUpdated<span class="pl-pds">'</span></span>, (<span class="pl-smi">e</span>, <span class="pl-smi">listingId</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-c">// do something with listingId</span>
-});</pre></div>
-
-<p>prefer:</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// good</span>
-<span class="pl-en">$</span>(<span class="pl-v">this</span>).<span class="pl-en">trigger</span>(<span class="pl-s"><span class="pl-pds">'</span>listingUpdated<span class="pl-pds">'</span></span>, { listingId<span class="pl-k">:</span> <span class="pl-smi">listing</span>.<span class="pl-c1">id</span> });
-
-<span class="pl-k">...</span>
-
-<span class="pl-en">$</span>(<span class="pl-v">this</span>).<span class="pl-en">on</span>(<span class="pl-s"><span class="pl-pds">'</span>listingUpdated<span class="pl-pds">'</span></span>, (<span class="pl-smi">e</span>, <span class="pl-smi">data</span>) <span class="pl-k">=&gt;</span> {
-  <span class="pl-c">// do something with data.listingId</span>
-});</pre></div>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-</li>
-</ul>
-
-<h2>
-<a id="jquery" class="anchor" href="#jquery" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>jQuery</h2>
-
-<p><a name="jquery--dollar-prefix"></a><a name="25.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#jquery--dollar-prefix">25.1</a> Prefix jQuery object variables with a <code>$</code>. jscs: <a href="http://jscs.info/rule/requireDollarBeforejQueryAssignment"><code>requireDollarBeforejQueryAssignment</code></a></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">const</span> <span class="pl-c1">sidebar</span> <span class="pl-k">=</span> <span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar<span class="pl-pds">'</span></span>);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">$sidebar</span> <span class="pl-k">=</span> <span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar<span class="pl-pds">'</span></span>);
-
-<span class="pl-c">// good</span>
-<span class="pl-k">const</span> <span class="pl-c1">$sidebarBtn</span> <span class="pl-k">=</span> <span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar-btn<span class="pl-pds">'</span></span>);</pre></div>
-
-<p><a name="jquery--cache"></a><a name="25.2"></a></p>
-</li>
-<li>
-<p><a href="#jquery--cache">25.2</a> Cache jQuery lookups.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-k">function</span> <span class="pl-en">setSidebar</span>() {
-  <span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar<span class="pl-pds">'</span></span>).<span class="pl-en">hide</span>();
-
-  <span class="pl-c">// ...stuff...</span>
-
-  <span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar<span class="pl-pds">'</span></span>).<span class="pl-en">css</span>({
-    <span class="pl-s"><span class="pl-pds">'</span>background-color<span class="pl-pds">'</span></span><span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>pink<span class="pl-pds">'</span></span>
-  });
-}
-
-<span class="pl-c">// good</span>
-<span class="pl-k">function</span> <span class="pl-en">setSidebar</span>() {
-  <span class="pl-k">const</span> <span class="pl-c1">$sidebar</span> <span class="pl-k">=</span> <span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar<span class="pl-pds">'</span></span>);
-  <span class="pl-smi">$sidebar</span>.<span class="pl-en">hide</span>();
-
-  <span class="pl-c">// ...stuff...</span>
-
-  <span class="pl-smi">$sidebar</span>.<span class="pl-en">css</span>({
-    <span class="pl-s"><span class="pl-pds">'</span>background-color<span class="pl-pds">'</span></span><span class="pl-k">:</span> <span class="pl-s"><span class="pl-pds">'</span>pink<span class="pl-pds">'</span></span>
-  });
-}</pre></div>
-
-<p><a name="jquery--queries"></a><a name="25.3"></a></p>
-</li>
-<li>
-<p><a href="#jquery--queries">25.3</a> For DOM queries use Cascading <code>$('.sidebar ul')</code> or parent &gt; child <code>$('.sidebar &gt; ul')</code>. <a href="http://jsperf.com/jquery-find-vs-context-sel/16">jsPerf</a></p>
-
-<p><a name="jquery--find"></a><a name="25.4"></a></p>
-</li>
-<li>
-<p><a href="#jquery--find">25.4</a> Use <code>find</code> with scoped jQuery object queries.</p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-c">// bad</span>
-<span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>ul<span class="pl-pds">'</span></span>, <span class="pl-s"><span class="pl-pds">'</span>.sidebar<span class="pl-pds">'</span></span>).<span class="pl-en">hide</span>();
-
-<span class="pl-c">// bad</span>
-<span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar<span class="pl-pds">'</span></span>).<span class="pl-c1">find</span>(<span class="pl-s"><span class="pl-pds">'</span>ul<span class="pl-pds">'</span></span>).<span class="pl-en">hide</span>();
-
-<span class="pl-c">// good</span>
-<span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar ul<span class="pl-pds">'</span></span>).<span class="pl-en">hide</span>();
-
-<span class="pl-c">// good</span>
-<span class="pl-en">$</span>(<span class="pl-s"><span class="pl-pds">'</span>.sidebar &gt; ul<span class="pl-pds">'</span></span>).<span class="pl-en">hide</span>();
-
-<span class="pl-c">// good</span>
-<span class="pl-smi">$sidebar</span>.<span class="pl-c1">find</span>(<span class="pl-s"><span class="pl-pds">'</span>ul<span class="pl-pds">'</span></span>).<span class="pl-en">hide</span>();</pre></div>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="ecmascript-5-compatibility" class="anchor" href="#ecmascript-5-compatibility" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>ECMAScript 5 Compatibility</h2>
-
-<p><a name="es5-compat--kangax"></a><a name="26.1"></a></p>
-
-<ul>
-<li>
-<a href="#es5-compat--kangax">26.1</a> Refer to <a href="https://twitter.com/kangax/">Kangax</a>'s ES5 <a href="http://kangax.github.io/es5-compat-table/">compatibility table</a>.</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="ecmascript-6-styles" class="anchor" href="#ecmascript-6-styles" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>ECMAScript 6 Styles</h2>
-
-<p><a name="es6-styles"></a><a name="27.1"></a></p>
-
-<ul>
-<li>
-<a href="#es6-styles">27.1</a> This is a collection of links to the various ES6 features.</li>
-</ul>
-
-<ol>
-<li><a href="#arrow-functions">Arrow Functions</a></li>
-<li><a href="#constructors">Classes</a></li>
-<li><a href="#es6-object-shorthand">Object Shorthand</a></li>
-<li><a href="#es6-object-concise">Object Concise</a></li>
-<li><a href="#es6-computed-properties">Object Computed Properties</a></li>
-<li><a href="#es6-template-literals">Template Strings</a></li>
-<li><a href="#destructuring">Destructuring</a></li>
-<li><a href="#es6-default-parameters">Default Parameters</a></li>
-<li><a href="#es6-rest">Rest</a></li>
-<li><a href="#es6-array-spreads">Array Spreads</a></li>
-<li><a href="#references">Let and Const</a></li>
-<li><a href="#iterators-and-generators">Iterators and Generators</a></li>
-<li><a href="#modules">Modules</a></li>
-</ol>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="testing" class="anchor" href="#testing" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Testing</h2>
-
-<p><a name="testing--yup"></a><a name="28.1"></a></p>
-
-<ul>
-<li>
-<p><a href="#testing--yup">28.1</a> <strong>Yup.</strong></p>
-
-<div class="highlight highlight-source-js"><pre><span class="pl-k">function</span> <span class="pl-en">foo</span>() {
-  <span class="pl-k">return</span> <span class="pl-c1">true</span>;
-}</pre></div>
-
-<p><a name="testing--for-real"></a><a name="28.2"></a></p>
-</li>
-<li>
-<a href="#testing--for-real">28.2</a> <strong>No, but seriously</strong>:
-
-<ul>
-<li>Whichever testing framework you use, you should be writing tests!</li>
-<li>Strive to write many small pure functions, and minimize where mutations occur.</li>
-<li>Be cautious about stubs and mocks - they can make your tests more brittle.</li>
-<li>We primarily use <a href="https://www.npmjs.com/package/mocha"><code>mocha</code></a> at Airbnb. <a href="https://www.npmjs.com/package/tape"><code>tape</code></a> is also used occasionally for small, separate modules.</li>
-<li>100% test coverage is a good goal to strive for, even if it's not always practical to reach it.</li>
-<li>Whenever you fix a bug, <em>write a regression test</em>. A bug fixed without a regression test is almost certainly going to break again in the future.</li>
-</ul>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="performance" class="anchor" href="#performance" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Performance</h2>
-
-<ul>
-<li><a href="http://www.kellegous.com/j/2013/01/26/layout-performance/">On Layout &amp; Web Performance</a></li>
-<li><a href="http://jsperf.com/string-vs-array-concat/2">String vs Array Concat</a></li>
-<li><a href="http://jsperf.com/try-catch-in-loop-cost">Try/Catch Cost In a Loop</a></li>
-<li><a href="http://jsperf.com/bang-function">Bang Function</a></li>
-<li><a href="http://jsperf.com/jquery-find-vs-context-sel/13">jQuery Find vs Context, Selector</a></li>
-<li><a href="http://jsperf.com/innerhtml-vs-textcontent-for-script-text">innerHTML vs textContent for script text</a></li>
-<li><a href="http://jsperf.com/ya-string-concat">Long String Concatenation</a></li>
-<li><a href="https://www.quora.com/JavaScript-programming-language-Are-Javascript-functions-like-map-reduce-and-filter-already-optimized-for-traversing-array/answer/Quildreen-Motta">Are Javascript functions like <code>map()</code>, <code>reduce()</code>, and <code>filter()</code> optimized for traversing arrays?</a></li>
-<li>Loading...</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="resources" class="anchor" href="#resources" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Resources</h2>
-
-<p><strong>Learning ES6</strong></p>
-
-<ul>
-<li><a href="https://people.mozilla.org/%7Ejorendorff/es6-draft.html">Draft ECMA 2015 (ES6) Spec</a></li>
-<li><a href="http://exploringjs.com/">ExploringJS</a></li>
-<li><a href="https://kangax.github.io/compat-table/es6/">ES6 Compatibility Table</a></li>
-<li><a href="http://es6-features.org/">Comprehensive Overview of ES6 Features</a></li>
-</ul>
-
-<p><strong>Read This</strong></p>
-
-<ul>
-<li><a href="http://www.ecma-international.org/ecma-262/6.0/index.html">Standard ECMA-262</a></li>
-</ul>
-
-<p><strong>Tools</strong></p>
-
-<ul>
-<li>Code Style Linters
-
-<ul>
-<li>
-<a href="http://eslint.org/">ESlint</a> - <a href="https://github.com/airbnb/javascript/blob/master/linters/.eslintrc">Airbnb Style .eslintrc</a>
-</li>
-<li>
-<a href="http://jshint.com/">JSHint</a> - <a href="https://github.com/airbnb/javascript/blob/master/linters/.jshintrc">Airbnb Style .jshintrc</a>
-</li>
-<li>
-<a href="https://github.com/jscs-dev/node-jscs">JSCS</a> - <a href="https://github.com/jscs-dev/node-jscs/blob/master/presets/airbnb.json">Airbnb Style Preset</a>
-</li>
-</ul>
-</li>
-</ul>
-
-<p><strong>Other Style Guides</strong></p>
-
-<ul>
-<li><a href="https://google.github.io/styleguide/javascriptguide.xml">Google JavaScript Style Guide</a></li>
-<li><a href="http://contribute.jquery.org/style-guide/js/">jQuery Core Style Guidelines</a></li>
-<li><a href="https://github.com/rwaldron/idiomatic.js">Principles of Writing Consistent, Idiomatic JavaScript</a></li>
-</ul>
-
-<p><strong>Other Styles</strong></p>
-
-<ul>
-<li>
-<a href="https://gist.github.com/cjohansen/4135065">Naming this in nested functions</a> - Christian Johansen</li>
-<li>
-<a href="https://github.com/airbnb/javascript/issues/52">Conditional Callbacks</a> - Ross Allen</li>
-<li>
-<a href="http://sideeffect.kr/popularconvention/#javascript">Popular JavaScript Coding Conventions on Github</a> - JeongHoon Byun</li>
-<li>
-<a href="http://benalman.com/news/2012/05/multiple-var-statements-javascript/">Multiple var statements in JavaScript, not superfluous</a> - Ben Alman</li>
-</ul>
-
-<p><strong>Further Reading</strong></p>
-
-<ul>
-<li>
-<a href="http://javascriptweblog.wordpress.com/2010/10/25/understanding-javascript-closures/">Understanding JavaScript Closures</a> - Angus Croll</li>
-<li>
-<a href="http://www.2ality.com/2013/06/basic-javascript.html">Basic JavaScript for the impatient programmer</a> - Dr. Axel Rauschmayer</li>
-<li>
-<a href="http://youmightnotneedjquery.com/">You Might Not Need jQuery</a> - Zack Bloom &amp; Adam Schwartz</li>
-<li>
-<a href="https://github.com/lukehoban/es6features">ES6 Features</a> - Luke Hoban</li>
-<li>
-<a href="https://github.com/bendc/frontend-guidelines">Frontend Guidelines</a> - Benjamin De Cock</li>
-</ul>
-
-<p><strong>Books</strong></p>
-
-<ul>
-<li>
-<a href="http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742">JavaScript: The Good Parts</a> - Douglas Crockford</li>
-<li>
-<a href="http://www.amazon.com/JavaScript-Patterns-Stoyan-Stefanov/dp/0596806752">JavaScript Patterns</a> - Stoyan Stefanov</li>
-<li>
-<a href="http://www.amazon.com/JavaScript-Design-Patterns-Recipes-Problem-Solution/dp/159059908X">Pro JavaScript Design Patterns</a>  - Ross Harmes and Dustin Diaz</li>
-<li>
-<a href="http://www.amazon.com/High-Performance-Web-Sites-Essential/dp/0596529309">High Performance Web Sites: Essential Knowledge for Front-End Engineers</a> - Steve Souders</li>
-<li>
-<a href="http://www.amazon.com/Maintainable-JavaScript-Nicholas-C-Zakas/dp/1449327680">Maintainable JavaScript</a> - Nicholas C. Zakas</li>
-<li>
-<a href="http://www.amazon.com/JavaScript-Web-Applications-Alex-MacCaw/dp/144930351X">JavaScript Web Applications</a> - Alex MacCaw</li>
-<li>
-<a href="http://www.amazon.com/Pro-JavaScript-Techniques-John-Resig/dp/1590597273">Pro JavaScript Techniques</a> - John Resig</li>
-<li>
-<a href="http://www.amazon.com/Smashing-Node-js-JavaScript-Everywhere-Magazine/dp/1119962595">Smashing Node.js: JavaScript Everywhere</a> - Guillermo Rauch</li>
-<li>
-<a href="http://www.amazon.com/Secrets-JavaScript-Ninja-John-Resig/dp/193398869X">Secrets of the JavaScript Ninja</a> - John Resig and Bear Bibeault</li>
-<li>
-<a href="http://humanjavascript.com/">Human JavaScript</a> - Henrik Joreteg</li>
-<li>
-<a href="http://superherojs.com/">Superhero.js</a> - Kim Joar Bekkelund, Mads Mobæk, &amp; Olav Bjorkoy</li>
-<li>
-<a href="http://jsbooks.revolunet.com/">JSBooks</a> - Julien Bouquillon</li>
-<li>
-<a href="https://www.manning.com/books/third-party-javascript">Third Party JavaScript</a> - Ben Vinegar and Anton Kovalyov</li>
-<li>
-<a href="http://amzn.com/0321812182">Effective JavaScript: 68 Specific Ways to Harness the Power of JavaScript</a> - David Herman</li>
-<li>
-<a href="http://eloquentjavascript.net/">Eloquent JavaScript</a> - Marijn Haverbeke</li>
-<li>
-<a href="http://shop.oreilly.com/product/0636920033769.do">You Don't Know JS: ES6 &amp; Beyond</a> - Kyle Simpson</li>
-</ul>
-
-<p><strong>Blogs</strong></p>
-
-<ul>
-<li><a href="http://dailyjs.com/">DailyJS</a></li>
-<li><a href="http://javascriptweekly.com/">JavaScript Weekly</a></li>
-<li><a href="http://javascriptweblog.wordpress.com/">JavaScript, JavaScript...</a></li>
-<li><a href="https://bocoup.com/weblog">Bocoup Weblog</a></li>
-<li><a href="http://www.adequatelygood.com/">Adequately Good</a></li>
-<li><a href="https://www.nczonline.net/">NCZOnline</a></li>
-<li><a href="http://perfectionkills.com/">Perfection Kills</a></li>
-<li><a href="http://benalman.com/">Ben Alman</a></li>
-<li><a href="http://dmitry.baranovskiy.com/">Dmitry Baranovskiy</a></li>
-<li><a href="http://dustindiaz.com/">Dustin Diaz</a></li>
-<li><a href="http://code.tutsplus.com/?s=javascript">nettuts</a></li>
-</ul>
-
-<p><strong>Podcasts</strong></p>
-
-<ul>
-<li><a href="https://devchat.tv/js-jabber/">JavaScript Jabber</a></li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="in-the-wild" class="anchor" href="#in-the-wild" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>In the Wild</h2>
-
-<p>This is a list of organizations that are using this style guide. Send us a pull request and we'll add you to the list.</p>
-
-<ul>
-<li>
-<strong>4Catalyzer</strong>: <a href="https://github.com/4Catalyzer/javascript">4Catalyzer/javascript</a>
-</li>
-<li>
-<strong>Aan Zee</strong>: <a href="https://github.com/AanZee/javascript">AanZee/javascript</a>
-</li>
-<li>
-<strong>Adult Swim</strong>: <a href="https://github.com/adult-swim/javascript">adult-swim/javascript</a>
-</li>
-<li>
-<strong>Airbnb</strong>: <a href="https://github.com/airbnb/javascript">airbnb/javascript</a>
-</li>
-<li>
-<strong>Apartmint</strong>: <a href="https://github.com/apartmint/javascript">apartmint/javascript</a>
-</li>
-<li>
-<strong>Ascribe</strong>: <a href="https://github.com/ascribe/javascript">ascribe/javascript</a>
-</li>
-<li>
-<strong>Avalara</strong>: <a href="https://github.com/avalara/javascript">avalara/javascript</a>
-</li>
-<li>
-<strong>Avant</strong>: <a href="https://github.com/avantcredit/javascript">avantcredit/javascript</a>
-</li>
-<li>
-<strong>Billabong</strong>: <a href="https://github.com/billabong/javascript">billabong/javascript</a>
-</li>
-<li>
-<strong>Bisk</strong>: <a href="https://github.com/Bisk/javascript/">bisk/javascript</a>
-</li>
-<li>
-<strong>Blendle</strong>: <a href="https://github.com/blendle/javascript">blendle/javascript</a>
-</li>
-<li>
-<strong>Brainshark</strong>: <a href="https://github.com/brainshark/javascript">brainshark/javascript</a>
-</li>
-<li>
-<strong>Chartboost</strong>: <a href="https://github.com/ChartBoost/javascript-style-guide">ChartBoost/javascript-style-guide</a>
-</li>
-<li>
-<strong>ComparaOnline</strong>: <a href="https://github.com/comparaonline/javascript-style-guide">comparaonline/javascript</a>
-</li>
-<li>
-<strong>Compass Learning</strong>: <a href="https://github.com/compasslearning/javascript-style-guide">compasslearning/javascript-style-guide</a>
-</li>
-<li>
-<strong>DailyMotion</strong>: <a href="https://github.com/dailymotion/javascript">dailymotion/javascript</a>
-</li>
-<li>
-<strong>DoSomething</strong>: <a href="https://github.com/DoSomething/eslint-config">DoSomething/eslint-config</a>
-</li>
-<li>
-<strong>Digitpaint</strong> <a href="https://github.com/digitpaint/javascript">digitpaint/javascript</a>
-</li>
-<li>
-<strong>Ecosia</strong>: <a href="https://github.com/ecosia/javascript">ecosia/javascript</a>
-</li>
-<li>
-<strong>Evernote</strong>: <a href="https://github.com/evernote/javascript-style-guide">evernote/javascript-style-guide</a>
-</li>
-<li>
-<strong>Evolution Gaming</strong>: <a href="https://github.com/evolution-gaming/javascript">evolution-gaming/javascript</a>
-</li>
-<li>
-<strong>EvozonJs</strong>: <a href="https://github.com/evozonjs/javascript">evozonjs/javascript</a>
-</li>
-<li>
-<strong>ExactTarget</strong>: <a href="https://github.com/ExactTarget/javascript">ExactTarget/javascript</a>
-</li>
-<li>
-<strong>Expensify</strong> <a href="https://github.com/Expensify/Style-Guide/blob/master/javascript.md">Expensify/Style-Guide</a>
-</li>
-<li>
-<strong>Flexberry</strong>: <a href="https://github.com/Flexberry/javascript-style-guide">Flexberry/javascript-style-guide</a>
-</li>
-<li>
-<strong>Gawker Media</strong>: <a href="https://github.com/gawkermedia/javascript">gawkermedia/javascript</a>
-</li>
-<li>
-<strong>General Electric</strong>: <a href="https://github.com/GeneralElectric/javascript">GeneralElectric/javascript</a>
-</li>
-<li>
-<strong>GoodData</strong>: <a href="https://github.com/gooddata/gdc-js-style">gooddata/gdc-js-style</a>
-</li>
-<li>
-<strong>Grooveshark</strong>: <a href="https://github.com/grooveshark/javascript">grooveshark/javascript</a>
-</li>
-<li>
-<strong>How About We</strong>: <a href="https://github.com/howaboutwe/javascript-style-guide">howaboutwe/javascript</a>
-</li>
-<li>
-<strong>Huballin</strong>: <a href="https://github.com/huballin/javascript">huballin/javascript</a>
-</li>
-<li>
-<strong>HubSpot</strong>: <a href="https://github.com/HubSpot/javascript">HubSpot/javascript</a>
-</li>
-<li>
-<strong>Hyper</strong>: <a href="https://github.com/hyperoslo/javascript-playbook/blob/master/style.md">hyperoslo/javascript-playbook</a>
-</li>
-<li>
-<strong>InfoJobs</strong>: <a href="https://github.com/InfoJobs/JavaScript-Style-Guide">InfoJobs/JavaScript-Style-Guide</a>
-</li>
-<li>
-<strong>Intent Media</strong>: <a href="https://github.com/intentmedia/javascript">intentmedia/javascript</a>
-</li>
-<li>
-<strong>Jam3</strong>: <a href="https://github.com/Jam3/Javascript-Code-Conventions">Jam3/Javascript-Code-Conventions</a>
-</li>
-<li>
-<strong>JeopardyBot</strong>: <a href="https://github.com/kesne/jeopardy-bot/blob/master/STYLEGUIDE.md">kesne/jeopardy-bot</a>
-</li>
-<li>
-<strong>JSSolutions</strong>: <a href="https://github.com/JSSolutions/javascript">JSSolutions/javascript</a>
-</li>
-<li>
-<strong>KickorStick</strong>: <a href="https://github.com/kickorstick/javascript">kickorstick/javascript</a>
-</li>
-<li>
-<strong>Kinetica Solutions</strong>: <a href="https://github.com/kinetica/Javascript-style-guide">kinetica/javascript</a>
-</li>
-<li>
-<strong>Mighty Spring</strong>: <a href="https://github.com/mightyspring/javascript">mightyspring/javascript</a>
-</li>
-<li>
-<strong>MinnPost</strong>: <a href="https://github.com/MinnPost/javascript">MinnPost/javascript</a>
-</li>
-<li>
-<strong>MitocGroup</strong>: <a href="https://github.com/MitocGroup/javascript">MitocGroup/javascript</a>
-</li>
-<li>
-<strong>ModCloth</strong>: <a href="https://github.com/modcloth/javascript">modcloth/javascript</a>
-</li>
-<li>
-<strong>Money Advice Service</strong>: <a href="https://github.com/moneyadviceservice/javascript">moneyadviceservice/javascript</a>
-</li>
-<li>
-<strong>Muber</strong>: <a href="https://github.com/muber/javascript">muber/javascript</a>
-</li>
-<li>
-<strong>National Geographic</strong>: <a href="https://github.com/natgeo/javascript">natgeo/javascript</a>
-</li>
-<li>
-<strong>National Park Service</strong>: <a href="https://github.com/nationalparkservice/javascript">nationalparkservice/javascript</a>
-</li>
-<li>
-<strong>Nimbl3</strong>: <a href="https://github.com/nimbl3/javascript">nimbl3/javascript</a>
-</li>
-<li>
-<strong>Orion Health</strong>: <a href="https://github.com/orionhealth/javascript">orionhealth/javascript</a>
-</li>
-<li>
-<strong>OutBoxSoft</strong>: <a href="https://github.com/OutBoxSoft/javascript">OutBoxSoft/javascript</a>
-</li>
-<li>
-<strong>Peerby</strong>: <a href="https://github.com/Peerby/javascript">Peerby/javascript</a>
-</li>
-<li>
-<strong>Razorfish</strong>: <a href="https://github.com/razorfish/javascript-style-guide">razorfish/javascript-style-guide</a>
-</li>
-<li>
-<strong>reddit</strong>: <a href="https://github.com/reddit/styleguide/tree/master/javascript">reddit/styleguide/javascript</a>
-</li>
-<li>
-<strong>React</strong>: <a href="https://github.com/facebook/react/blob/master/CONTRIBUTING.md#style-guide">/facebook/react/blob/master/CONTRIBUTING.md#style-guide</a>
-</li>
-<li>
-<strong>REI</strong>: <a href="https://github.com/rei/code-style-guides/blob/master/docs/javascript.md">reidev/js-style-guide</a>
-</li>
-<li>
-<strong>Ripple</strong>: <a href="https://github.com/ripple/javascript-style-guide">ripple/javascript-style-guide</a>
-</li>
-<li>
-<strong>SeekingAlpha</strong>: <a href="https://github.com/seekingalpha/javascript-style-guide">seekingalpha/javascript-style-guide</a>
-</li>
-<li>
-<strong>Shutterfly</strong>: <a href="https://github.com/shutterfly/javascript">shutterfly/javascript</a>
-</li>
-<li>
-<strong>Springload</strong>: <a href="https://github.com/springload/javascript">springload/javascript</a>
-</li>
-<li>
-<strong>StudentSphere</strong>: <a href="https://github.com/studentsphere/guide-javascript">studentsphere/javascript</a>
-</li>
-<li>
-<strong>SysGarage</strong>: <a href="https://github.com/sysgarage/javascript-style-guide">sysgarage/javascript-style-guide</a>
-</li>
-<li>
-<strong>Target</strong>: <a href="https://github.com/target/javascript">target/javascript</a>
-</li>
-<li>
-<strong>TheLadders</strong>: <a href="https://github.com/TheLadders/javascript">TheLadders/javascript</a>
-</li>
-<li>
-<strong>The Nerdery</strong>: <a href="https://github.com/thenerdery/javascript-standards">thenerdery/javascript-standards</a>
-</li>
-<li>
-<strong>T4R Technology</strong>: <a href="https://github.com/T4R-Technology/javascript">T4R-Technology/javascript</a>
-</li>
-<li>
-<strong>VoxFeed</strong>: <a href="https://github.com/VoxFeed/javascript-style-guide">VoxFeed/javascript-style-guide</a>
-</li>
-<li>
-<strong>WeBox Studio</strong>: <a href="https://github.com/weboxstudio/javascript">weboxstudio/javascript</a>
-</li>
-<li>
-<strong>Weggo</strong>: <a href="https://github.com/Weggo/javascript">Weggo/javascript</a>
-</li>
-<li>
-<strong>Zillow</strong>: <a href="https://github.com/zillow/javascript">zillow/javascript</a>
-</li>
-<li>
-<strong>ZocDoc</strong>: <a href="https://github.com/ZocDoc/javascript">ZocDoc/javascript</a>
-</li>
-</ul>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="translation" class="anchor" href="#translation" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Translation</h2>
-
-<p>This style guide is also available in other languages:</p>
-
-<ul>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Brazil.png" alt="br"> <strong>Brazilian Portuguese</strong>: <a href="https://github.com/armoucar/javascript-style-guide">armoucar/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Bulgaria.png" alt="bg"> <strong>Bulgarian</strong>: <a href="https://github.com/borislavvv/javascript">borislavvv/javascript</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/fpmweb/javascript-style-guide/master/img/catala.png" alt="ca"> <strong>Catalan</strong>: <a href="https://github.com/fpmweb/javascript-style-guide">fpmweb/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/China.png" alt="cn"> <strong>Chinese (Simplified)</strong>: <a href="https://github.com/sivan/javascript-style-guide">sivan/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Taiwan.png" alt="tw"> <strong>Chinese (Traditional)</strong>: <a href="https://github.com/jigsawye/javascript">jigsawye/javascript</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/France.png" alt="fr"> <strong>French</strong>: <a href="https://github.com/nmussy/javascript-style-guide">nmussy/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Germany.png" alt="de"> <strong>German</strong>: <a href="https://github.com/timofurrer/javascript-style-guide">timofurrer/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Italy.png" alt="it"> <strong>Italian</strong>: <a href="https://github.com/sinkswim/javascript-style-guide">sinkswim/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Japan.png" alt="jp"> <strong>Japanese</strong>: <a href="https://github.com/mitsuruog/javacript-style-guide">mitsuruog/javacript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/South-Korea.png" alt="kr"> <strong>Korean</strong>: <a href="https://github.com/tipjs/javascript-style-guide">tipjs/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Poland.png" alt="pl"> <strong>Polish</strong>: <a href="https://github.com/mjurczyk/javascript">mjurczyk/javascript</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Russia.png" alt="ru"> <strong>Russian</strong>: <a href="https://github.com/uprock/javascript">uprock/javascript</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Spain.png" alt="es"> <strong>Spanish</strong>: <a href="https://github.com/paolocarrasco/javascript-style-guide">paolocarrasco/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Thailand.png" alt="th"> <strong>Thai</strong>: <a href="https://github.com/lvarayut/javascript-style-guide">lvarayut/javascript-style-guide</a>
-</li>
-<li>
-<img src="https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Vietnam.png" alt="vn"> <strong>Vietnam</strong>: <a href="https://github.com/giangpii/javascript-style-guide">giangpii/javascript-style-guide</a>
-</li>
-</ul>
-
-<h2>
-<a id="the-javascript-style-guide-guide" class="anchor" href="#the-javascript-style-guide-guide" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>The JavaScript Style Guide Guide</h2>
-
-<ul>
-<li><a href="https://github.com/airbnb/javascript/wiki/The-JavaScript-Style-Guide-Guide">Reference</a></li>
-</ul>
-
-<h2>
-<a id="chat-with-us-about-javascript" class="anchor" href="#chat-with-us-about-javascript" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Chat With Us About JavaScript</h2>
-
-<ul>
-<li>Find us on <a href="https://gitter.im/airbnb/javascript">gitter</a>.</li>
-</ul>
-
-<h2>
-<a id="contributors" class="anchor" href="#contributors" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Contributors</h2>
-
-<ul>
-<li><a href="https://github.com/airbnb/javascript/graphs/contributors">View Contributors</a></li>
-</ul>
-
-<h2>
-<a id="license" class="anchor" href="#license" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>License</h2>
-
-<p>(The MIT License)</p>
-
-<p>Copyright (c) 2014-2016 Airbnb</p>
-
-<p>Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-'Software'), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:</p>
-
-<p>The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.</p>
-
-<p>THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
-
-<p><strong><a href="#table-of-contents">⬆ back to top</a></strong></p>
-
-<h2>
-<a id="amendments" class="anchor" href="#amendments" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Amendments</h2>
-
-<p>We encourage you to fork this guide and change the rules to fit your team's style guide. Below, you may list some amendments to the style guide. This allows you to periodically update your style guide without having to deal with merge conflicts.</p>
-
-<h1>
-<a id="" class="anchor" href="#" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>};</h1>
-
-      <footer class="site-footer">
-        <span class="site-footer-owner"><a href="https://github.com/airbnb/javascript">Airbnb JavaScript Style Guide</a> is maintained by <a href="https://github.com/airbnb">airbnb</a>.</span>
-
-        <span class="site-footer-credits">This page was generated by <a href="https://pages.github.com">GitHub Pages</a> using the <a href="https://github.com/jasonlong/cayman-theme">Cayman theme</a> by <a href="https://twitter.com/jasonlong">Jason Long</a>.</span>
-      </footer>
-
-    </section>
-
-  
-  </body>
-</html>
diff --git a/index.md b/index.md
new file mode 100644
index 00000000..e316eb73
--- /dev/null
+++ b/index.md
@@ -0,0 +1,2976 @@
+# Airbnb JavaScript Style Guide() {
+
+*A mostly reasonable approach to JavaScript*
+
+[![Downloads](https://img.shields.io/npm/dm/eslint-config-airbnb.svg)](https://www.npmjs.com/package/eslint-config-airbnb)
+[![Downloads](https://img.shields.io/npm/dm/eslint-config-airbnb-base.svg)](https://www.npmjs.com/package/eslint-config-airbnb-base)
+[![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/airbnb/javascript?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
+
+Other Style Guides
+ - [ES5](es5/)
+ - [React](react/)
+ - [CSS & Sass](https://github.com/airbnb/css)
+ - [Ruby](https://github.com/airbnb/ruby)
+
+## Table of Contents
+
+  1. [Types](#types)
+  1. [References](#references)
+  1. [Objects](#objects)
+  1. [Arrays](#arrays)
+  1. [Destructuring](#destructuring)
+  1. [Strings](#strings)
+  1. [Functions](#functions)
+  1. [Arrow Functions](#arrow-functions)
+  1. [Classes & Constructors](#classes--constructors)
+  1. [Modules](#modules)
+  1. [Iterators and Generators](#iterators-and-generators)
+  1. [Properties](#properties)
+  1. [Variables](#variables)
+  1. [Hoisting](#hoisting)
+  1. [Comparison Operators & Equality](#comparison-operators--equality)
+  1. [Blocks](#blocks)
+  1. [Comments](#comments)
+  1. [Whitespace](#whitespace)
+  1. [Commas](#commas)
+  1. [Semicolons](#semicolons)
+  1. [Type Casting & Coercion](#type-casting--coercion)
+  1. [Naming Conventions](#naming-conventions)
+  1. [Accessors](#accessors)
+  1. [Events](#events)
+  1. [jQuery](#jquery)
+  1. [ECMAScript 5 Compatibility](#ecmascript-5-compatibility)
+  1. [ECMAScript 6 Styles](#ecmascript-6-styles)
+  1. [Testing](#testing)
+  1. [Performance](#performance)
+  1. [Resources](#resources)
+  1. [In the Wild](#in-the-wild)
+  1. [Translation](#translation)
+  1. [The JavaScript Style Guide Guide](#the-javascript-style-guide-guide)
+  1. [Chat With Us About JavaScript](#chat-with-us-about-javascript)
+  1. [Contributors](#contributors)
+  1. [License](#license)
+
+## Types
+
+  <a name="types--primitives"></a><a name="1.1"></a>
+  - [1.1](#types--primitives) **Primitives**: When you access a primitive type you work directly on its value.
+
+    + `string`
+    + `number`
+    + `boolean`
+    + `null`
+    + `undefined`
+
+    ```javascript
+    const foo = 1;
+    let bar = foo;
+
+    bar = 9;
+
+    console.log(foo, bar); // => 1, 9
+    ```
+
+  <a name="types--complex"></a><a name="1.2"></a>
+  - [1.2](#types--complex)  **Complex**: When you access a complex type you work on a reference to its value.
+
+    + `object`
+    + `array`
+    + `function`
+
+    ```javascript
+    const foo = [1, 2];
+    const bar = foo;
+
+    bar[0] = 9;
+
+    console.log(foo[0], bar[0]); // => 9, 9
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+## References
+
+  <a name="references--prefer-const"></a><a name="2.1"></a>
+  - [2.1](#references--prefer-const) Use `const` for all of your references; avoid using `var`. eslint: [`prefer-const`](http://eslint.org/docs/rules/prefer-const.html), [`no-const-assign`](http://eslint.org/docs/rules/no-const-assign.html)
+
+    > Why? This ensures that you can't reassign your references, which can lead to bugs and difficult to comprehend code.
+
+    ```javascript
+    // bad
+    var a = 1;
+    var b = 2;
+
+    // good
+    const a = 1;
+    const b = 2;
+    ```
+
+  <a name="references--disallow-var"></a><a name="2.2"></a>
+  - [2.2](#references--disallow-var) If you must reassign references, use `let` instead of `var`. eslint: [`no-var`](http://eslint.org/docs/rules/no-var.html) jscs: [`disallowVar`](http://jscs.info/rule/disallowVar)
+
+    > Why? `let` is block-scoped rather than function-scoped like `var`.
+
+    ```javascript
+    // bad
+    var count = 1;
+    if (true) {
+      count += 1;
+    }
+
+    // good, use the let.
+    let count = 1;
+    if (true) {
+      count += 1;
+    }
+    ```
+
+  <a name="references--block-scope"></a><a name="2.3"></a>
+  - [2.3](#references--block-scope) Note that both `let` and `const` are block-scoped.
+
+    ```javascript
+    // const and let only exist in the blocks they are defined in.
+    {
+      let a = 1;
+      const b = 1;
+    }
+    console.log(a); // ReferenceError
+    console.log(b); // ReferenceError
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+## Objects
+
+  <a name="objects--no-new"></a><a name="3.1"></a>
+  - [3.1](#objects--no-new) Use the literal syntax for object creation. eslint: [`no-new-object`](http://eslint.org/docs/rules/no-new-object.html)
+
+    ```javascript
+    // bad
+    const item = new Object();
+
+    // good
+    const item = {};
+    ```
+
+  <a name="objects--reserved-words"></a><a name="3.2"></a>
+  - [3.2](#objects--reserved-words) If your code will be executed in browsers in script context, don't use [reserved words](http://es5.github.io/#x7.6.1) as keys. It won't work in IE8. [More info](https://github.com/airbnb/javascript/issues/61). It’s OK to use them in ES6 modules and server-side code. jscs: [`disallowIdentifierNames`](http://jscs.info/rule/disallowIdentifierNames)
+
+    ```javascript
+    // bad
+    const superman = {
+      default: { clark: 'kent' },
+      private: true,
+    };
+
+    // good
+    const superman = {
+      defaults: { clark: 'kent' },
+      hidden: true,
+    };
+    ```
+
+  <a name="objects--reserved-words-2"></a><a name="3.3"></a>
+  - [3.3](#objects--reserved-words-2) Use readable synonyms in place of reserved words. jscs: [`disallowIdentifierNames`](http://jscs.info/rule/disallowIdentifierNames)
+
+    ```javascript
+    // bad
+    const superman = {
+      class: 'alien',
+    };
+
+    // bad
+    const superman = {
+      klass: 'alien',
+    };
+
+    // good
+    const superman = {
+      type: 'alien',
+    };
+    ```
+
+  <a name="es6-computed-properties"></a><a name="3.4"></a>
+  - [3.4](#es6-computed-properties) Use computed property names when creating objects with dynamic property names.
+
+    > Why? They allow you to define all the properties of an object in one place.
+
+    ```javascript
+
+    function getKey(k) {
+      return `a key named ${k}`;
+    }
+
+    // bad
+    const obj = {
+      id: 5,
+      name: 'San Francisco',
+    };
+    obj[getKey('enabled')] = true;
+
+    // good
+    const obj = {
+      id: 5,
+      name: 'San Francisco',
+      [getKey('enabled')]: true,
+    };
+    ```
+
+  <a name="es6-object-shorthand"></a><a name="3.5"></a>
+  - [3.5](#es6-object-shorthand) Use object method shorthand. eslint: [`object-shorthand`](http://eslint.org/docs/rules/object-shorthand.html) jscs: [`requireEnhancedObjectLiterals`](http://jscs.info/rule/requireEnhancedObjectLiterals)
+
+    ```javascript
+    // bad
+    const atom = {
+      value: 1,
+
+      addValue: function (value) {
+        return atom.value + value;
+      },
+    };
+
+    // good
+    const atom = {
+      value: 1,
+
+      addValue(value) {
+        return atom.value + value;
+      },
+    };
+    ```
+
+  <a name="es6-object-concise"></a><a name="3.6"></a>
+  - [3.6](#es6-object-concise) Use property value shorthand. eslint: [`object-shorthand`](http://eslint.org/docs/rules/object-shorthand.html) jscs: [`requireEnhancedObjectLiterals`](http://jscs.info/rule/requireEnhancedObjectLiterals)
+
+    > Why? It is shorter to write and descriptive.
+
+    ```javascript
+    const lukeSkywalker = 'Luke Skywalker';
+
+    // bad
+    const obj = {
+      lukeSkywalker: lukeSkywalker,
+    };
+
+    // good
+    const obj = {
+      lukeSkywalker,
+    };
+    ```
+
+  <a name="objects--grouped-shorthand"></a><a name="3.7"></a>
+  - [3.7](#objects--grouped-shorthand) Group your shorthand properties at the beginning of your object declaration.
+
+    > Why? It's easier to tell which properties are using the shorthand.
+
+    ```javascript
+    const anakinSkywalker = 'Anakin Skywalker';
+    const lukeSkywalker = 'Luke Skywalker';
+
+    // bad
+    const obj = {
+      episodeOne: 1,
+      twoJediWalkIntoACantina: 2,
+      lukeSkywalker,
+      episodeThree: 3,
+      mayTheFourth: 4,
+      anakinSkywalker,
+    };
+
+    // good
+    const obj = {
+      lukeSkywalker,
+      anakinSkywalker,
+      episodeOne: 1,
+      twoJediWalkIntoACantina: 2,
+      episodeThree: 3,
+      mayTheFourth: 4,
+    };
+    ```
+
+  <a name="objects--quoted-props"></a><a name="3.8"></a>
+  - [3.8](#objects--quoted-props) Only quote properties that are invalid identifiers. eslint: [`quote-props`](http://eslint.org/docs/rules/quote-props.html) jscs: [`disallowQuotedKeysInObjects`](http://jscs.info/rule/disallowQuotedKeysInObjects)
+
+  > Why? In general we consider it subjectively easier to read. It improves syntax highlighting, and is also more easily optimized by many JS engines.
+
+  ```javascript
+  // bad
+  const bad = {
+    'foo': 3,
+    'bar': 4,
+    'data-blah': 5,
+  };
+
+  // good
+  const good = {
+    foo: 3,
+    bar: 4,
+    'data-blah': 5,
+  };
+  ```
+
+  <a name="objects--prototype-builtins"></a>
+  - [3.9](#objects--prototype-builtins) Do not call `Object.prototype` methods directly, such as `hasOwnProperty`, `propertyIsEnumerable`, and `isPrototypeOf`.
+
+  > Why? These methods may be shadowed by properties on the object in question - consider `{ hasOwnProperty: false }` - or, the object may be a null object (`Object.create(null)`).
+
+  ```javascript
+  // bad
+  console.log(object.hasOwnProperty(key));
+
+  // good
+  console.log(Object.prototype.hasOwnProperty.call(object, key));
+
+  // best
+  const has = Object.prototype.hasOwnProperty; // cache the lookup once, in module scope.
+  /* or */
+  const has = require('has');
+  …
+  console.log(has.call(object, key));
+  ```
+
+**[⬆ back to top](#table-of-contents)**
+
+## Arrays
+
+  <a name="arrays--literals"></a><a name="4.1"></a>
+  - [4.1](#arrays--literals) Use the literal syntax for array creation. eslint: [`no-array-constructor`](http://eslint.org/docs/rules/no-array-constructor.html)
+
+    ```javascript
+    // bad
+    const items = new Array();
+
+    // good
+    const items = [];
+    ```
+
+  <a name="arrays--push"></a><a name="4.2"></a>
+  - [4.2](#arrays--push) Use [Array#push](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/push) instead of direct assignment to add items to an array.
+
+    ```javascript
+    const someStack = [];
+
+    // bad
+    someStack[someStack.length] = 'abracadabra';
+
+    // good
+    someStack.push('abracadabra');
+    ```
+
+  <a name="es6-array-spreads"></a><a name="4.3"></a>
+  - [4.3](#es6-array-spreads) Use array spreads `...` to copy arrays.
+
+    ```javascript
+    // bad
+    const len = items.length;
+    const itemsCopy = [];
+    let i;
+
+    for (i = 0; i < len; i++) {
+      itemsCopy[i] = items[i];
+    }
+
+    // good
+    const itemsCopy = [...items];
+    ```
+
+  <a name="arrays--from"></a><a name="4.4"></a>
+  - [4.4](#arrays--from) To convert an array-like object to an array, use [Array.from](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/from).
+
+    ```javascript
+    const foo = document.querySelectorAll('.foo');
+    const nodes = Array.from(foo);
+    ```
+
+  <a name="arrays--callback-return"></a><a name="4.5"></a>
+  - [4.5](#arrays--callback-return) Use return statements in array method callbacks. It's ok to omit the return if the function body consists of a single statement following [8.2](#8.2). eslint: [`array-callback-return`](http://eslint.org/docs/rules/array-callback-return)
+
+    ```javascript
+    // good
+    [1, 2, 3].map((x) => {
+      const y = x + 1;
+      return x * y;
+    });
+
+    // good
+    [1, 2, 3].map(x => x + 1);
+
+    // bad
+    const flat = {};
+    [[0, 1], [2, 3], [4, 5]].reduce((memo, item, index) => {
+      const flatten = memo.concat(item);
+      flat[index] = flatten;
+    });
+
+    // good
+    const flat = {};
+    [[0, 1], [2, 3], [4, 5]].reduce((memo, item, index) => {
+      const flatten = memo.concat(item);
+      flat[index] = flatten;
+      return flatten;
+    });
+
+    // bad
+    inbox.filter((msg) => {
+      const { subject, author } = msg;
+      if (subject === 'Mockingbird') {
+        return author === 'Harper Lee';
+      } else {
+        return false;
+      }
+    });
+
+    // good
+    inbox.filter((msg) => {
+      const { subject, author } = msg;
+      if (subject === 'Mockingbird') {
+        return author === 'Harper Lee';
+      }
+
+      return false;
+    });
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+## Destructuring
+
+  <a name="destructuring--object"></a><a name="5.1"></a>
+  - [5.1](#destructuring--object) Use object destructuring when accessing and using multiple properties of an object. jscs: [`requireObjectDestructuring`](http://jscs.info/rule/requireObjectDestructuring)
+
+    > Why? Destructuring saves you from creating temporary references for those properties.
+
+    ```javascript
+    // bad
+    function getFullName(user) {
+      const firstName = user.firstName;
+      const lastName = user.lastName;
+
+      return `${firstName} ${lastName}`;
+    }
+
+    // good
+    function getFullName(user) {
+      const { firstName, lastName } = user;
+      return `${firstName} ${lastName}`;
+    }
+
+    // best
+    function getFullName({ firstName, lastName }) {
+      return `${firstName} ${lastName}`;
+    }
+    ```
+
+  <a name="destructuring--array"></a><a name="5.2"></a>
+  - [5.2](#destructuring--array) Use array destructuring. jscs: [`requireArrayDestructuring`](http://jscs.info/rule/requireArrayDestructuring)
+
+    ```javascript
+    const arr = [1, 2, 3, 4];
+
+    // bad
+    const first = arr[0];
+    const second = arr[1];
+
+    // good
+    const [first, second] = arr;
+    ```
+
+  <a name="destructuring--object-over-array"></a><a name="5.3"></a>
+  - [5.3](#destructuring--object-over-array) Use object destructuring for multiple return values, not array destructuring. jscs: [`disallowArrayDestructuringReturn`](http://jscs.info/rule/disallowArrayDestructuringReturn)
+
+    > Why? You can add new properties over time or change the order of things without breaking call sites.
+
+    ```javascript
+    // bad
+    function processInput(input) {
+      // then a miracle occurs
+      return [left, right, top, bottom];
+    }
+
+    // the caller needs to think about the order of return data
+    const [left, __, top] = processInput(input);
+
+    // good
+    function processInput(input) {
+      // then a miracle occurs
+      return { left, right, top, bottom };
+    }
+
+    // the caller selects only the data they need
+    const { left, top } = processInput(input);
+    ```
+
+
+**[⬆ back to top](#table-of-contents)**
+
+## Strings
+
+  <a name="strings--quotes"></a><a name="6.1"></a>
+  - [6.1](#strings--quotes) Use single quotes `''` for strings. eslint: [`quotes`](http://eslint.org/docs/rules/quotes.html) jscs: [`validateQuoteMarks`](http://jscs.info/rule/validateQuoteMarks)
+
+    ```javascript
+    // bad
+    const name = "Capt. Janeway";
+
+    // good
+    const name = 'Capt. Janeway';
+    ```
+
+  <a name="strings--line-length"></a><a name="6.2"></a>
+  - [6.2](#strings--line-length) Strings that cause the line to go over 100 characters should be written across multiple lines using string concatenation.
+
+  <a name="strings--concat-perf"></a><a name="6.3"></a>
+  - [6.3](#strings--concat-perf) Note: If overused, long strings with concatenation could impact performance. [jsPerf](http://jsperf.com/ya-string-concat) & [Discussion](https://github.com/airbnb/javascript/issues/40).
+
+    ```javascript
+    // bad
+    const errorMessage = 'This is a super long error that was thrown because of Batman. When you stop to think about how Batman had anything to do with this, you would get nowhere fast.';
+
+    // bad
+    const errorMessage = 'This is a super long error that was thrown because \
+    of Batman. When you stop to think about how Batman had anything to do \
+    with this, you would get nowhere \
+    fast.';
+
+    // good
+    const errorMessage = 'This is a super long error that was thrown because ' +
+      'of Batman. When you stop to think about how Batman had anything to do ' +
+      'with this, you would get nowhere fast.';
+    ```
+
+  <a name="es6-template-literals"></a><a name="6.4"></a>
+  - [6.4](#es6-template-literals) When programmatically building up strings, use template strings instead of concatenation. eslint: [`prefer-template`](http://eslint.org/docs/rules/prefer-template.html) [`template-curly-spacing`](http://eslint.org/docs/rules/template-curly-spacing) jscs: [`requireTemplateStrings`](http://jscs.info/rule/requireTemplateStrings)
+
+    > Why? Template strings give you a readable, concise syntax with proper newlines and string interpolation features.
+
+    ```javascript
+    // bad
+    function sayHi(name) {
+      return 'How are you, ' + name + '?';
+    }
+
+    // bad
+    function sayHi(name) {
+      return ['How are you, ', name, '?'].join();
+    }
+
+    // bad
+    function sayHi(name) {
+      return `How are you, ${ name }?`;
+    }
+
+    // good
+    function sayHi(name) {
+      return `How are you, ${name}?`;
+    }
+    ```
+
+  <a name="strings--eval"></a><a name="6.5"></a>
+  - [6.5](#strings--eval) Never use `eval()` on a string, it opens too many vulnerabilities.
+
+  <a name="strings--escaping"></a>
+  - [6.6](#strings--escaping) Do not unnecessarily escape characters in strings. eslint: [`no-useless-escape`](http://eslint.org/docs/rules/no-useless-escape)
+
+    > Why? Backslashes harm readability, thus they should only be present when necessary.
+
+    ```javascript
+    // bad
+    const foo = '\'this\' \i\s \"quoted\"';
+
+    // good
+    const foo = '\'this\' is "quoted"';
+    const foo = `'this' is "quoted"`;
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Functions
+
+  <a name="functions--declarations"></a><a name="7.1"></a>
+  - [7.1](#functions--declarations) Use function declarations instead of function expressions. jscs: [`requireFunctionDeclarations`](http://jscs.info/rule/requireFunctionDeclarations)
+
+    > Why? Function declarations are named, so they're easier to identify in call stacks. Also, the whole body of a function declaration is hoisted, whereas only the reference of a function expression is hoisted. This rule makes it possible to always use [Arrow Functions](#arrow-functions) in place of function expressions.
+
+    ```javascript
+    // bad
+    const foo = function () {
+    };
+
+    // good
+    function foo() {
+    }
+    ```
+
+  <a name="functions--iife"></a><a name="7.2"></a>
+  - [7.2](#functions--iife) Wrap immediately invoked function expressions in parentheses. eslint: [`wrap-iife`](http://eslint.org/docs/rules/wrap-iife.html) jscs: [`requireParenthesesAroundIIFE`](http://jscs.info/rule/requireParenthesesAroundIIFE)
+
+    > Why? An immediately invoked function expression is a single unit - wrapping both it, and its invocation parens, in parens, cleanly expresses this. Note that in a world with modules everywhere, you almost never need an IIFE.
+
+    ```javascript
+    // immediately-invoked function expression (IIFE)
+    (function () {
+      console.log('Welcome to the Internet. Please follow me.');
+    }());
+    ```
+
+  <a name="functions--in-blocks"></a><a name="7.3"></a>
+  - [7.3](#functions--in-blocks) Never declare a function in a non-function block (if, while, etc). Assign the function to a variable instead. Browsers will allow you to do it, but they all interpret it differently, which is bad news bears. eslint: [`no-loop-func`](http://eslint.org/docs/rules/no-loop-func.html)
+
+  <a name="functions--note-on-blocks"></a><a name="7.4"></a>
+  - [7.4](#functions--note-on-blocks) **Note:** ECMA-262 defines a `block` as a list of statements. A function declaration is not a statement. [Read ECMA-262's note on this issue](http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf#page=97).
+
+    ```javascript
+    // bad
+    if (currentUser) {
+      function test() {
+        console.log('Nope.');
+      }
+    }
+
+    // good
+    let test;
+    if (currentUser) {
+      test = () => {
+        console.log('Yup.');
+      };
+    }
+    ```
+
+  <a name="functions--arguments-shadow"></a><a name="7.5"></a>
+  - [7.5](#functions--arguments-shadow) Never name a parameter `arguments`. This will take precedence over the `arguments` object that is given to every function scope.
+
+    ```javascript
+    // bad
+    function nope(name, options, arguments) {
+      // ...stuff...
+    }
+
+    // good
+    function yup(name, options, args) {
+      // ...stuff...
+    }
+    ```
+
+  <a name="es6-rest"></a><a name="7.6"></a>
+  - [7.6](#es6-rest) Never use `arguments`, opt to use rest syntax `...` instead. eslint: [`prefer-rest-params`](http://eslint.org/docs/rules/prefer-rest-params)
+
+    > Why? `...` is explicit about which arguments you want pulled. Plus, rest arguments are a real Array, and not merely Array-like like `arguments`.
+
+    ```javascript
+    // bad
+    function concatenateAll() {
+      const args = Array.prototype.slice.call(arguments);
+      return args.join('');
+    }
+
+    // good
+    function concatenateAll(...args) {
+      return args.join('');
+    }
+    ```
+
+  <a name="es6-default-parameters"></a><a name="7.7"></a>
+  - [7.7](#es6-default-parameters) Use default parameter syntax rather than mutating function arguments.
+
+    ```javascript
+    // really bad
+    function handleThings(opts) {
+      // No! We shouldn't mutate function arguments.
+      // Double bad: if opts is falsy it'll be set to an object which may
+      // be what you want but it can introduce subtle bugs.
+      opts = opts || {};
+      // ...
+    }
+
+    // still bad
+    function handleThings(opts) {
+      if (opts === void 0) {
+        opts = {};
+      }
+      // ...
+    }
+
+    // good
+    function handleThings(opts = {}) {
+      // ...
+    }
+    ```
+
+  <a name="functions--default-side-effects"></a><a name="7.8"></a>
+  - [7.8](#functions--default-side-effects) Avoid side effects with default parameters.
+
+    > Why? They are confusing to reason about.
+
+    ```javascript
+    var b = 1;
+    // bad
+    function count(a = b++) {
+      console.log(a);
+    }
+    count();  // 1
+    count();  // 2
+    count(3); // 3
+    count();  // 3
+    ```
+
+  <a name="functions--defaults-last"></a><a name="7.9"></a>
+  - [7.9](#functions--defaults-last) Always put default parameters last.
+
+    ```javascript
+    // bad
+    function handleThings(opts = {}, name) {
+      // ...
+    }
+
+    // good
+    function handleThings(name, opts = {}) {
+      // ...
+    }
+    ```
+
+  <a name="functions--constructor"></a><a name="7.10"></a>
+  - [7.10](#functions--constructor) Never use the Function constructor to create a new function.
+
+    > Why? Creating a function in this way evaluates a string similarly to eval(), which opens vulnerabilities.
+
+    ```javascript
+    // bad
+    var add = new Function('a', 'b', 'return a + b');
+
+    // still bad
+    var subtract = Function('a', 'b', 'return a - b');
+    ```
+
+  <a name="functions--signature-spacing"></a><a name="7.11"></a>
+  - [7.11](#functions--signature-spacing) Spacing in a function signature.
+
+    > Why? Consistency is good, and you shouldn’t have to add or remove a space when adding or removing a name.
+
+    ```javascript
+    // bad
+    const f = function(){};
+    const g = function (){};
+    const h = function() {};
+
+    // good
+    const x = function () {};
+    const y = function a() {};
+    ```
+
+  <a name="functions--mutate-params"></a><a name="7.12"></a>
+  - [7.12](#functions--mutate-params) Never mutate parameters. eslint: [`no-param-reassign`](http://eslint.org/docs/rules/no-param-reassign.html)
+
+    > Why? Manipulating objects passed in as parameters can cause unwanted variable side effects in the original caller.
+
+    ```javascript
+    // bad
+    function f1(obj) {
+      obj.key = 1;
+    };
+
+    // good
+    function f2(obj) {
+      const key = Object.prototype.hasOwnProperty.call(obj, 'key') ? obj.key : 1;
+    };
+    ```
+
+  <a name="functions--reassign-params"></a><a name="7.13"></a>
+  - [7.13](#functions--reassign-params) Never reassign parameters. eslint: [`no-param-reassign`](http://eslint.org/docs/rules/no-param-reassign.html)
+
+    > Why? Reassigning parameters can lead to unexpected behavior, especially when accessing the `arguments` object. It can also cause optimization issues, especially in V8.
+
+    ```javascript
+    // bad
+    function f1(a) {
+      a = 1;
+    }
+
+    function f2(a) {
+      if (!a) { a = 1; }
+    }
+
+    // good
+    function f3(a) {
+      const b = a || 1;
+    }
+
+    function f4(a = 1) {
+    }
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+## Arrow Functions
+
+  <a name="arrows--use-them"></a><a name="8.1"></a>
+  - [8.1](#arrows--use-them) When you must use function expressions (as when passing an anonymous function), use arrow function notation. eslint: [`prefer-arrow-callback`](http://eslint.org/docs/rules/prefer-arrow-callback.html), [`arrow-spacing`](http://eslint.org/docs/rules/arrow-spacing.html) jscs: [`requireArrowFunctions`](http://jscs.info/rule/requireArrowFunctions)
+
+    > Why? It creates a version of the function that executes in the context of `this`, which is usually what you want, and is a more concise syntax.
+
+    > Why not? If you have a fairly complicated function, you might move that logic out into its own function declaration.
+
+    ```javascript
+    // bad
+    [1, 2, 3].map(function (x) {
+      const y = x + 1;
+      return x * y;
+    });
+
+    // good
+    [1, 2, 3].map((x) => {
+      const y = x + 1;
+      return x * y;
+    });
+    ```
+
+  <a name="arrows--implicit-return"></a><a name="8.2"></a>
+  - [8.2](#arrows--implicit-return) If the function body consists of a single expression, omit the braces and use the implicit return. Otherwise, keep the braces and use a `return` statement. eslint: [`arrow-parens`](http://eslint.org/docs/rules/arrow-parens.html), [`arrow-body-style`](http://eslint.org/docs/rules/arrow-body-style.html) jscs:  [`disallowParenthesesAroundArrowParam`](http://jscs.info/rule/disallowParenthesesAroundArrowParam), [`requireShorthandArrowFunctions`](http://jscs.info/rule/requireShorthandArrowFunctions)
+
+    > Why? Syntactic sugar. It reads well when multiple functions are chained together.
+
+    ```javascript
+    // bad
+    [1, 2, 3].map(number => {
+      const nextNumber = number + 1;
+      `A string containing the ${nextNumber}.`;
+    });
+
+    // good
+    [1, 2, 3].map(number => `A string containing the ${number}.`);
+
+    // good
+    [1, 2, 3].map((number) => {
+      const nextNumber = number + 1;
+      return `A string containing the ${nextNumber}.`;
+    });
+
+    // good
+    [1, 2, 3].map((number, index) => ({
+      index: number
+    }));
+    ```
+
+  <a name="arrows--paren-wrap"></a><a name="8.3"></a>
+  - [8.3](#arrows--paren-wrap) In case the expression spans over multiple lines, wrap it in parentheses for better readability.
+
+    > Why? It shows clearly where the function starts and ends.
+
+    ```js
+    // bad
+    [1, 2, 3].map(number => 'As time went by, the string containing the ' +
+      `${number} became much longer. So we needed to break it over multiple ` +
+      'lines.'
+    );
+
+    // good
+    [1, 2, 3].map(number => (
+      `As time went by, the string containing the ${number} became much ` +
+      'longer. So we needed to break it over multiple lines.'
+    ));
+    ```
+
+  <a name="arrows--one-arg-parens"></a><a name="8.4"></a>
+  - [8.4](#arrows--one-arg-parens) If your function takes a single argument and doesn’t use braces, omit the parentheses. Otherwise, always include parentheses around arguments. eslint: [`arrow-parens`](http://eslint.org/docs/rules/arrow-parens.html) jscs:  [`disallowParenthesesAroundArrowParam`](http://jscs.info/rule/disallowParenthesesAroundArrowParam)
+
+    > Why? Less visual clutter.
+
+    ```js
+    // bad
+    [1, 2, 3].map((x) => x * x);
+
+    // good
+    [1, 2, 3].map(x => x * x);
+
+    // good
+    [1, 2, 3].map(number => (
+      `A long string with the ${number}. It’s so long that we’ve broken it ` +
+      'over multiple lines!'
+    ));
+
+    // bad
+    [1, 2, 3].map(x => {
+      const y = x + 1;
+      return x * y;
+    });
+
+    // good
+    [1, 2, 3].map((x) => {
+      const y = x + 1;
+      return x * y;
+    });
+    ```
+
+  <a name="arrows--confusing"></a><a name="8.5"></a>
+  - [8.5](#arrows--confusing) Avoid confusing arrow function syntax (`=>`) with comparison operators (`<=`, `>=`). eslint: [`no-confusing-arrow`](http://eslint.org/docs/rules/no-confusing-arrow)
+
+    ```js
+    // bad
+    const itemHeight = item => item.height > 256 ? item.largeSize : item.smallSize;
+
+    // bad
+    const itemHeight = (item) => item.height > 256 ? item.largeSize : item.smallSize;
+
+    // good
+    const itemHeight = (item) => { return item.height > 256 ? item.largeSize : item.smallSize; };
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Classes & Constructors
+
+  <a name="constructors--use-class"></a><a name="9.1"></a>
+  - [9.1](#constructors--use-class) Always use `class`. Avoid manipulating `prototype` directly.
+
+    > Why? `class` syntax is more concise and easier to reason about.
+
+    ```javascript
+    // bad
+    function Queue(contents = []) {
+      this.queue = [...contents];
+    }
+    Queue.prototype.pop = function () {
+      const value = this.queue[0];
+      this.queue.splice(0, 1);
+      return value;
+    };
+
+
+    // good
+    class Queue {
+      constructor(contents = []) {
+        this.queue = [...contents];
+      }
+      pop() {
+        const value = this.queue[0];
+        this.queue.splice(0, 1);
+        return value;
+      }
+    }
+    ```
+
+  <a name="constructors--extends"></a><a name="9.2"></a>
+  - [9.2](#constructors--extends) Use `extends` for inheritance.
+
+    > Why? It is a built-in way to inherit prototype functionality without breaking `instanceof`.
+
+    ```javascript
+    // bad
+    const inherits = require('inherits');
+    function PeekableQueue(contents) {
+      Queue.apply(this, contents);
+    }
+    inherits(PeekableQueue, Queue);
+    PeekableQueue.prototype.peek = function () {
+      return this._queue[0];
+    }
+
+    // good
+    class PeekableQueue extends Queue {
+      peek() {
+        return this._queue[0];
+      }
+    }
+    ```
+
+  <a name="constructors--chaining"></a><a name="9.3"></a>
+  - [9.3](#constructors--chaining) Methods can return `this` to help with method chaining.
+
+    ```javascript
+    // bad
+    Jedi.prototype.jump = function () {
+      this.jumping = true;
+      return true;
+    };
+
+    Jedi.prototype.setHeight = function (height) {
+      this.height = height;
+    };
+
+    const luke = new Jedi();
+    luke.jump(); // => true
+    luke.setHeight(20); // => undefined
+
+    // good
+    class Jedi {
+      jump() {
+        this.jumping = true;
+        return this;
+      }
+
+      setHeight(height) {
+        this.height = height;
+        return this;
+      }
+    }
+
+    const luke = new Jedi();
+
+    luke.jump()
+      .setHeight(20);
+    ```
+
+
+  <a name="constructors--tostring"></a><a name="9.4"></a>
+  - [9.4](#constructors--tostring) It's okay to write a custom toString() method, just make sure it works successfully and causes no side effects.
+
+    ```javascript
+    class Jedi {
+      constructor(options = {}) {
+        this.name = options.name || 'no name';
+      }
+
+      getName() {
+        return this.name;
+      }
+
+      toString() {
+        return `Jedi - ${this.getName()}`;
+      }
+    }
+    ```
+
+  <a name="constructors--no-useless"></a><a name="9.5"></a>
+  - [9.5](#constructors--no-useless) Classes have a default constructor if one is not specified. An empty constructor function or one that just delegates to a parent class is unnecessary. eslint: [`no-useless-constructor`](http://eslint.org/docs/rules/no-useless-constructor)
+
+    ```javascript
+    // bad
+    class Jedi {
+      constructor() {}
+
+      getName() {
+        return this.name;
+      }
+    }
+
+    // bad
+    class Rey extends Jedi {
+      constructor(...args) {
+        super(...args);
+      }
+    }
+
+    // good
+    class Rey extends Jedi {
+      constructor(...args) {
+        super(...args);
+        this.name = 'Rey';
+      }
+    }
+    ```
+
+  <a name="classes--no-duplicate-members"></a>
+  - [9.6](#classes--no-duplicate-members) Avoid duplicate class members. eslint: [`no-dupe-class-members`](http://eslint.org/docs/rules/no-dupe-class-members)
+
+    > Why? Duplicate class member declarations will silently prefer the last one - having duplicates is almost certainly a bug.
+
+    ```javascript
+    // bad
+    class Foo {
+      bar() { return 1; }
+      bar() { return 2; }
+    }
+
+    // good
+    class Foo {
+      bar() { return 1; }
+    }
+
+    // good
+    class Foo {
+      bar() { return 2; }
+    }
+    ```
+
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Modules
+
+  <a name="modules--use-them"></a><a name="10.1"></a>
+  - [10.1](#modules--use-them) Always use modules (`import`/`export`) over a non-standard module system. You can always transpile to your preferred module system.
+
+    > Why? Modules are the future, let's start using the future now.
+
+    ```javascript
+    // bad
+    const AirbnbStyleGuide = require('./AirbnbStyleGuide');
+    module.exports = AirbnbStyleGuide.es6;
+
+    // ok
+    import AirbnbStyleGuide from './AirbnbStyleGuide';
+    export default AirbnbStyleGuide.es6;
+
+    // best
+    import { es6 } from './AirbnbStyleGuide';
+    export default es6;
+    ```
+
+  <a name="modules--no-wildcard"></a><a name="10.2"></a>
+  - [10.2](#modules--no-wildcard) Do not use wildcard imports.
+
+    > Why? This makes sure you have a single default export.
+
+    ```javascript
+    // bad
+    import * as AirbnbStyleGuide from './AirbnbStyleGuide';
+
+    // good
+    import AirbnbStyleGuide from './AirbnbStyleGuide';
+    ```
+
+  <a name="modules--no-export-from-import"></a><a name="10.3"></a>
+  - [10.3](#modules--no-export-from-import) And do not export directly from an import.
+
+    > Why? Although the one-liner is concise, having one clear way to import and one clear way to export makes things consistent.
+
+    ```javascript
+    // bad
+    // filename es6.js
+    export { es6 as default } from './airbnbStyleGuide';
+
+    // good
+    // filename es6.js
+    import { es6 } from './AirbnbStyleGuide';
+    export default es6;
+    ```
+
+  <a name="modules--no-duplicate-imports"></a>
+  - [10.4](#modules--no-duplicate-imports) Only import from a path in one place.
+ eslint: [`no-duplicate-imports`](http://eslint.org/docs/rules/no-duplicate-imports)
+    > Why? Having multiple lines that import from the same path can make code harder to maintain.
+
+    ```javascript
+    // bad
+    import foo from 'foo';
+    // … some other imports … //
+    import { named1, named2 } from 'foo';
+
+    // good
+    import foo, { named1, named2 } from 'foo';
+
+    // good
+    import foo, {
+      named1,
+      named2,
+    } from 'foo';
+    ```
+
+  <a name="modules--no-mutable-exports"></a>
+  - [10.5](#modules--no-mutable-exports) Do not export mutable bindings.
+ eslint: [`import/no-mutable-exports`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-mutable-exports.md)
+    > Why? Mutation should be avoided in general, but in particular when exporting mutable bindings. While this technique may be needed for some special cases, in general, only constant references should be exported.
+
+    ```javascript
+    // bad
+    let foo = 3;
+    export { foo }
+
+    // good
+    const foo = 3;
+    export { foo }
+    ```
+
+  <a name="modules--prefer-default-export"></a>
+  - [10.6](#modules--prefer-default-export) In modules with a single export, prefer default export over named export.
+ eslint: [`import/prefer-default-export`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/prefer-default-export.md)
+
+    ```javascript
+    // bad
+    export function foo() {}
+
+    // good
+    export default function foo() {}
+    ```
+
+  <a name="modules--imports-first"></a>
+  - [10.7](#modules--imports-first) Put all `import`s above non-import statements.
+ eslint: [`import/imports-first`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/imports-first.md)
+    > Why? Since `import`s are hoisted, keeping them all at the top prevents surprising behavior.
+
+    ```javascript
+    // bad
+    import foo from 'foo';
+    foo.init();
+
+    import bar from 'bar';
+
+    // good
+    import foo from 'foo';
+    import bar from 'bar';
+
+    foo.init();
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+## Iterators and Generators
+
+  <a name="iterators--nope"></a><a name="11.1"></a>
+  - [11.1](#iterators--nope) Don't use iterators. Prefer JavaScript's higher-order functions like `map()` and `reduce()` instead of loops like `for-of`. eslint: [`no-iterator`](http://eslint.org/docs/rules/no-iterator.html)
+
+    > Why? This enforces our immutable rule. Dealing with pure functions that return values is easier to reason about than side effects.
+
+    ```javascript
+    const numbers = [1, 2, 3, 4, 5];
+
+    // bad
+    let sum = 0;
+    for (let num of numbers) {
+      sum += num;
+    }
+
+    sum === 15;
+
+    // good
+    let sum = 0;
+    numbers.forEach(num => sum += num);
+    sum === 15;
+
+    // best (use the functional force)
+    const sum = numbers.reduce((total, num) => total + num, 0);
+    sum === 15;
+    ```
+
+  <a name="generators--nope"></a><a name="11.2"></a>
+  - [11.2](#generators--nope) Don't use generators for now.
+
+    > Why? They don't transpile well to ES5.
+
+  <a name="generators--spacing"></a>
+  - [11.3](#generators--spacing) If you must use generators, or if you disregard [our advice](#generators--nope), make sure their function signature is spaced properly. eslint: [`generator-star-spacing`](http://eslint.org/docs/rules/generator-star-spacing)
+
+    > Why? `function` and `*` are part of the same conceptual keyword - `*` is not a modifier for `function`, `function*` is a unique construct, different from `function`.
+
+    ```js
+    // bad
+    function * foo() {
+    }
+
+    const bar = function * () {
+    }
+
+    const baz = function *() {
+    }
+
+    const quux = function*() {
+    }
+
+    function*foo() {
+    }
+
+    function *foo() {
+    }
+
+    // very bad
+    function
+    *
+    foo() {
+    }
+
+    const wat = function
+    *
+    () {
+    }
+
+    // good
+    function* foo() {
+    }
+
+    const foo = function* () {
+    }
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Properties
+
+  <a name="properties--dot"></a><a name="12.1"></a>
+  - [12.1](#properties--dot) Use dot notation when accessing properties. eslint: [`dot-notation`](http://eslint.org/docs/rules/dot-notation.html) jscs: [`requireDotNotation`](http://jscs.info/rule/requireDotNotation)
+
+    ```javascript
+    const luke = {
+      jedi: true,
+      age: 28,
+    };
+
+    // bad
+    const isJedi = luke['jedi'];
+
+    // good
+    const isJedi = luke.jedi;
+    ```
+
+  <a name="properties--bracket"></a><a name="12.2"></a>
+  - [12.2](#properties--bracket) Use bracket notation `[]` when accessing properties with a variable.
+
+    ```javascript
+    const luke = {
+      jedi: true,
+      age: 28,
+    };
+
+    function getProp(prop) {
+      return luke[prop];
+    }
+
+    const isJedi = getProp('jedi');
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Variables
+
+  <a name="variables--const"></a><a name="13.1"></a>
+  - [13.1](#variables--const) Always use `const` to declare variables. Not doing so will result in global variables. We want to avoid polluting the global namespace. Captain Planet warned us of that.
+
+    ```javascript
+    // bad
+    superPower = new SuperPower();
+
+    // good
+    const superPower = new SuperPower();
+    ```
+
+  <a name="variables--one-const"></a><a name="13.2"></a>
+  - [13.2](#variables--one-const) Use one `const` declaration per variable. eslint: [`one-var`](http://eslint.org/docs/rules/one-var.html) jscs: [`disallowMultipleVarDecl`](http://jscs.info/rule/disallowMultipleVarDecl)
+
+    > Why? It's easier to add new variable declarations this way, and you never have to worry about swapping out a `;` for a `,` or introducing punctuation-only diffs. You can also step through each declaration with the debugger, instead of jumping through all of them at once.
+
+    ```javascript
+    // bad
+    const items = getItems(),
+        goSportsTeam = true,
+        dragonball = 'z';
+
+    // bad
+    // (compare to above, and try to spot the mistake)
+    const items = getItems(),
+        goSportsTeam = true;
+        dragonball = 'z';
+
+    // good
+    const items = getItems();
+    const goSportsTeam = true;
+    const dragonball = 'z';
+    ```
+
+  <a name="variables--const-let-group"></a><a name="13.3"></a>
+  - [13.3](#variables--const-let-group) Group all your `const`s and then group all your `let`s.
+
+    > Why? This is helpful when later on you might need to assign a variable depending on one of the previous assigned variables.
+
+    ```javascript
+    // bad
+    let i, len, dragonball,
+        items = getItems(),
+        goSportsTeam = true;
+
+    // bad
+    let i;
+    const items = getItems();
+    let dragonball;
+    const goSportsTeam = true;
+    let len;
+
+    // good
+    const goSportsTeam = true;
+    const items = getItems();
+    let dragonball;
+    let i;
+    let length;
+    ```
+
+  <a name="variables--define-where-used"></a><a name="13.4"></a>
+  - [13.4](#variables--define-where-used) Assign variables where you need them, but place them in a reasonable place.
+
+    > Why? `let` and `const` are block scoped and not function scoped.
+
+    ```javascript
+    // bad - unnecessary function call
+    function checkName(hasName) {
+      const name = getName();
+
+      if (hasName === 'test') {
+        return false;
+      }
+
+      if (name === 'test') {
+        this.setName('');
+        return false;
+      }
+
+      return name;
+    }
+
+    // good
+    function checkName(hasName) {
+      if (hasName === 'test') {
+        return false;
+      }
+
+      const name = getName();
+
+      if (name === 'test') {
+        this.setName('');
+        return false;
+      }
+
+      return name;
+    }
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Hoisting
+
+  <a name="hoisting--about"></a><a name="14.1"></a>
+  - [14.1](#hoisting--about) `var` declarations get hoisted to the top of their scope, their assignment does not. `const` and `let` declarations are blessed with a new concept called [Temporal Dead Zones (TDZ)](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let#Temporal_dead_zone_and_errors_with_let). It's important to know why [typeof is no longer safe](http://es-discourse.com/t/why-typeof-is-no-longer-safe/15).
+
+    ```javascript
+    // we know this wouldn't work (assuming there
+    // is no notDefined global variable)
+    function example() {
+      console.log(notDefined); // => throws a ReferenceError
+    }
+
+    // creating a variable declaration after you
+    // reference the variable will work due to
+    // variable hoisting. Note: the assignment
+    // value of `true` is not hoisted.
+    function example() {
+      console.log(declaredButNotAssigned); // => undefined
+      var declaredButNotAssigned = true;
+    }
+
+    // the interpreter is hoisting the variable
+    // declaration to the top of the scope,
+    // which means our example could be rewritten as:
+    function example() {
+      let declaredButNotAssigned;
+      console.log(declaredButNotAssigned); // => undefined
+      declaredButNotAssigned = true;
+    }
+
+    // using const and let
+    function example() {
+      console.log(declaredButNotAssigned); // => throws a ReferenceError
+      console.log(typeof declaredButNotAssigned); // => throws a ReferenceError
+      const declaredButNotAssigned = true;
+    }
+    ```
+
+  <a name="hoisting--anon-expressions"></a><a name="14.2"></a>
+  - [14.2](#hoisting--anon-expressions) Anonymous function expressions hoist their variable name, but not the function assignment.
+
+    ```javascript
+    function example() {
+      console.log(anonymous); // => undefined
+
+      anonymous(); // => TypeError anonymous is not a function
+
+      var anonymous = function () {
+        console.log('anonymous function expression');
+      };
+    }
+    ```
+
+  <a name="hoisting--named-expresions"></a><a name="14.3"></a>
+  - [14.3](#hoisting--named-expresions) Named function expressions hoist the variable name, not the function name or the function body.
+
+    ```javascript
+    function example() {
+      console.log(named); // => undefined
+
+      named(); // => TypeError named is not a function
+
+      superPower(); // => ReferenceError superPower is not defined
+
+      var named = function superPower() {
+        console.log('Flying');
+      };
+    }
+
+    // the same is true when the function name
+    // is the same as the variable name.
+    function example() {
+      console.log(named); // => undefined
+
+      named(); // => TypeError named is not a function
+
+      var named = function named() {
+        console.log('named');
+      }
+    }
+    ```
+
+  <a name="hoisting--declarations"></a><a name="14.4"></a>
+  - [14.4](#hoisting--declarations) Function declarations hoist their name and the function body.
+
+    ```javascript
+    function example() {
+      superPower(); // => Flying
+
+      function superPower() {
+        console.log('Flying');
+      }
+    }
+    ```
+
+  - For more information refer to [JavaScript Scoping & Hoisting](http://www.adequatelygood.com/2010/2/JavaScript-Scoping-and-Hoisting/) by [Ben Cherry](http://www.adequatelygood.com/).
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Comparison Operators & Equality
+
+  <a name="comparison--eqeqeq"></a><a name="15.1"></a>
+  - [15.1](#comparison--eqeqeq) Use `===` and `!==` over `==` and `!=`. eslint: [`eqeqeq`](http://eslint.org/docs/rules/eqeqeq.html)
+
+  <a name="comparison--if"></a><a name="15.2"></a>
+  - [15.2](#comparison--if) Conditional statements such as the `if` statement evaluate their expression using coercion with the `ToBoolean` abstract method and always follow these simple rules:
+
+    + **Objects** evaluate to **true**
+    + **Undefined** evaluates to **false**
+    + **Null** evaluates to **false**
+    + **Booleans** evaluate to **the value of the boolean**
+    + **Numbers** evaluate to **false** if **+0, -0, or NaN**, otherwise **true**
+    + **Strings** evaluate to **false** if an empty string `''`, otherwise **true**
+
+    ```javascript
+    if ([0] && []) {
+      // true
+      // an array (even an empty one) is an object, objects will evaluate to true
+    }
+    ```
+
+  <a name="comparison--shortcuts"></a><a name="15.3"></a>
+  - [15.3](#comparison--shortcuts) Use shortcuts.
+
+    ```javascript
+    // bad
+    if (name !== '') {
+      // ...stuff...
+    }
+
+    // good
+    if (name) {
+      // ...stuff...
+    }
+
+    // bad
+    if (collection.length > 0) {
+      // ...stuff...
+    }
+
+    // good
+    if (collection.length) {
+      // ...stuff...
+    }
+    ```
+
+  <a name="comparison--moreinfo"></a><a name="15.4"></a>
+  - [15.4](#comparison--moreinfo) For more information see [Truth Equality and JavaScript](http://javascriptweblog.wordpress.com/2011/02/07/truth-equality-and-javascript/#more-2108) by Angus Croll.
+
+  <a name="comparison--switch-blocks"></a><a name="15.5"></a>
+  - [15.5](#comparison--switch-blocks) Use braces to create blocks in `case` and `default` clauses that contain lexical declarations (e.g. `let`, `const`, `function`, and `class`).
+
+  > Why? Lexical declarations are visible in the entire `switch` block but only get initialized when assigned, which only happens when its `case` is reached. This causes problems when multiple `case` clauses attempt to define the same thing.
+
+  eslint rules: [`no-case-declarations`](http://eslint.org/docs/rules/no-case-declarations.html).
+
+    ```javascript
+    // bad
+    switch (foo) {
+      case 1:
+        let x = 1;
+        break;
+      case 2:
+        const y = 2;
+        break;
+      case 3:
+        function f() {}
+        break;
+      default:
+        class C {}
+    }
+
+    // good
+    switch (foo) {
+      case 1: {
+        let x = 1;
+        break;
+      }
+      case 2: {
+        const y = 2;
+        break;
+      }
+      case 3: {
+        function f() {}
+        break;
+      }
+      case 4:
+        bar();
+        break;
+      default: {
+        class C {}
+      }
+    }
+    ```
+
+  <a name="comparison--nested-ternaries"></a><a name="15.6"></a>
+  - [15.6](#comparison--nested-ternaries) Ternaries should not be nested and generally be single line expressions.
+
+    eslint rules: [`no-nested-ternary`](http://eslint.org/docs/rules/no-nested-ternary.html).
+
+    ```javascript
+    // bad
+    const foo = maybe1 > maybe2
+      ? "bar"
+      : value1 > value2 ? "baz" : null;
+
+    // better
+    const maybeNull = value1 > value2 ? 'baz' : null;
+
+    const foo = maybe1 > maybe2
+      ? 'bar'
+      : maybeNull;
+
+    // best
+    const maybeNull = value1 > value2 ? 'baz' : null;
+
+    const foo = maybe1 > maybe2 ? 'bar' : maybeNull;
+    ```
+
+  <a name="comparison--unneeded-ternary"></a><a name="15.7"></a>
+  - [15.7](#comparison--unneeded-ternary) Avoid unneeded ternary statements.
+
+    eslint rules: [`no-unneeded-ternary`](http://eslint.org/docs/rules/no-unneeded-ternary.html).
+
+    ```javascript
+    // bad
+    const foo = a ? a : b;
+    const bar = c ? true : false;
+    const baz = c ? false : true;
+
+    // good
+    const foo = a || b;
+    const bar = !!c;
+    const baz = !c;
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Blocks
+
+  <a name="blocks--braces"></a><a name="16.1"></a>
+  - [16.1](#blocks--braces) Use braces with all multi-line blocks.
+
+    ```javascript
+    // bad
+    if (test)
+      return false;
+
+    // good
+    if (test) return false;
+
+    // good
+    if (test) {
+      return false;
+    }
+
+    // bad
+    function foo() { return false; }
+
+    // good
+    function bar() {
+      return false;
+    }
+    ```
+
+  <a name="blocks--cuddled-elses"></a><a name="16.2"></a>
+  - [16.2](#blocks--cuddled-elses) If you're using multi-line blocks with `if` and `else`, put `else` on the same line as your `if` block's closing brace. eslint: [`brace-style`](http://eslint.org/docs/rules/brace-style.html) jscs:  [`disallowNewlineBeforeBlockStatements`](http://jscs.info/rule/disallowNewlineBeforeBlockStatements)
+
+    ```javascript
+    // bad
+    if (test) {
+      thing1();
+      thing2();
+    }
+    else {
+      thing3();
+    }
+
+    // good
+    if (test) {
+      thing1();
+      thing2();
+    } else {
+      thing3();
+    }
+    ```
+
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Comments
+
+  <a name="comments--multiline"></a><a name="17.1"></a>
+  - [17.1](#comments--multiline) Use `/** ... */` for multi-line comments. Include a description, specify types and values for all parameters and return values.
+
+    ```javascript
+    // bad
+    // make() returns a new element
+    // based on the passed in tag name
+    //
+    // @param {String} tag
+    // @return {Element} element
+    function make(tag) {
+
+      // ...stuff...
+
+      return element;
+    }
+
+    // good
+    /**
+     * make() returns a new element
+     * based on the passed in tag name
+     *
+     * @param {String} tag
+     * @return {Element} element
+     */
+    function make(tag) {
+
+      // ...stuff...
+
+      return element;
+    }
+    ```
+
+  <a name="comments--singleline"></a><a name="17.2"></a>
+  - [17.2](#comments--singleline) Use `//` for single line comments. Place single line comments on a newline above the subject of the comment. Put an empty line before the comment unless it's on the first line of a block.
+
+    ```javascript
+    // bad
+    const active = true;  // is current tab
+
+    // good
+    // is current tab
+    const active = true;
+
+    // bad
+    function getType() {
+      console.log('fetching type...');
+      // set the default type to 'no type'
+      const type = this._type || 'no type';
+
+      return type;
+    }
+
+    // good
+    function getType() {
+      console.log('fetching type...');
+
+      // set the default type to 'no type'
+      const type = this._type || 'no type';
+
+      return type;
+    }
+
+    // also good
+    function getType() {
+      // set the default type to 'no type'
+      const type = this._type || 'no type';
+
+      return type;
+    }
+    ```
+
+  <a name="comments--actionitems"></a><a name="17.3"></a>
+  - [17.3](#comments--actionitems) Prefixing your comments with `FIXME` or `TODO` helps other developers quickly understand if you're pointing out a problem that needs to be revisited, or if you're suggesting a solution to the problem that needs to be implemented. These are different than regular comments because they are actionable. The actions are `FIXME: -- need to figure this out` or `TODO: -- need to implement`.
+
+  <a name="comments--fixme"></a><a name="17.4"></a>
+  - [17.4](#comments--fixme) Use `// FIXME:` to annotate problems.
+
+    ```javascript
+    class Calculator extends Abacus {
+      constructor() {
+        super();
+
+        // FIXME: shouldn't use a global here
+        total = 0;
+      }
+    }
+    ```
+
+  <a name="comments--todo"></a><a name="17.5"></a>
+  - [17.5](#comments--todo) Use `// TODO:` to annotate solutions to problems.
+
+    ```javascript
+    class Calculator extends Abacus {
+      constructor() {
+        super();
+
+        // TODO: total should be configurable by an options param
+        this.total = 0;
+      }
+    }
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Whitespace
+
+  <a name="whitespace--spaces"></a><a name="18.1"></a>
+  - [18.1](#whitespace--spaces) Use soft tabs set to 2 spaces. eslint: [`indent`](http://eslint.org/docs/rules/indent.html) jscs: [`validateIndentation`](http://jscs.info/rule/validateIndentation)
+
+    ```javascript
+    // bad
+    function foo() {
+    ∙∙∙∙const name;
+    }
+
+    // bad
+    function bar() {
+    ∙const name;
+    }
+
+    // good
+    function baz() {
+    ∙∙const name;
+    }
+    ```
+
+  <a name="whitespace--before-blocks"></a><a name="18.2"></a>
+  - [18.2](#whitespace--before-blocks) Place 1 space before the leading brace. eslint: [`space-before-blocks`](http://eslint.org/docs/rules/space-before-blocks.html) jscs: [`requireSpaceBeforeBlockStatements`](http://jscs.info/rule/requireSpaceBeforeBlockStatements)
+
+    ```javascript
+    // bad
+    function test(){
+      console.log('test');
+    }
+
+    // good
+    function test() {
+      console.log('test');
+    }
+
+    // bad
+    dog.set('attr',{
+      age: '1 year',
+      breed: 'Bernese Mountain Dog',
+    });
+
+    // good
+    dog.set('attr', {
+      age: '1 year',
+      breed: 'Bernese Mountain Dog',
+    });
+    ```
+
+  <a name="whitespace--around-keywords"></a><a name="18.3"></a>
+  - [18.3](#whitespace--around-keywords) Place 1 space before the opening parenthesis in control statements (`if`, `while` etc.). Place no space between the argument list and the function name in function calls and declarations. eslint: [`keyword-spacing`](http://eslint.org/docs/rules/keyword-spacing.html) jscs: [`requireSpaceAfterKeywords`](http://jscs.info/rule/requireSpaceAfterKeywords)
+
+    ```javascript
+    // bad
+    if(isJedi) {
+      fight ();
+    }
+
+    // good
+    if (isJedi) {
+      fight();
+    }
+
+    // bad
+    function fight () {
+      console.log ('Swooosh!');
+    }
+
+    // good
+    function fight() {
+      console.log('Swooosh!');
+    }
+    ```
+
+  <a name="whitespace--infix-ops"></a><a name="18.4"></a>
+  - [18.4](#whitespace--infix-ops) Set off operators with spaces. eslint: [`space-infix-ops`](http://eslint.org/docs/rules/space-infix-ops.html) jscs: [`requireSpaceBeforeBinaryOperators`](http://jscs.info/rule/requireSpaceBeforeBinaryOperators), [`requireSpaceAfterBinaryOperators`](http://jscs.info/rule/requireSpaceAfterBinaryOperators)
+
+    ```javascript
+    // bad
+    const x=y+5;
+
+    // good
+    const x = y + 5;
+    ```
+
+  <a name="whitespace--newline-at-end"></a><a name="18.5"></a>
+  - [18.5](#whitespace--newline-at-end) End files with a single newline character.
+
+    ```javascript
+    // bad
+    (function (global) {
+      // ...stuff...
+    })(this);
+    ```
+
+    ```javascript
+    // bad
+    (function (global) {
+      // ...stuff...
+    })(this);↵
+    ↵
+    ```
+
+    ```javascript
+    // good
+    (function (global) {
+      // ...stuff...
+    })(this);↵
+    ```
+
+  <a name="whitespace--chains"></a><a name="18.6"></a>
+  - [18.6](#whitespace--chains) Use indentation when making long method chains (more than 2 method chains). Use a leading dot, which
+    emphasizes that the line is a method call, not a new statement. eslint: [`newline-per-chained-call`](http://eslint.org/docs/rules/newline-per-chained-call) [`no-whitespace-before-property`](http://eslint.org/docs/rules/no-whitespace-before-property)
+
+    ```javascript
+    // bad
+    $('#items').find('.selected').highlight().end().find('.open').updateCount();
+
+    // bad
+    $('#items').
+      find('.selected').
+        highlight().
+        end().
+      find('.open').
+        updateCount();
+
+    // good
+    $('#items')
+      .find('.selected')
+        .highlight()
+        .end()
+      .find('.open')
+        .updateCount();
+
+    // bad
+    const leds = stage.selectAll('.led').data(data).enter().append('svg:svg').classed('led', true)
+        .attr('width', (radius + margin) * 2).append('svg:g')
+        .attr('transform', 'translate(' + (radius + margin) + ',' + (radius + margin) + ')')
+        .call(tron.led);
+
+    // good
+    const leds = stage.selectAll('.led')
+        .data(data)
+      .enter().append('svg:svg')
+        .classed('led', true)
+        .attr('width', (radius + margin) * 2)
+      .append('svg:g')
+        .attr('transform', 'translate(' + (radius + margin) + ',' + (radius + margin) + ')')
+        .call(tron.led);
+
+    // good
+    const leds = stage.selectAll('.led').data(data);
+    ```
+
+  <a name="whitespace--after-blocks"></a><a name="18.7"></a>
+  - [18.7](#whitespace--after-blocks) Leave a blank line after blocks and before the next statement. jscs: [`requirePaddingNewLinesAfterBlocks`](http://jscs.info/rule/requirePaddingNewLinesAfterBlocks)
+
+    ```javascript
+    // bad
+    if (foo) {
+      return bar;
+    }
+    return baz;
+
+    // good
+    if (foo) {
+      return bar;
+    }
+
+    return baz;
+
+    // bad
+    const obj = {
+      foo() {
+      },
+      bar() {
+      },
+    };
+    return obj;
+
+    // good
+    const obj = {
+      foo() {
+      },
+
+      bar() {
+      },
+    };
+
+    return obj;
+
+    // bad
+    const arr = [
+      function foo() {
+      },
+      function bar() {
+      },
+    ];
+    return arr;
+
+    // good
+    const arr = [
+      function foo() {
+      },
+
+      function bar() {
+      },
+    ];
+
+    return arr;
+    ```
+
+  <a name="whitespace--padded-blocks"></a><a name="18.8"></a>
+  - [18.8](#whitespace--padded-blocks) Do not pad your blocks with blank lines. eslint: [`padded-blocks`](http://eslint.org/docs/rules/padded-blocks.html) jscs:  [`disallowPaddingNewlinesInBlocks`](http://jscs.info/rule/disallowPaddingNewlinesInBlocks)
+
+    ```javascript
+    // bad
+    function bar() {
+
+      console.log(foo);
+
+    }
+
+    // also bad
+    if (baz) {
+
+      console.log(qux);
+    } else {
+      console.log(foo);
+
+    }
+
+    // good
+    function bar() {
+      console.log(foo);
+    }
+
+    // good
+    if (baz) {
+      console.log(qux);
+    } else {
+      console.log(foo);
+    }
+    ```
+
+  <a name="whitespace--in-parens"></a><a name="18.9"></a>
+  - [18.9](#whitespace--in-parens) Do not add spaces inside parentheses. eslint: [`space-in-parens`](http://eslint.org/docs/rules/space-in-parens.html) jscs: [`disallowSpacesInsideParentheses`](http://jscs.info/rule/disallowSpacesInsideParentheses)
+
+    ```javascript
+    // bad
+    function bar( foo ) {
+      return foo;
+    }
+
+    // good
+    function bar(foo) {
+      return foo;
+    }
+
+    // bad
+    if ( foo ) {
+      console.log(foo);
+    }
+
+    // good
+    if (foo) {
+      console.log(foo);
+    }
+    ```
+
+  <a name="whitespace--in-brackets"></a><a name="18.10"></a>
+  - [18.10](#whitespace--in-brackets) Do not add spaces inside brackets. eslint: [`array-bracket-spacing`](http://eslint.org/docs/rules/array-bracket-spacing.html) jscs: [`disallowSpacesInsideArrayBrackets`](http://jscs.info/rule/disallowSpacesInsideArrayBrackets)
+
+    ```javascript
+    // bad
+    const foo = [ 1, 2, 3 ];
+    console.log(foo[ 0 ]);
+
+    // good
+    const foo = [1, 2, 3];
+    console.log(foo[0]);
+    ```
+
+  <a name="whitespace--in-braces"></a><a name="18.11"></a>
+  - [18.11](#whitespace--in-braces) Add spaces inside curly braces. eslint: [`object-curly-spacing`](http://eslint.org/docs/rules/object-curly-spacing.html) jscs: [`requireSpacesInsideObjectBrackets`](http://jscs.info/rule/requireSpacesInsideObjectBrackets)
+
+    ```javascript
+    // bad
+    const foo = {clark: 'kent'};
+
+    // good
+    const foo = { clark: 'kent' };
+    ```
+
+  <a name="whitespace--max-len"></a><a name="18.12"></a>
+  - [18.12](#whitespace--max-len) Avoid having lines of code that are longer than 100 characters (including whitespace). eslint: [`max-len`](http://eslint.org/docs/rules/max-len.html) jscs: [`maximumLineLength`](http://jscs.info/rule/maximumLineLength)
+
+    > Why? This ensures readability and maintainability.
+
+    ```javascript
+    // bad
+    const foo = 'Whatever national crop flips the window. The cartoon reverts within the screw. Whatever wizard constrains a helpful ally. The counterpart ascends!';
+
+    // bad
+    $.ajax({ method: 'POST', url: 'https://airbnb.com/', data: { name: 'John' } }).done(() => console.log('Congratulations!')).fail(() => console.log('You have failed this city.'));
+
+    // good
+    const foo = 'Whatever national crop flips the window. The cartoon reverts within the screw. ' +
+      'Whatever wizard constrains a helpful ally. The counterpart ascends!';
+
+    // good
+    $.ajax({
+      method: 'POST',
+      url: 'https://airbnb.com/',
+      data: { name: 'John' },
+    })
+      .done(() => console.log('Congratulations!'))
+      .fail(() => console.log('You have failed this city.'));
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+## Commas
+
+<a name="commas--leading-trailing"></a><a name="19.1"></a>
+  - [19.1](#commas--leading-trailing) Leading commas: **Nope.** eslint: [`comma-style`](http://eslint.org/docs/rules/comma-style.html) jscs: [`requireCommaBeforeLineBreak`](http://jscs.info/rule/requireCommaBeforeLineBreak)
+
+    ```javascript
+    // bad
+    const story = [
+        once
+      , upon
+      , aTime
+    ];
+
+    // good
+    const story = [
+      once,
+      upon,
+      aTime,
+    ];
+
+    // bad
+    const hero = {
+        firstName: 'Ada'
+      , lastName: 'Lovelace'
+      , birthYear: 1815
+      , superPower: 'computers'
+    };
+
+    // good
+    const hero = {
+      firstName: 'Ada',
+      lastName: 'Lovelace',
+      birthYear: 1815,
+      superPower: 'computers',
+    };
+    ```
+
+  <a name="commas--dangling"></a><a name="19.2"></a>
+  - [19.2](#commas--dangling) Additional trailing comma: **Yup.** eslint: [`comma-dangle`](http://eslint.org/docs/rules/comma-dangle.html) jscs: [`requireTrailingComma`](http://jscs.info/rule/requireTrailingComma)
+
+    > Why? This leads to cleaner git diffs. Also, transpilers like Babel will remove the additional trailing comma in the transpiled code which means you don't have to worry about the [trailing comma problem](es5/README.md#commas) in legacy browsers.
+
+    ```javascript
+    // bad - git diff without trailing comma
+    const hero = {
+         firstName: 'Florence',
+    -    lastName: 'Nightingale'
+    +    lastName: 'Nightingale',
+    +    inventorOf: ['coxcomb graph', 'modern nursing']
+    };
+
+    // good - git diff with trailing comma
+    const hero = {
+         firstName: 'Florence',
+         lastName: 'Nightingale',
+    +    inventorOf: ['coxcomb chart', 'modern nursing'],
+    };
+
+    // bad
+    const hero = {
+      firstName: 'Dana',
+      lastName: 'Scully'
+    };
+
+    const heroes = [
+      'Batman',
+      'Superman'
+    ];
+
+    // good
+    const hero = {
+      firstName: 'Dana',
+      lastName: 'Scully',
+    };
+
+    const heroes = [
+      'Batman',
+      'Superman',
+    ];
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Semicolons
+
+  <a name="semicolons--required"></a><a name="20.1"></a>
+  - [20.1](#20.1) **Yup.** eslint: [`semi`](http://eslint.org/docs/rules/semi.html) jscs: [`requireSemicolons`](http://jscs.info/rule/requireSemicolons)
+
+    ```javascript
+    // bad
+    (function () {
+      const name = 'Skywalker'
+      return name
+    })()
+
+    // good
+    (function () {
+      const name = 'Skywalker';
+      return name;
+    }());
+
+    // good, but legacy (guards against the function becoming an argument when two files with IIFEs are concatenated)
+    ;(() => {
+      const name = 'Skywalker';
+      return name;
+    }());
+    ```
+
+    [Read more](http://stackoverflow.com/questions/7365172/semicolon-before-self-invoking-function/7365214%237365214).
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Type Casting & Coercion
+
+  <a name="coercion--explicit"></a><a name="21.1"></a>
+  - [21.1](#coercion--explicit) Perform type coercion at the beginning of the statement.
+
+  <a name="coercion--strings"></a><a name="21.2"></a>
+  - [21.2](#coercion--strings)  Strings:
+
+    ```javascript
+    // => this.reviewScore = 9;
+
+    // bad
+    const totalScore = this.reviewScore + ''; // invokes this.reviewScore.valueOf()
+
+    // bad
+    const totalScore = this.reviewScore.toString(); // isn't guaranteed to return a string
+
+    // good
+    const totalScore = String(this.reviewScore);
+    ```
+
+  <a name="coercion--numbers"></a><a name="21.3"></a>
+  - [21.3](#coercion--numbers) Numbers: Use `Number` for type casting and `parseInt` always with a radix for parsing strings. eslint: [`radix`](http://eslint.org/docs/rules/radix)
+
+    ```javascript
+    const inputValue = '4';
+
+    // bad
+    const val = new Number(inputValue);
+
+    // bad
+    const val = +inputValue;
+
+    // bad
+    const val = inputValue >> 0;
+
+    // bad
+    const val = parseInt(inputValue);
+
+    // good
+    const val = Number(inputValue);
+
+    // good
+    const val = parseInt(inputValue, 10);
+    ```
+
+  <a name="coercion--comment-deviations"></a><a name="21.4"></a>
+  - [21.4](#coercion--comment-deviations) If for whatever reason you are doing something wild and `parseInt` is your bottleneck and need to use Bitshift for [performance reasons](http://jsperf.com/coercion-vs-casting/3), leave a comment explaining why and what you're doing.
+
+    ```javascript
+    // good
+    /**
+     * parseInt was the reason my code was slow.
+     * Bitshifting the String to coerce it to a
+     * Number made it a lot faster.
+     */
+    const val = inputValue >> 0;
+    ```
+
+  <a name="coercion--bitwise"></a><a name="21.5"></a>
+  - [21.5](#coercion--bitwise) **Note:** Be careful when using bitshift operations. Numbers are represented as [64-bit values](http://es5.github.io/#x4.3.19), but bitshift operations always return a 32-bit integer ([source](http://es5.github.io/#x11.7)). Bitshift can lead to unexpected behavior for integer values larger than 32 bits. [Discussion](https://github.com/airbnb/javascript/issues/109). Largest signed 32-bit Int is 2,147,483,647:
+
+    ```javascript
+    2147483647 >> 0 //=> 2147483647
+    2147483648 >> 0 //=> -2147483648
+    2147483649 >> 0 //=> -2147483647
+    ```
+
+  <a name="coercion--booleans"></a><a name="21.6"></a>
+  - [21.6](#coercion--booleans) Booleans:
+
+    ```javascript
+    const age = 0;
+
+    // bad
+    const hasAge = new Boolean(age);
+
+    // good
+    const hasAge = Boolean(age);
+
+    // best
+    const hasAge = !!age;
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Naming Conventions
+
+  <a name="naming--descriptive"></a><a name="22.1"></a>
+  - [22.1](#naming--descriptive) Avoid single letter names. Be descriptive with your naming.
+
+    ```javascript
+    // bad
+    function q() {
+      // ...stuff...
+    }
+
+    // good
+    function query() {
+      // ..stuff..
+    }
+    ```
+
+  <a name="naming--camelCase"></a><a name="22.2"></a>
+  - [22.2](#naming--camelCase) Use camelCase when naming objects, functions, and instances. eslint: [`camelcase`](http://eslint.org/docs/rules/camelcase.html) jscs: [`requireCamelCaseOrUpperCaseIdentifiers`](http://jscs.info/rule/requireCamelCaseOrUpperCaseIdentifiers)
+
+    ```javascript
+    // bad
+    const OBJEcttsssss = {};
+    const this_is_my_object = {};
+    function c() {}
+
+    // good
+    const thisIsMyObject = {};
+    function thisIsMyFunction() {}
+    ```
+
+  <a name="naming--PascalCase"></a><a name="22.3"></a>
+  - [22.3](#naming--PascalCase) Use PascalCase only when naming constructors or classes. eslint: [`new-cap`](http://eslint.org/docs/rules/new-cap.html) jscs: [`requireCapitalizedConstructors`](http://jscs.info/rule/requireCapitalizedConstructors)
+
+    ```javascript
+    // bad
+    function user(options) {
+      this.name = options.name;
+    }
+
+    const bad = new user({
+      name: 'nope',
+    });
+
+    // good
+    class User {
+      constructor(options) {
+        this.name = options.name;
+      }
+    }
+
+    const good = new User({
+      name: 'yup',
+    });
+    ```
+
+  <a name="naming--leading-underscore"></a><a name="22.4"></a>
+  - [22.4](#naming--leading-underscore) Do not use trailing or leading underscores. eslint: [`no-underscore-dangle`](http://eslint.org/docs/rules/no-underscore-dangle.html) jscs: [`disallowDanglingUnderscores`](http://jscs.info/rule/disallowDanglingUnderscores)
+
+    > Why? JavaScript does not have the concept of privacy in terms of properties or methods. Although a leading underscore is a common convention to mean “private”, in fact, these properties are fully public, and as such, are part of your public API contract. This convention might lead developers to wrongly think that a change won't count as breaking, or that tests aren't needed. tl;dr: if you want something to be “private”, it must not be observably present.
+
+    ```javascript
+    // bad
+    this.__firstName__ = 'Panda';
+    this.firstName_ = 'Panda';
+    this._firstName = 'Panda';
+
+    // good
+    this.firstName = 'Panda';
+    ```
+
+  <a name="naming--self-this"></a><a name="22.5"></a>
+  - [22.5](#naming--self-this) Don't save references to `this`. Use arrow functions or Function#bind. jscs: [`disallowNodeTypes`](http://jscs.info/rule/disallowNodeTypes)
+
+    ```javascript
+    // bad
+    function foo() {
+      const self = this;
+      return function () {
+        console.log(self);
+      };
+    }
+
+    // bad
+    function foo() {
+      const that = this;
+      return function () {
+        console.log(that);
+      };
+    }
+
+    // good
+    function foo() {
+      return () => {
+        console.log(this);
+      };
+    }
+    ```
+
+  <a name="naming--filename-matches-export"></a><a name="22.6"></a>
+  - [22.6](#naming--filename-matches-export) A base filename should exactly match the name of its default export.
+
+    ```javascript
+    // file 1 contents
+    class CheckBox {
+      // ...
+    }
+    export default CheckBox;
+
+    // file 2 contents
+    export default function fortyTwo() { return 42; }
+
+    // file 3 contents
+    export default function insideDirectory() {}
+
+    // in some other file
+    // bad
+    import CheckBox from './checkBox'; // PascalCase import/export, camelCase filename
+    import FortyTwo from './FortyTwo'; // PascalCase import/filename, camelCase export
+    import InsideDirectory from './InsideDirectory'; // PascalCase import/filename, camelCase export
+
+    // bad
+    import CheckBox from './check_box'; // PascalCase import/export, snake_case filename
+    import forty_two from './forty_two'; // snake_case import/filename, camelCase export
+    import inside_directory from './inside_directory'; // snake_case import, camelCase export
+    import index from './inside_directory/index'; // requiring the index file explicitly
+    import insideDirectory from './insideDirectory/index'; // requiring the index file explicitly
+
+    // good
+    import CheckBox from './CheckBox'; // PascalCase export/import/filename
+    import fortyTwo from './fortyTwo'; // camelCase export/import/filename
+    import insideDirectory from './insideDirectory'; // camelCase export/import/directory name/implicit "index"
+    // ^ supports both insideDirectory.js and insideDirectory/index.js
+    ```
+
+  <a name="naming--camelCase-default-export"></a><a name="22.7"></a>
+  - [22.7](#naming--camelCase-default-export) Use camelCase when you export-default a function. Your filename should be identical to your function's name.
+
+    ```javascript
+    function makeStyleGuide() {
+    }
+
+    export default makeStyleGuide;
+    ```
+
+  <a name="naming--PascalCase-singleton"></a><a name="22.8"></a>
+  - [22.8](#naming--PascalCase-singleton) Use PascalCase when you export a constructor / class / singleton / function library / bare object.
+
+    ```javascript
+    const AirbnbStyleGuide = {
+      es6: {
+      }
+    };
+
+    export default AirbnbStyleGuide;
+    ```
+
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Accessors
+
+  <a name="accessors--not-required"></a><a name="23.1"></a>
+  - [23.1](#accessors--not-required) Accessor functions for properties are not required.
+
+  <a name="accessors--no-getters-setters"></a><a name="23.2"></a>
+  - [23.2](#accessors--no-getters-setters) Do not use JavaScript getters/setters as they cause unexpected side effects and are harder to test, maintain, and reason about. Instead, if you do make accessor functions, use getVal() and setVal('hello').
+
+    ```javascript
+    // bad
+    class Dragon {
+      get age() {
+        // ...
+      }
+
+      set age(value) {
+        // ...
+      }
+    }
+
+    // good
+    class Dragon {
+      getAge() {
+        // ...
+      }
+
+      setAge(value) {
+        // ...
+      }
+    }
+    ```
+
+  <a name="accessors--boolean-prefix"></a><a name="23.3"></a>
+  - [23.3](#accessors--boolean-prefix) If the property/method is a `boolean`, use `isVal()` or `hasVal()`.
+
+    ```javascript
+    // bad
+    if (!dragon.age()) {
+      return false;
+    }
+
+    // good
+    if (!dragon.hasAge()) {
+      return false;
+    }
+    ```
+
+  <a name="accessors--consistent"></a><a name="23.4"></a>
+  - [23.4](#accessors--consistent) It's okay to create get() and set() functions, but be consistent.
+
+    ```javascript
+    class Jedi {
+      constructor(options = {}) {
+        const lightsaber = options.lightsaber || 'blue';
+        this.set('lightsaber', lightsaber);
+      }
+
+      set(key, val) {
+        this[key] = val;
+      }
+
+      get(key) {
+        return this[key];
+      }
+    }
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Events
+
+  <a name="events--hash"></a><a name="24.1"></a>
+  - [24.1](#events--hash) When attaching data payloads to events (whether DOM events or something more proprietary like Backbone events), pass a hash instead of a raw value. This allows a subsequent contributor to add more data to the event payload without finding and updating every handler for the event. For example, instead of:
+
+    ```javascript
+    // bad
+    $(this).trigger('listingUpdated', listing.id);
+
+    ...
+
+    $(this).on('listingUpdated', (e, listingId) => {
+      // do something with listingId
+    });
+    ```
+
+    prefer:
+
+    ```javascript
+    // good
+    $(this).trigger('listingUpdated', { listingId: listing.id });
+
+    ...
+
+    $(this).on('listingUpdated', (e, data) => {
+      // do something with data.listingId
+    });
+    ```
+
+  **[⬆ back to top](#table-of-contents)**
+
+
+## jQuery
+
+  <a name="jquery--dollar-prefix"></a><a name="25.1"></a>
+  - [25.1](#jquery--dollar-prefix) Prefix jQuery object variables with a `$`. jscs: [`requireDollarBeforejQueryAssignment`](http://jscs.info/rule/requireDollarBeforejQueryAssignment)
+
+    ```javascript
+    // bad
+    const sidebar = $('.sidebar');
+
+    // good
+    const $sidebar = $('.sidebar');
+
+    // good
+    const $sidebarBtn = $('.sidebar-btn');
+    ```
+
+  <a name="jquery--cache"></a><a name="25.2"></a>
+  - [25.2](#jquery--cache) Cache jQuery lookups.
+
+    ```javascript
+    // bad
+    function setSidebar() {
+      $('.sidebar').hide();
+
+      // ...stuff...
+
+      $('.sidebar').css({
+        'background-color': 'pink'
+      });
+    }
+
+    // good
+    function setSidebar() {
+      const $sidebar = $('.sidebar');
+      $sidebar.hide();
+
+      // ...stuff...
+
+      $sidebar.css({
+        'background-color': 'pink'
+      });
+    }
+    ```
+
+  <a name="jquery--queries"></a><a name="25.3"></a>
+  - [25.3](#jquery--queries) For DOM queries use Cascading `$('.sidebar ul')` or parent > child `$('.sidebar > ul')`. [jsPerf](http://jsperf.com/jquery-find-vs-context-sel/16)
+
+  <a name="jquery--find"></a><a name="25.4"></a>
+  - [25.4](#jquery--find) Use `find` with scoped jQuery object queries.
+
+    ```javascript
+    // bad
+    $('ul', '.sidebar').hide();
+
+    // bad
+    $('.sidebar').find('ul').hide();
+
+    // good
+    $('.sidebar ul').hide();
+
+    // good
+    $('.sidebar > ul').hide();
+
+    // good
+    $sidebar.find('ul').hide();
+    ```
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## ECMAScript 5 Compatibility
+
+  <a name="es5-compat--kangax"></a><a name="26.1"></a>
+  - [26.1](#es5-compat--kangax) Refer to [Kangax](https://twitter.com/kangax/)'s ES5 [compatibility table](http://kangax.github.io/es5-compat-table/).
+
+**[⬆ back to top](#table-of-contents)**
+
+## ECMAScript 6 Styles
+
+  <a name="es6-styles"></a><a name="27.1"></a>
+  - [27.1](#es6-styles) This is a collection of links to the various ES6 features.
+
+1. [Arrow Functions](#arrow-functions)
+1. [Classes](#constructors)
+1. [Object Shorthand](#es6-object-shorthand)
+1. [Object Concise](#es6-object-concise)
+1. [Object Computed Properties](#es6-computed-properties)
+1. [Template Strings](#es6-template-literals)
+1. [Destructuring](#destructuring)
+1. [Default Parameters](#es6-default-parameters)
+1. [Rest](#es6-rest)
+1. [Array Spreads](#es6-array-spreads)
+1. [Let and Const](#references)
+1. [Iterators and Generators](#iterators-and-generators)
+1. [Modules](#modules)
+
+**[⬆ back to top](#table-of-contents)**
+
+## Testing
+
+  <a name="testing--yup"></a><a name="28.1"></a>
+  - [28.1](#testing--yup) **Yup.**
+
+    ```javascript
+    function foo() {
+      return true;
+    }
+    ```
+
+  <a name="testing--for-real"></a><a name="28.2"></a>
+  - [28.2](#testing--for-real) **No, but seriously**:
+   - Whichever testing framework you use, you should be writing tests!
+   - Strive to write many small pure functions, and minimize where mutations occur.
+   - Be cautious about stubs and mocks - they can make your tests more brittle.
+   - We primarily use [`mocha`](https://www.npmjs.com/package/mocha) at Airbnb. [`tape`](https://www.npmjs.com/package/tape) is also used occasionally for small, separate modules.
+   - 100% test coverage is a good goal to strive for, even if it's not always practical to reach it.
+   - Whenever you fix a bug, _write a regression test_. A bug fixed without a regression test is almost certainly going to break again in the future.
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Performance
+
+  - [On Layout & Web Performance](http://www.kellegous.com/j/2013/01/26/layout-performance/)
+  - [String vs Array Concat](http://jsperf.com/string-vs-array-concat/2)
+  - [Try/Catch Cost In a Loop](http://jsperf.com/try-catch-in-loop-cost)
+  - [Bang Function](http://jsperf.com/bang-function)
+  - [jQuery Find vs Context, Selector](http://jsperf.com/jquery-find-vs-context-sel/13)
+  - [innerHTML vs textContent for script text](http://jsperf.com/innerhtml-vs-textcontent-for-script-text)
+  - [Long String Concatenation](http://jsperf.com/ya-string-concat)
+  - [Are Javascript functions like `map()`, `reduce()`, and `filter()` optimized for traversing arrays?](https://www.quora.com/JavaScript-programming-language-Are-Javascript-functions-like-map-reduce-and-filter-already-optimized-for-traversing-array/answer/Quildreen-Motta)
+  - Loading...
+
+**[⬆ back to top](#table-of-contents)**
+
+
+## Resources
+
+**Learning ES6**
+
+  - [Draft ECMA 2015 (ES6) Spec](https://people.mozilla.org/~jorendorff/es6-draft.html)
+  - [ExploringJS](http://exploringjs.com/)
+  - [ES6 Compatibility Table](https://kangax.github.io/compat-table/es6/)
+  - [Comprehensive Overview of ES6 Features](http://es6-features.org/)
+
+**Read This**
+
+  - [Standard ECMA-262](http://www.ecma-international.org/ecma-262/6.0/index.html)
+
+**Tools**
+
+  - Code Style Linters
+    + [ESlint](http://eslint.org/) - [Airbnb Style .eslintrc](https://github.com/airbnb/javascript/blob/master/linters/.eslintrc)
+    + [JSHint](http://jshint.com/) - [Airbnb Style .jshintrc](https://github.com/airbnb/javascript/blob/master/linters/.jshintrc)
+    + [JSCS](https://github.com/jscs-dev/node-jscs) - [Airbnb Style Preset](https://github.com/jscs-dev/node-jscs/blob/master/presets/airbnb.json)
+
+**Other Style Guides**
+
+  - [Google JavaScript Style Guide](https://google.github.io/styleguide/javascriptguide.xml)
+  - [jQuery Core Style Guidelines](http://contribute.jquery.org/style-guide/js/)
+  - [Principles of Writing Consistent, Idiomatic JavaScript](https://github.com/rwaldron/idiomatic.js)
+
+**Other Styles**
+
+  - [Naming this in nested functions](https://gist.github.com/cjohansen/4135065) - Christian Johansen
+  - [Conditional Callbacks](https://github.com/airbnb/javascript/issues/52) - Ross Allen
+  - [Popular JavaScript Coding Conventions on Github](http://sideeffect.kr/popularconvention/#javascript) - JeongHoon Byun
+  - [Multiple var statements in JavaScript, not superfluous](http://benalman.com/news/2012/05/multiple-var-statements-javascript/) - Ben Alman
+
+**Further Reading**
+
+  - [Understanding JavaScript Closures](http://javascriptweblog.wordpress.com/2010/10/25/understanding-javascript-closures/) - Angus Croll
+  - [Basic JavaScript for the impatient programmer](http://www.2ality.com/2013/06/basic-javascript.html) - Dr. Axel Rauschmayer
+  - [You Might Not Need jQuery](http://youmightnotneedjquery.com/) - Zack Bloom & Adam Schwartz
+  - [ES6 Features](https://github.com/lukehoban/es6features) - Luke Hoban
+  - [Frontend Guidelines](https://github.com/bendc/frontend-guidelines) - Benjamin De Cock
+
+**Books**
+
+  - [JavaScript: The Good Parts](http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742) - Douglas Crockford
+  - [JavaScript Patterns](http://www.amazon.com/JavaScript-Patterns-Stoyan-Stefanov/dp/0596806752) - Stoyan Stefanov
+  - [Pro JavaScript Design Patterns](http://www.amazon.com/JavaScript-Design-Patterns-Recipes-Problem-Solution/dp/159059908X)  - Ross Harmes and Dustin Diaz
+  - [High Performance Web Sites: Essential Knowledge for Front-End Engineers](http://www.amazon.com/High-Performance-Web-Sites-Essential/dp/0596529309) - Steve Souders
+  - [Maintainable JavaScript](http://www.amazon.com/Maintainable-JavaScript-Nicholas-C-Zakas/dp/1449327680) - Nicholas C. Zakas
+  - [JavaScript Web Applications](http://www.amazon.com/JavaScript-Web-Applications-Alex-MacCaw/dp/144930351X) - Alex MacCaw
+  - [Pro JavaScript Techniques](http://www.amazon.com/Pro-JavaScript-Techniques-John-Resig/dp/1590597273) - John Resig
+  - [Smashing Node.js: JavaScript Everywhere](http://www.amazon.com/Smashing-Node-js-JavaScript-Everywhere-Magazine/dp/1119962595) - Guillermo Rauch
+  - [Secrets of the JavaScript Ninja](http://www.amazon.com/Secrets-JavaScript-Ninja-John-Resig/dp/193398869X) - John Resig and Bear Bibeault
+  - [Human JavaScript](http://humanjavascript.com/) - Henrik Joreteg
+  - [Superhero.js](http://superherojs.com/) - Kim Joar Bekkelund, Mads Mobæk, & Olav Bjorkoy
+  - [JSBooks](http://jsbooks.revolunet.com/) - Julien Bouquillon
+  - [Third Party JavaScript](https://www.manning.com/books/third-party-javascript) - Ben Vinegar and Anton Kovalyov
+  - [Effective JavaScript: 68 Specific Ways to Harness the Power of JavaScript](http://amzn.com/0321812182) - David Herman
+  - [Eloquent JavaScript](http://eloquentjavascript.net/) - Marijn Haverbeke
+  - [You Don't Know JS: ES6 & Beyond](http://shop.oreilly.com/product/0636920033769.do) - Kyle Simpson
+
+**Blogs**
+
+  - [DailyJS](http://dailyjs.com/)
+  - [JavaScript Weekly](http://javascriptweekly.com/)
+  - [JavaScript, JavaScript...](http://javascriptweblog.wordpress.com/)
+  - [Bocoup Weblog](https://bocoup.com/weblog)
+  - [Adequately Good](http://www.adequatelygood.com/)
+  - [NCZOnline](https://www.nczonline.net/)
+  - [Perfection Kills](http://perfectionkills.com/)
+  - [Ben Alman](http://benalman.com/)
+  - [Dmitry Baranovskiy](http://dmitry.baranovskiy.com/)
+  - [Dustin Diaz](http://dustindiaz.com/)
+  - [nettuts](http://code.tutsplus.com/?s=javascript)
+
+**Podcasts**
+
+  - [JavaScript Jabber](https://devchat.tv/js-jabber/)
+
+
+**[⬆ back to top](#table-of-contents)**
+
+## In the Wild
+
+  This is a list of organizations that are using this style guide. Send us a pull request and we'll add you to the list.
+
+  - **4Catalyzer**: [4Catalyzer/javascript](https://github.com/4Catalyzer/javascript)
+  - **Aan Zee**: [AanZee/javascript](https://github.com/AanZee/javascript)
+  - **Adult Swim**: [adult-swim/javascript](https://github.com/adult-swim/javascript)
+  - **Airbnb**: [airbnb/javascript](https://github.com/airbnb/javascript)
+  - **Apartmint**: [apartmint/javascript](https://github.com/apartmint/javascript)
+  - **Ascribe**: [ascribe/javascript](https://github.com/ascribe/javascript)
+  - **Avalara**: [avalara/javascript](https://github.com/avalara/javascript)
+  - **Avant**: [avantcredit/javascript](https://github.com/avantcredit/javascript)
+  - **Billabong**: [billabong/javascript](https://github.com/billabong/javascript)
+  - **Bisk**: [bisk/javascript](https://github.com/Bisk/javascript/)
+  - **Blendle**: [blendle/javascript](https://github.com/blendle/javascript)
+  - **Brainshark**: [brainshark/javascript](https://github.com/brainshark/javascript)
+  - **Chartboost**: [ChartBoost/javascript-style-guide](https://github.com/ChartBoost/javascript-style-guide)
+  - **ComparaOnline**: [comparaonline/javascript](https://github.com/comparaonline/javascript-style-guide)
+  - **Compass Learning**: [compasslearning/javascript-style-guide](https://github.com/compasslearning/javascript-style-guide)
+  - **DailyMotion**: [dailymotion/javascript](https://github.com/dailymotion/javascript)
+  - **DoSomething**: [DoSomething/eslint-config](https://github.com/DoSomething/eslint-config)
+  - **Digitpaint** [digitpaint/javascript](https://github.com/digitpaint/javascript)
+  - **Ecosia**: [ecosia/javascript](https://github.com/ecosia/javascript)
+  - **Evernote**: [evernote/javascript-style-guide](https://github.com/evernote/javascript-style-guide)
+  - **Evolution Gaming**: [evolution-gaming/javascript](https://github.com/evolution-gaming/javascript)
+  - **EvozonJs**: [evozonjs/javascript](https://github.com/evozonjs/javascript)
+  - **ExactTarget**: [ExactTarget/javascript](https://github.com/ExactTarget/javascript)
+  - **Expensify** [Expensify/Style-Guide](https://github.com/Expensify/Style-Guide/blob/master/javascript.md)
+  - **Flexberry**: [Flexberry/javascript-style-guide](https://github.com/Flexberry/javascript-style-guide)
+  - **Gawker Media**: [gawkermedia/javascript](https://github.com/gawkermedia/javascript)
+  - **General Electric**: [GeneralElectric/javascript](https://github.com/GeneralElectric/javascript)
+  - **GoodData**: [gooddata/gdc-js-style](https://github.com/gooddata/gdc-js-style)
+  - **Grooveshark**: [grooveshark/javascript](https://github.com/grooveshark/javascript)
+  - **How About We**: [howaboutwe/javascript](https://github.com/howaboutwe/javascript-style-guide)
+  - **Huballin**: [huballin/javascript](https://github.com/huballin/javascript)
+  - **HubSpot**: [HubSpot/javascript](https://github.com/HubSpot/javascript)
+  - **Hyper**: [hyperoslo/javascript-playbook](https://github.com/hyperoslo/javascript-playbook/blob/master/style.md)
+  - **InfoJobs**: [InfoJobs/JavaScript-Style-Guide](https://github.com/InfoJobs/JavaScript-Style-Guide)
+  - **Intent Media**: [intentmedia/javascript](https://github.com/intentmedia/javascript)
+  - **Jam3**: [Jam3/Javascript-Code-Conventions](https://github.com/Jam3/Javascript-Code-Conventions)
+  - **JeopardyBot**: [kesne/jeopardy-bot](https://github.com/kesne/jeopardy-bot/blob/master/STYLEGUIDE.md)
+  - **JSSolutions**: [JSSolutions/javascript](https://github.com/JSSolutions/javascript)
+  - **KickorStick**: [kickorstick/javascript](https://github.com/kickorstick/javascript)
+  - **Kinetica Solutions**: [kinetica/javascript](https://github.com/kinetica/Javascript-style-guide)
+  - **Mighty Spring**: [mightyspring/javascript](https://github.com/mightyspring/javascript)
+  - **MinnPost**: [MinnPost/javascript](https://github.com/MinnPost/javascript)
+  - **MitocGroup**: [MitocGroup/javascript](https://github.com/MitocGroup/javascript)
+  - **ModCloth**: [modcloth/javascript](https://github.com/modcloth/javascript)
+  - **Money Advice Service**: [moneyadviceservice/javascript](https://github.com/moneyadviceservice/javascript)
+  - **Muber**: [muber/javascript](https://github.com/muber/javascript)
+  - **National Geographic**: [natgeo/javascript](https://github.com/natgeo/javascript)
+  - **National Park Service**: [nationalparkservice/javascript](https://github.com/nationalparkservice/javascript)
+  - **Nimbl3**: [nimbl3/javascript](https://github.com/nimbl3/javascript)
+  - **Orion Health**: [orionhealth/javascript](https://github.com/orionhealth/javascript)
+  - **OutBoxSoft**: [OutBoxSoft/javascript](https://github.com/OutBoxSoft/javascript)
+  - **Peerby**: [Peerby/javascript](https://github.com/Peerby/javascript)
+  - **Razorfish**: [razorfish/javascript-style-guide](https://github.com/razorfish/javascript-style-guide)
+  - **reddit**: [reddit/styleguide/javascript](https://github.com/reddit/styleguide/tree/master/javascript)
+  - **React**: [/facebook/react/blob/master/CONTRIBUTING.md#style-guide](https://github.com/facebook/react/blob/master/CONTRIBUTING.md#style-guide)
+  - **REI**: [reidev/js-style-guide](https://github.com/rei/code-style-guides/blob/master/docs/javascript.md)
+  - **Ripple**: [ripple/javascript-style-guide](https://github.com/ripple/javascript-style-guide)
+  - **SeekingAlpha**: [seekingalpha/javascript-style-guide](https://github.com/seekingalpha/javascript-style-guide)
+  - **Shutterfly**: [shutterfly/javascript](https://github.com/shutterfly/javascript)
+  - **Springload**: [springload/javascript](https://github.com/springload/javascript)
+  - **StudentSphere**: [studentsphere/javascript](https://github.com/studentsphere/guide-javascript)
+  - **SysGarage**: [sysgarage/javascript-style-guide](https://github.com/sysgarage/javascript-style-guide)
+  - **Target**: [target/javascript](https://github.com/target/javascript)
+  - **TheLadders**: [TheLadders/javascript](https://github.com/TheLadders/javascript)
+  - **The Nerdery**: [thenerdery/javascript-standards](https://github.com/thenerdery/javascript-standards)
+  - **T4R Technology**: [T4R-Technology/javascript](https://github.com/T4R-Technology/javascript)
+  - **VoxFeed**: [VoxFeed/javascript-style-guide](https://github.com/VoxFeed/javascript-style-guide)
+  - **WeBox Studio**: [weboxstudio/javascript](https://github.com/weboxstudio/javascript)
+  - **Weggo**: [Weggo/javascript](https://github.com/Weggo/javascript)
+  - **Zillow**: [zillow/javascript](https://github.com/zillow/javascript)
+  - **ZocDoc**: [ZocDoc/javascript](https://github.com/ZocDoc/javascript)
+
+**[⬆ back to top](#table-of-contents)**
+
+## Translation
+
+  This style guide is also available in other languages:
+
+  - ![br](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Brazil.png) **Brazilian Portuguese**: [armoucar/javascript-style-guide](https://github.com/armoucar/javascript-style-guide)
+  - ![bg](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Bulgaria.png) **Bulgarian**: [borislavvv/javascript](https://github.com/borislavvv/javascript)
+  - ![ca](https://raw.githubusercontent.com/fpmweb/javascript-style-guide/master/img/catala.png) **Catalan**: [fpmweb/javascript-style-guide](https://github.com/fpmweb/javascript-style-guide)
+  - ![cn](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/China.png) **Chinese (Simplified)**: [sivan/javascript-style-guide](https://github.com/sivan/javascript-style-guide)
+  - ![tw](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Taiwan.png) **Chinese (Traditional)**: [jigsawye/javascript](https://github.com/jigsawye/javascript)
+  - ![fr](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/France.png) **French**: [nmussy/javascript-style-guide](https://github.com/nmussy/javascript-style-guide)
+  - ![de](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Germany.png) **German**: [timofurrer/javascript-style-guide](https://github.com/timofurrer/javascript-style-guide)
+  - ![it](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Italy.png) **Italian**: [sinkswim/javascript-style-guide](https://github.com/sinkswim/javascript-style-guide)
+  - ![jp](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Japan.png) **Japanese**: [mitsuruog/javacript-style-guide](https://github.com/mitsuruog/javacript-style-guide)
+  - ![kr](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/South-Korea.png) **Korean**: [tipjs/javascript-style-guide](https://github.com/tipjs/javascript-style-guide)
+  - ![pl](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Poland.png) **Polish**: [mjurczyk/javascript](https://github.com/mjurczyk/javascript)
+  - ![ru](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Russia.png) **Russian**: [uprock/javascript](https://github.com/uprock/javascript)
+  - ![es](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Spain.png) **Spanish**: [paolocarrasco/javascript-style-guide](https://github.com/paolocarrasco/javascript-style-guide)
+  - ![th](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Thailand.png) **Thai**: [lvarayut/javascript-style-guide](https://github.com/lvarayut/javascript-style-guide)
+  - ![vn](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Vietnam.png) **Vietnam**: [giangpii/javascript-style-guide](https://github.com/giangpii/javascript-style-guide)
+
+## The JavaScript Style Guide Guide
+
+  - [Reference](https://github.com/airbnb/javascript/wiki/The-JavaScript-Style-Guide-Guide)
+
+## Chat With Us About JavaScript
+
+  - Find us on [gitter](https://gitter.im/airbnb/javascript).
+
+## Contributors
+
+  - [View Contributors](https://github.com/airbnb/javascript/graphs/contributors)
+
+
+## License
+
+(The MIT License)
+
+Copyright (c) 2014-2016 Airbnb
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+**[⬆ back to top](#table-of-contents)**
+
+## Amendments
+
+We encourage you to fork this guide and change the rules to fit your team's style guide. Below, you may list some amendments to the style guide. This allows you to periodically update your style guide without having to deal with merge conflicts.
+
+# };
diff --git a/params.json b/params.json
deleted file mode 100644
index 67265701..00000000
--- a/params.json
+++ /dev/null
@@ -1,7 +0,0 @@
-{
-  "name": "Airbnb JavaScript Style Guide",
-  "tagline": "A mostly reasonable approach to JavaScript",
-  "body": "# Airbnb JavaScript Style Guide() {\r\n\r\n*A mostly reasonable approach to JavaScript*\r\n\r\n[![Downloads](https://img.shields.io/npm/dm/eslint-config-airbnb.svg)](https://www.npmjs.com/package/eslint-config-airbnb)\r\n[![Downloads](https://img.shields.io/npm/dm/eslint-config-airbnb-base.svg)](https://www.npmjs.com/package/eslint-config-airbnb-base)\r\n[![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/airbnb/javascript?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)\r\n\r\nOther Style Guides\r\n - [ES5](es5/)\r\n - [React](react/)\r\n - [CSS & Sass](https://github.com/airbnb/css)\r\n - [Ruby](https://github.com/airbnb/ruby)\r\n\r\n## Table of Contents\r\n\r\n  1. [Types](#types)\r\n  1. [References](#references)\r\n  1. [Objects](#objects)\r\n  1. [Arrays](#arrays)\r\n  1. [Destructuring](#destructuring)\r\n  1. [Strings](#strings)\r\n  1. [Functions](#functions)\r\n  1. [Arrow Functions](#arrow-functions)\r\n  1. [Classes & Constructors](#classes--constructors)\r\n  1. [Modules](#modules)\r\n  1. [Iterators and Generators](#iterators-and-generators)\r\n  1. [Properties](#properties)\r\n  1. [Variables](#variables)\r\n  1. [Hoisting](#hoisting)\r\n  1. [Comparison Operators & Equality](#comparison-operators--equality)\r\n  1. [Blocks](#blocks)\r\n  1. [Comments](#comments)\r\n  1. [Whitespace](#whitespace)\r\n  1. [Commas](#commas)\r\n  1. [Semicolons](#semicolons)\r\n  1. [Type Casting & Coercion](#type-casting--coercion)\r\n  1. [Naming Conventions](#naming-conventions)\r\n  1. [Accessors](#accessors)\r\n  1. [Events](#events)\r\n  1. [jQuery](#jquery)\r\n  1. [ECMAScript 5 Compatibility](#ecmascript-5-compatibility)\r\n  1. [ECMAScript 6 Styles](#ecmascript-6-styles)\r\n  1. [Testing](#testing)\r\n  1. [Performance](#performance)\r\n  1. [Resources](#resources)\r\n  1. [In the Wild](#in-the-wild)\r\n  1. [Translation](#translation)\r\n  1. [The JavaScript Style Guide Guide](#the-javascript-style-guide-guide)\r\n  1. [Chat With Us About JavaScript](#chat-with-us-about-javascript)\r\n  1. [Contributors](#contributors)\r\n  1. [License](#license)\r\n\r\n## Types\r\n\r\n  <a name=\"types--primitives\"></a><a name=\"1.1\"></a>\r\n  - [1.1](#types--primitives) **Primitives**: When you access a primitive type you work directly on its value.\r\n\r\n    + `string`\r\n    + `number`\r\n    + `boolean`\r\n    + `null`\r\n    + `undefined`\r\n\r\n    ```javascript\r\n    const foo = 1;\r\n    let bar = foo;\r\n\r\n    bar = 9;\r\n\r\n    console.log(foo, bar); // => 1, 9\r\n    ```\r\n\r\n  <a name=\"types--complex\"></a><a name=\"1.2\"></a>\r\n  - [1.2](#types--complex)  **Complex**: When you access a complex type you work on a reference to its value.\r\n\r\n    + `object`\r\n    + `array`\r\n    + `function`\r\n\r\n    ```javascript\r\n    const foo = [1, 2];\r\n    const bar = foo;\r\n\r\n    bar[0] = 9;\r\n\r\n    console.log(foo[0], bar[0]); // => 9, 9\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## References\r\n\r\n  <a name=\"references--prefer-const\"></a><a name=\"2.1\"></a>\r\n  - [2.1](#references--prefer-const) Use `const` for all of your references; avoid using `var`. eslint: [`prefer-const`](http://eslint.org/docs/rules/prefer-const.html), [`no-const-assign`](http://eslint.org/docs/rules/no-const-assign.html)\r\n\r\n    > Why? This ensures that you can't reassign your references, which can lead to bugs and difficult to comprehend code.\r\n\r\n    ```javascript\r\n    // bad\r\n    var a = 1;\r\n    var b = 2;\r\n\r\n    // good\r\n    const a = 1;\r\n    const b = 2;\r\n    ```\r\n\r\n  <a name=\"references--disallow-var\"></a><a name=\"2.2\"></a>\r\n  - [2.2](#references--disallow-var) If you must reassign references, use `let` instead of `var`. eslint: [`no-var`](http://eslint.org/docs/rules/no-var.html) jscs: [`disallowVar`](http://jscs.info/rule/disallowVar)\r\n\r\n    > Why? `let` is block-scoped rather than function-scoped like `var`.\r\n\r\n    ```javascript\r\n    // bad\r\n    var count = 1;\r\n    if (true) {\r\n      count += 1;\r\n    }\r\n\r\n    // good, use the let.\r\n    let count = 1;\r\n    if (true) {\r\n      count += 1;\r\n    }\r\n    ```\r\n\r\n  <a name=\"references--block-scope\"></a><a name=\"2.3\"></a>\r\n  - [2.3](#references--block-scope) Note that both `let` and `const` are block-scoped.\r\n\r\n    ```javascript\r\n    // const and let only exist in the blocks they are defined in.\r\n    {\r\n      let a = 1;\r\n      const b = 1;\r\n    }\r\n    console.log(a); // ReferenceError\r\n    console.log(b); // ReferenceError\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Objects\r\n\r\n  <a name=\"objects--no-new\"></a><a name=\"3.1\"></a>\r\n  - [3.1](#objects--no-new) Use the literal syntax for object creation. eslint: [`no-new-object`](http://eslint.org/docs/rules/no-new-object.html)\r\n\r\n    ```javascript\r\n    // bad\r\n    const item = new Object();\r\n\r\n    // good\r\n    const item = {};\r\n    ```\r\n\r\n  <a name=\"objects--reserved-words\"></a><a name=\"3.2\"></a>\r\n  - [3.2](#objects--reserved-words) If your code will be executed in browsers in script context, don't use [reserved words](http://es5.github.io/#x7.6.1) as keys. It won't work in IE8. [More info](https://github.com/airbnb/javascript/issues/61). It’s OK to use them in ES6 modules and server-side code. jscs: [`disallowIdentifierNames`](http://jscs.info/rule/disallowIdentifierNames)\r\n\r\n    ```javascript\r\n    // bad\r\n    const superman = {\r\n      default: { clark: 'kent' },\r\n      private: true,\r\n    };\r\n\r\n    // good\r\n    const superman = {\r\n      defaults: { clark: 'kent' },\r\n      hidden: true,\r\n    };\r\n    ```\r\n\r\n  <a name=\"objects--reserved-words-2\"></a><a name=\"3.3\"></a>\r\n  - [3.3](#objects--reserved-words-2) Use readable synonyms in place of reserved words. jscs: [`disallowIdentifierNames`](http://jscs.info/rule/disallowIdentifierNames)\r\n\r\n    ```javascript\r\n    // bad\r\n    const superman = {\r\n      class: 'alien',\r\n    };\r\n\r\n    // bad\r\n    const superman = {\r\n      klass: 'alien',\r\n    };\r\n\r\n    // good\r\n    const superman = {\r\n      type: 'alien',\r\n    };\r\n    ```\r\n\r\n  <a name=\"es6-computed-properties\"></a><a name=\"3.4\"></a>\r\n  - [3.4](#es6-computed-properties) Use computed property names when creating objects with dynamic property names.\r\n\r\n    > Why? They allow you to define all the properties of an object in one place.\r\n\r\n    ```javascript\r\n\r\n    function getKey(k) {\r\n      return `a key named ${k}`;\r\n    }\r\n\r\n    // bad\r\n    const obj = {\r\n      id: 5,\r\n      name: 'San Francisco',\r\n    };\r\n    obj[getKey('enabled')] = true;\r\n\r\n    // good\r\n    const obj = {\r\n      id: 5,\r\n      name: 'San Francisco',\r\n      [getKey('enabled')]: true,\r\n    };\r\n    ```\r\n\r\n  <a name=\"es6-object-shorthand\"></a><a name=\"3.5\"></a>\r\n  - [3.5](#es6-object-shorthand) Use object method shorthand. eslint: [`object-shorthand`](http://eslint.org/docs/rules/object-shorthand.html) jscs: [`requireEnhancedObjectLiterals`](http://jscs.info/rule/requireEnhancedObjectLiterals)\r\n\r\n    ```javascript\r\n    // bad\r\n    const atom = {\r\n      value: 1,\r\n\r\n      addValue: function (value) {\r\n        return atom.value + value;\r\n      },\r\n    };\r\n\r\n    // good\r\n    const atom = {\r\n      value: 1,\r\n\r\n      addValue(value) {\r\n        return atom.value + value;\r\n      },\r\n    };\r\n    ```\r\n\r\n  <a name=\"es6-object-concise\"></a><a name=\"3.6\"></a>\r\n  - [3.6](#es6-object-concise) Use property value shorthand. eslint: [`object-shorthand`](http://eslint.org/docs/rules/object-shorthand.html) jscs: [`requireEnhancedObjectLiterals`](http://jscs.info/rule/requireEnhancedObjectLiterals)\r\n\r\n    > Why? It is shorter to write and descriptive.\r\n\r\n    ```javascript\r\n    const lukeSkywalker = 'Luke Skywalker';\r\n\r\n    // bad\r\n    const obj = {\r\n      lukeSkywalker: lukeSkywalker,\r\n    };\r\n\r\n    // good\r\n    const obj = {\r\n      lukeSkywalker,\r\n    };\r\n    ```\r\n\r\n  <a name=\"objects--grouped-shorthand\"></a><a name=\"3.7\"></a>\r\n  - [3.7](#objects--grouped-shorthand) Group your shorthand properties at the beginning of your object declaration.\r\n\r\n    > Why? It's easier to tell which properties are using the shorthand.\r\n\r\n    ```javascript\r\n    const anakinSkywalker = 'Anakin Skywalker';\r\n    const lukeSkywalker = 'Luke Skywalker';\r\n\r\n    // bad\r\n    const obj = {\r\n      episodeOne: 1,\r\n      twoJediWalkIntoACantina: 2,\r\n      lukeSkywalker,\r\n      episodeThree: 3,\r\n      mayTheFourth: 4,\r\n      anakinSkywalker,\r\n    };\r\n\r\n    // good\r\n    const obj = {\r\n      lukeSkywalker,\r\n      anakinSkywalker,\r\n      episodeOne: 1,\r\n      twoJediWalkIntoACantina: 2,\r\n      episodeThree: 3,\r\n      mayTheFourth: 4,\r\n    };\r\n    ```\r\n\r\n  <a name=\"objects--quoted-props\"></a><a name=\"3.8\"></a>\r\n  - [3.8](#objects--quoted-props) Only quote properties that are invalid identifiers. eslint: [`quote-props`](http://eslint.org/docs/rules/quote-props.html) jscs: [`disallowQuotedKeysInObjects`](http://jscs.info/rule/disallowQuotedKeysInObjects)\r\n\r\n  > Why? In general we consider it subjectively easier to read. It improves syntax highlighting, and is also more easily optimized by many JS engines.\r\n\r\n  ```javascript\r\n  // bad\r\n  const bad = {\r\n    'foo': 3,\r\n    'bar': 4,\r\n    'data-blah': 5,\r\n  };\r\n\r\n  // good\r\n  const good = {\r\n    foo: 3,\r\n    bar: 4,\r\n    'data-blah': 5,\r\n  };\r\n  ```\r\n\r\n  <a name=\"objects--prototype-builtins\"></a>\r\n  - [3.9](#objects--prototype-builtins) Do not call `Object.prototype` methods directly, such as `hasOwnProperty`, `propertyIsEnumerable`, and `isPrototypeOf`.\r\n\r\n  > Why? These methods may be shadowed by properties on the object in question - consider `{ hasOwnProperty: false }` - or, the object may be a null object (`Object.create(null)`).\r\n\r\n  ```javascript\r\n  // bad\r\n  console.log(object.hasOwnProperty(key));\r\n\r\n  // good\r\n  console.log(Object.prototype.hasOwnProperty.call(object, key));\r\n\r\n  // best\r\n  const has = Object.prototype.hasOwnProperty; // cache the lookup once, in module scope.\r\n  /* or */\r\n  const has = require('has');\r\n  …\r\n  console.log(has.call(object, key));\r\n  ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Arrays\r\n\r\n  <a name=\"arrays--literals\"></a><a name=\"4.1\"></a>\r\n  - [4.1](#arrays--literals) Use the literal syntax for array creation. eslint: [`no-array-constructor`](http://eslint.org/docs/rules/no-array-constructor.html)\r\n\r\n    ```javascript\r\n    // bad\r\n    const items = new Array();\r\n\r\n    // good\r\n    const items = [];\r\n    ```\r\n\r\n  <a name=\"arrays--push\"></a><a name=\"4.2\"></a>\r\n  - [4.2](#arrays--push) Use [Array#push](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/push) instead of direct assignment to add items to an array.\r\n\r\n    ```javascript\r\n    const someStack = [];\r\n\r\n    // bad\r\n    someStack[someStack.length] = 'abracadabra';\r\n\r\n    // good\r\n    someStack.push('abracadabra');\r\n    ```\r\n\r\n  <a name=\"es6-array-spreads\"></a><a name=\"4.3\"></a>\r\n  - [4.3](#es6-array-spreads) Use array spreads `...` to copy arrays.\r\n\r\n    ```javascript\r\n    // bad\r\n    const len = items.length;\r\n    const itemsCopy = [];\r\n    let i;\r\n\r\n    for (i = 0; i < len; i++) {\r\n      itemsCopy[i] = items[i];\r\n    }\r\n\r\n    // good\r\n    const itemsCopy = [...items];\r\n    ```\r\n\r\n  <a name=\"arrays--from\"></a><a name=\"4.4\"></a>\r\n  - [4.4](#arrays--from) To convert an array-like object to an array, use [Array.from](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/from).\r\n\r\n    ```javascript\r\n    const foo = document.querySelectorAll('.foo');\r\n    const nodes = Array.from(foo);\r\n    ```\r\n\r\n  <a name=\"arrays--callback-return\"></a><a name=\"4.5\"></a>\r\n  - [4.5](#arrays--callback-return) Use return statements in array method callbacks. It's ok to omit the return if the function body consists of a single statement following [8.2](#8.2). eslint: [`array-callback-return`](http://eslint.org/docs/rules/array-callback-return)\r\n\r\n    ```javascript\r\n    // good\r\n    [1, 2, 3].map((x) => {\r\n      const y = x + 1;\r\n      return x * y;\r\n    });\r\n\r\n    // good\r\n    [1, 2, 3].map(x => x + 1);\r\n\r\n    // bad\r\n    const flat = {};\r\n    [[0, 1], [2, 3], [4, 5]].reduce((memo, item, index) => {\r\n      const flatten = memo.concat(item);\r\n      flat[index] = flatten;\r\n    });\r\n\r\n    // good\r\n    const flat = {};\r\n    [[0, 1], [2, 3], [4, 5]].reduce((memo, item, index) => {\r\n      const flatten = memo.concat(item);\r\n      flat[index] = flatten;\r\n      return flatten;\r\n    });\r\n\r\n    // bad\r\n    inbox.filter((msg) => {\r\n      const { subject, author } = msg;\r\n      if (subject === 'Mockingbird') {\r\n        return author === 'Harper Lee';\r\n      } else {\r\n        return false;\r\n      }\r\n    });\r\n\r\n    // good\r\n    inbox.filter((msg) => {\r\n      const { subject, author } = msg;\r\n      if (subject === 'Mockingbird') {\r\n        return author === 'Harper Lee';\r\n      }\r\n\r\n      return false;\r\n    });\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Destructuring\r\n\r\n  <a name=\"destructuring--object\"></a><a name=\"5.1\"></a>\r\n  - [5.1](#destructuring--object) Use object destructuring when accessing and using multiple properties of an object. jscs: [`requireObjectDestructuring`](http://jscs.info/rule/requireObjectDestructuring)\r\n\r\n    > Why? Destructuring saves you from creating temporary references for those properties.\r\n\r\n    ```javascript\r\n    // bad\r\n    function getFullName(user) {\r\n      const firstName = user.firstName;\r\n      const lastName = user.lastName;\r\n\r\n      return `${firstName} ${lastName}`;\r\n    }\r\n\r\n    // good\r\n    function getFullName(user) {\r\n      const { firstName, lastName } = user;\r\n      return `${firstName} ${lastName}`;\r\n    }\r\n\r\n    // best\r\n    function getFullName({ firstName, lastName }) {\r\n      return `${firstName} ${lastName}`;\r\n    }\r\n    ```\r\n\r\n  <a name=\"destructuring--array\"></a><a name=\"5.2\"></a>\r\n  - [5.2](#destructuring--array) Use array destructuring. jscs: [`requireArrayDestructuring`](http://jscs.info/rule/requireArrayDestructuring)\r\n\r\n    ```javascript\r\n    const arr = [1, 2, 3, 4];\r\n\r\n    // bad\r\n    const first = arr[0];\r\n    const second = arr[1];\r\n\r\n    // good\r\n    const [first, second] = arr;\r\n    ```\r\n\r\n  <a name=\"destructuring--object-over-array\"></a><a name=\"5.3\"></a>\r\n  - [5.3](#destructuring--object-over-array) Use object destructuring for multiple return values, not array destructuring. jscs: [`disallowArrayDestructuringReturn`](http://jscs.info/rule/disallowArrayDestructuringReturn)\r\n\r\n    > Why? You can add new properties over time or change the order of things without breaking call sites.\r\n\r\n    ```javascript\r\n    // bad\r\n    function processInput(input) {\r\n      // then a miracle occurs\r\n      return [left, right, top, bottom];\r\n    }\r\n\r\n    // the caller needs to think about the order of return data\r\n    const [left, __, top] = processInput(input);\r\n\r\n    // good\r\n    function processInput(input) {\r\n      // then a miracle occurs\r\n      return { left, right, top, bottom };\r\n    }\r\n\r\n    // the caller selects only the data they need\r\n    const { left, top } = processInput(input);\r\n    ```\r\n\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Strings\r\n\r\n  <a name=\"strings--quotes\"></a><a name=\"6.1\"></a>\r\n  - [6.1](#strings--quotes) Use single quotes `''` for strings. eslint: [`quotes`](http://eslint.org/docs/rules/quotes.html) jscs: [`validateQuoteMarks`](http://jscs.info/rule/validateQuoteMarks)\r\n\r\n    ```javascript\r\n    // bad\r\n    const name = \"Capt. Janeway\";\r\n\r\n    // good\r\n    const name = 'Capt. Janeway';\r\n    ```\r\n\r\n  <a name=\"strings--line-length\"></a><a name=\"6.2\"></a>\r\n  - [6.2](#strings--line-length) Strings that cause the line to go over 100 characters should be written across multiple lines using string concatenation.\r\n\r\n  <a name=\"strings--concat-perf\"></a><a name=\"6.3\"></a>\r\n  - [6.3](#strings--concat-perf) Note: If overused, long strings with concatenation could impact performance. [jsPerf](http://jsperf.com/ya-string-concat) & [Discussion](https://github.com/airbnb/javascript/issues/40).\r\n\r\n    ```javascript\r\n    // bad\r\n    const errorMessage = 'This is a super long error that was thrown because of Batman. When you stop to think about how Batman had anything to do with this, you would get nowhere fast.';\r\n\r\n    // bad\r\n    const errorMessage = 'This is a super long error that was thrown because \\\r\n    of Batman. When you stop to think about how Batman had anything to do \\\r\n    with this, you would get nowhere \\\r\n    fast.';\r\n\r\n    // good\r\n    const errorMessage = 'This is a super long error that was thrown because ' +\r\n      'of Batman. When you stop to think about how Batman had anything to do ' +\r\n      'with this, you would get nowhere fast.';\r\n    ```\r\n\r\n  <a name=\"es6-template-literals\"></a><a name=\"6.4\"></a>\r\n  - [6.4](#es6-template-literals) When programmatically building up strings, use template strings instead of concatenation. eslint: [`prefer-template`](http://eslint.org/docs/rules/prefer-template.html) [`template-curly-spacing`](http://eslint.org/docs/rules/template-curly-spacing) jscs: [`requireTemplateStrings`](http://jscs.info/rule/requireTemplateStrings)\r\n\r\n    > Why? Template strings give you a readable, concise syntax with proper newlines and string interpolation features.\r\n\r\n    ```javascript\r\n    // bad\r\n    function sayHi(name) {\r\n      return 'How are you, ' + name + '?';\r\n    }\r\n\r\n    // bad\r\n    function sayHi(name) {\r\n      return ['How are you, ', name, '?'].join();\r\n    }\r\n\r\n    // bad\r\n    function sayHi(name) {\r\n      return `How are you, ${ name }?`;\r\n    }\r\n\r\n    // good\r\n    function sayHi(name) {\r\n      return `How are you, ${name}?`;\r\n    }\r\n    ```\r\n\r\n  <a name=\"strings--eval\"></a><a name=\"6.5\"></a>\r\n  - [6.5](#strings--eval) Never use `eval()` on a string, it opens too many vulnerabilities.\r\n\r\n  <a name=\"strings--escaping\"></a>\r\n  - [6.6](#strings--escaping) Do not unnecessarily escape characters in strings. eslint: [`no-useless-escape`](http://eslint.org/docs/rules/no-useless-escape)\r\n\r\n    > Why? Backslashes harm readability, thus they should only be present when necessary.\r\n\r\n    ```javascript\r\n    // bad\r\n    const foo = '\\'this\\' \\i\\s \\\"quoted\\\"';\r\n\r\n    // good\r\n    const foo = '\\'this\\' is \"quoted\"';\r\n    const foo = `'this' is \"quoted\"`;\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Functions\r\n\r\n  <a name=\"functions--declarations\"></a><a name=\"7.1\"></a>\r\n  - [7.1](#functions--declarations) Use function declarations instead of function expressions. jscs: [`requireFunctionDeclarations`](http://jscs.info/rule/requireFunctionDeclarations)\r\n\r\n    > Why? Function declarations are named, so they're easier to identify in call stacks. Also, the whole body of a function declaration is hoisted, whereas only the reference of a function expression is hoisted. This rule makes it possible to always use [Arrow Functions](#arrow-functions) in place of function expressions.\r\n\r\n    ```javascript\r\n    // bad\r\n    const foo = function () {\r\n    };\r\n\r\n    // good\r\n    function foo() {\r\n    }\r\n    ```\r\n\r\n  <a name=\"functions--iife\"></a><a name=\"7.2\"></a>\r\n  - [7.2](#functions--iife) Wrap immediately invoked function expressions in parentheses. eslint: [`wrap-iife`](http://eslint.org/docs/rules/wrap-iife.html) jscs: [`requireParenthesesAroundIIFE`](http://jscs.info/rule/requireParenthesesAroundIIFE)\r\n\r\n    > Why? An immediately invoked function expression is a single unit - wrapping both it, and its invocation parens, in parens, cleanly expresses this. Note that in a world with modules everywhere, you almost never need an IIFE.\r\n\r\n    ```javascript\r\n    // immediately-invoked function expression (IIFE)\r\n    (function () {\r\n      console.log('Welcome to the Internet. Please follow me.');\r\n    }());\r\n    ```\r\n\r\n  <a name=\"functions--in-blocks\"></a><a name=\"7.3\"></a>\r\n  - [7.3](#functions--in-blocks) Never declare a function in a non-function block (if, while, etc). Assign the function to a variable instead. Browsers will allow you to do it, but they all interpret it differently, which is bad news bears. eslint: [`no-loop-func`](http://eslint.org/docs/rules/no-loop-func.html)\r\n\r\n  <a name=\"functions--note-on-blocks\"></a><a name=\"7.4\"></a>\r\n  - [7.4](#functions--note-on-blocks) **Note:** ECMA-262 defines a `block` as a list of statements. A function declaration is not a statement. [Read ECMA-262's note on this issue](http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf#page=97).\r\n\r\n    ```javascript\r\n    // bad\r\n    if (currentUser) {\r\n      function test() {\r\n        console.log('Nope.');\r\n      }\r\n    }\r\n\r\n    // good\r\n    let test;\r\n    if (currentUser) {\r\n      test = () => {\r\n        console.log('Yup.');\r\n      };\r\n    }\r\n    ```\r\n\r\n  <a name=\"functions--arguments-shadow\"></a><a name=\"7.5\"></a>\r\n  - [7.5](#functions--arguments-shadow) Never name a parameter `arguments`. This will take precedence over the `arguments` object that is given to every function scope.\r\n\r\n    ```javascript\r\n    // bad\r\n    function nope(name, options, arguments) {\r\n      // ...stuff...\r\n    }\r\n\r\n    // good\r\n    function yup(name, options, args) {\r\n      // ...stuff...\r\n    }\r\n    ```\r\n\r\n  <a name=\"es6-rest\"></a><a name=\"7.6\"></a>\r\n  - [7.6](#es6-rest) Never use `arguments`, opt to use rest syntax `...` instead. eslint: [`prefer-rest-params`](http://eslint.org/docs/rules/prefer-rest-params)\r\n\r\n    > Why? `...` is explicit about which arguments you want pulled. Plus, rest arguments are a real Array, and not merely Array-like like `arguments`.\r\n\r\n    ```javascript\r\n    // bad\r\n    function concatenateAll() {\r\n      const args = Array.prototype.slice.call(arguments);\r\n      return args.join('');\r\n    }\r\n\r\n    // good\r\n    function concatenateAll(...args) {\r\n      return args.join('');\r\n    }\r\n    ```\r\n\r\n  <a name=\"es6-default-parameters\"></a><a name=\"7.7\"></a>\r\n  - [7.7](#es6-default-parameters) Use default parameter syntax rather than mutating function arguments.\r\n\r\n    ```javascript\r\n    // really bad\r\n    function handleThings(opts) {\r\n      // No! We shouldn't mutate function arguments.\r\n      // Double bad: if opts is falsy it'll be set to an object which may\r\n      // be what you want but it can introduce subtle bugs.\r\n      opts = opts || {};\r\n      // ...\r\n    }\r\n\r\n    // still bad\r\n    function handleThings(opts) {\r\n      if (opts === void 0) {\r\n        opts = {};\r\n      }\r\n      // ...\r\n    }\r\n\r\n    // good\r\n    function handleThings(opts = {}) {\r\n      // ...\r\n    }\r\n    ```\r\n\r\n  <a name=\"functions--default-side-effects\"></a><a name=\"7.8\"></a>\r\n  - [7.8](#functions--default-side-effects) Avoid side effects with default parameters.\r\n\r\n    > Why? They are confusing to reason about.\r\n\r\n    ```javascript\r\n    var b = 1;\r\n    // bad\r\n    function count(a = b++) {\r\n      console.log(a);\r\n    }\r\n    count();  // 1\r\n    count();  // 2\r\n    count(3); // 3\r\n    count();  // 3\r\n    ```\r\n\r\n  <a name=\"functions--defaults-last\"></a><a name=\"7.9\"></a>\r\n  - [7.9](#functions--defaults-last) Always put default parameters last.\r\n\r\n    ```javascript\r\n    // bad\r\n    function handleThings(opts = {}, name) {\r\n      // ...\r\n    }\r\n\r\n    // good\r\n    function handleThings(name, opts = {}) {\r\n      // ...\r\n    }\r\n    ```\r\n\r\n  <a name=\"functions--constructor\"></a><a name=\"7.10\"></a>\r\n  - [7.10](#functions--constructor) Never use the Function constructor to create a new function.\r\n\r\n    > Why? Creating a function in this way evaluates a string similarly to eval(), which opens vulnerabilities.\r\n\r\n    ```javascript\r\n    // bad\r\n    var add = new Function('a', 'b', 'return a + b');\r\n\r\n    // still bad\r\n    var subtract = Function('a', 'b', 'return a - b');\r\n    ```\r\n\r\n  <a name=\"functions--signature-spacing\"></a><a name=\"7.11\"></a>\r\n  - [7.11](#functions--signature-spacing) Spacing in a function signature.\r\n\r\n    > Why? Consistency is good, and you shouldn’t have to add or remove a space when adding or removing a name.\r\n\r\n    ```javascript\r\n    // bad\r\n    const f = function(){};\r\n    const g = function (){};\r\n    const h = function() {};\r\n\r\n    // good\r\n    const x = function () {};\r\n    const y = function a() {};\r\n    ```\r\n\r\n  <a name=\"functions--mutate-params\"></a><a name=\"7.12\"></a>\r\n  - [7.12](#functions--mutate-params) Never mutate parameters. eslint: [`no-param-reassign`](http://eslint.org/docs/rules/no-param-reassign.html)\r\n\r\n    > Why? Manipulating objects passed in as parameters can cause unwanted variable side effects in the original caller.\r\n\r\n    ```javascript\r\n    // bad\r\n    function f1(obj) {\r\n      obj.key = 1;\r\n    };\r\n\r\n    // good\r\n    function f2(obj) {\r\n      const key = Object.prototype.hasOwnProperty.call(obj, 'key') ? obj.key : 1;\r\n    };\r\n    ```\r\n\r\n  <a name=\"functions--reassign-params\"></a><a name=\"7.13\"></a>\r\n  - [7.13](#functions--reassign-params) Never reassign parameters. eslint: [`no-param-reassign`](http://eslint.org/docs/rules/no-param-reassign.html)\r\n\r\n    > Why? Reassigning parameters can lead to unexpected behavior, especially when accessing the `arguments` object. It can also cause optimization issues, especially in V8.\r\n\r\n    ```javascript\r\n    // bad\r\n    function f1(a) {\r\n      a = 1;\r\n    }\r\n\r\n    function f2(a) {\r\n      if (!a) { a = 1; }\r\n    }\r\n\r\n    // good\r\n    function f3(a) {\r\n      const b = a || 1;\r\n    }\r\n\r\n    function f4(a = 1) {\r\n    }\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Arrow Functions\r\n\r\n  <a name=\"arrows--use-them\"></a><a name=\"8.1\"></a>\r\n  - [8.1](#arrows--use-them) When you must use function expressions (as when passing an anonymous function), use arrow function notation. eslint: [`prefer-arrow-callback`](http://eslint.org/docs/rules/prefer-arrow-callback.html), [`arrow-spacing`](http://eslint.org/docs/rules/arrow-spacing.html) jscs: [`requireArrowFunctions`](http://jscs.info/rule/requireArrowFunctions)\r\n\r\n    > Why? It creates a version of the function that executes in the context of `this`, which is usually what you want, and is a more concise syntax.\r\n\r\n    > Why not? If you have a fairly complicated function, you might move that logic out into its own function declaration.\r\n\r\n    ```javascript\r\n    // bad\r\n    [1, 2, 3].map(function (x) {\r\n      const y = x + 1;\r\n      return x * y;\r\n    });\r\n\r\n    // good\r\n    [1, 2, 3].map((x) => {\r\n      const y = x + 1;\r\n      return x * y;\r\n    });\r\n    ```\r\n\r\n  <a name=\"arrows--implicit-return\"></a><a name=\"8.2\"></a>\r\n  - [8.2](#arrows--implicit-return) If the function body consists of a single expression, omit the braces and use the implicit return. Otherwise, keep the braces and use a `return` statement. eslint: [`arrow-parens`](http://eslint.org/docs/rules/arrow-parens.html), [`arrow-body-style`](http://eslint.org/docs/rules/arrow-body-style.html) jscs:  [`disallowParenthesesAroundArrowParam`](http://jscs.info/rule/disallowParenthesesAroundArrowParam), [`requireShorthandArrowFunctions`](http://jscs.info/rule/requireShorthandArrowFunctions)\r\n\r\n    > Why? Syntactic sugar. It reads well when multiple functions are chained together.\r\n\r\n    ```javascript\r\n    // bad\r\n    [1, 2, 3].map(number => {\r\n      const nextNumber = number + 1;\r\n      `A string containing the ${nextNumber}.`;\r\n    });\r\n\r\n    // good\r\n    [1, 2, 3].map(number => `A string containing the ${number}.`);\r\n\r\n    // good\r\n    [1, 2, 3].map((number) => {\r\n      const nextNumber = number + 1;\r\n      return `A string containing the ${nextNumber}.`;\r\n    });\r\n\r\n    // good\r\n    [1, 2, 3].map((number, index) => ({\r\n      index: number\r\n    }));\r\n    ```\r\n\r\n  <a name=\"arrows--paren-wrap\"></a><a name=\"8.3\"></a>\r\n  - [8.3](#arrows--paren-wrap) In case the expression spans over multiple lines, wrap it in parentheses for better readability.\r\n\r\n    > Why? It shows clearly where the function starts and ends.\r\n\r\n    ```js\r\n    // bad\r\n    [1, 2, 3].map(number => 'As time went by, the string containing the ' +\r\n      `${number} became much longer. So we needed to break it over multiple ` +\r\n      'lines.'\r\n    );\r\n\r\n    // good\r\n    [1, 2, 3].map(number => (\r\n      `As time went by, the string containing the ${number} became much ` +\r\n      'longer. So we needed to break it over multiple lines.'\r\n    ));\r\n    ```\r\n\r\n  <a name=\"arrows--one-arg-parens\"></a><a name=\"8.4\"></a>\r\n  - [8.4](#arrows--one-arg-parens) If your function takes a single argument and doesn’t use braces, omit the parentheses. Otherwise, always include parentheses around arguments. eslint: [`arrow-parens`](http://eslint.org/docs/rules/arrow-parens.html) jscs:  [`disallowParenthesesAroundArrowParam`](http://jscs.info/rule/disallowParenthesesAroundArrowParam)\r\n\r\n    > Why? Less visual clutter.\r\n\r\n    ```js\r\n    // bad\r\n    [1, 2, 3].map((x) => x * x);\r\n\r\n    // good\r\n    [1, 2, 3].map(x => x * x);\r\n\r\n    // good\r\n    [1, 2, 3].map(number => (\r\n      `A long string with the ${number}. It’s so long that we’ve broken it ` +\r\n      'over multiple lines!'\r\n    ));\r\n\r\n    // bad\r\n    [1, 2, 3].map(x => {\r\n      const y = x + 1;\r\n      return x * y;\r\n    });\r\n\r\n    // good\r\n    [1, 2, 3].map((x) => {\r\n      const y = x + 1;\r\n      return x * y;\r\n    });\r\n    ```\r\n\r\n  <a name=\"arrows--confusing\"></a><a name=\"8.5\"></a>\r\n  - [8.5](#arrows--confusing) Avoid confusing arrow function syntax (`=>`) with comparison operators (`<=`, `>=`). eslint: [`no-confusing-arrow`](http://eslint.org/docs/rules/no-confusing-arrow)\r\n\r\n    ```js\r\n    // bad\r\n    const itemHeight = item => item.height > 256 ? item.largeSize : item.smallSize;\r\n\r\n    // bad\r\n    const itemHeight = (item) => item.height > 256 ? item.largeSize : item.smallSize;\r\n\r\n    // good\r\n    const itemHeight = (item) => { return item.height > 256 ? item.largeSize : item.smallSize; };\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Classes & Constructors\r\n\r\n  <a name=\"constructors--use-class\"></a><a name=\"9.1\"></a>\r\n  - [9.1](#constructors--use-class) Always use `class`. Avoid manipulating `prototype` directly.\r\n\r\n    > Why? `class` syntax is more concise and easier to reason about.\r\n\r\n    ```javascript\r\n    // bad\r\n    function Queue(contents = []) {\r\n      this.queue = [...contents];\r\n    }\r\n    Queue.prototype.pop = function () {\r\n      const value = this.queue[0];\r\n      this.queue.splice(0, 1);\r\n      return value;\r\n    };\r\n\r\n\r\n    // good\r\n    class Queue {\r\n      constructor(contents = []) {\r\n        this.queue = [...contents];\r\n      }\r\n      pop() {\r\n        const value = this.queue[0];\r\n        this.queue.splice(0, 1);\r\n        return value;\r\n      }\r\n    }\r\n    ```\r\n\r\n  <a name=\"constructors--extends\"></a><a name=\"9.2\"></a>\r\n  - [9.2](#constructors--extends) Use `extends` for inheritance.\r\n\r\n    > Why? It is a built-in way to inherit prototype functionality without breaking `instanceof`.\r\n\r\n    ```javascript\r\n    // bad\r\n    const inherits = require('inherits');\r\n    function PeekableQueue(contents) {\r\n      Queue.apply(this, contents);\r\n    }\r\n    inherits(PeekableQueue, Queue);\r\n    PeekableQueue.prototype.peek = function () {\r\n      return this._queue[0];\r\n    }\r\n\r\n    // good\r\n    class PeekableQueue extends Queue {\r\n      peek() {\r\n        return this._queue[0];\r\n      }\r\n    }\r\n    ```\r\n\r\n  <a name=\"constructors--chaining\"></a><a name=\"9.3\"></a>\r\n  - [9.3](#constructors--chaining) Methods can return `this` to help with method chaining.\r\n\r\n    ```javascript\r\n    // bad\r\n    Jedi.prototype.jump = function () {\r\n      this.jumping = true;\r\n      return true;\r\n    };\r\n\r\n    Jedi.prototype.setHeight = function (height) {\r\n      this.height = height;\r\n    };\r\n\r\n    const luke = new Jedi();\r\n    luke.jump(); // => true\r\n    luke.setHeight(20); // => undefined\r\n\r\n    // good\r\n    class Jedi {\r\n      jump() {\r\n        this.jumping = true;\r\n        return this;\r\n      }\r\n\r\n      setHeight(height) {\r\n        this.height = height;\r\n        return this;\r\n      }\r\n    }\r\n\r\n    const luke = new Jedi();\r\n\r\n    luke.jump()\r\n      .setHeight(20);\r\n    ```\r\n\r\n\r\n  <a name=\"constructors--tostring\"></a><a name=\"9.4\"></a>\r\n  - [9.4](#constructors--tostring) It's okay to write a custom toString() method, just make sure it works successfully and causes no side effects.\r\n\r\n    ```javascript\r\n    class Jedi {\r\n      constructor(options = {}) {\r\n        this.name = options.name || 'no name';\r\n      }\r\n\r\n      getName() {\r\n        return this.name;\r\n      }\r\n\r\n      toString() {\r\n        return `Jedi - ${this.getName()}`;\r\n      }\r\n    }\r\n    ```\r\n\r\n  <a name=\"constructors--no-useless\"></a><a name=\"9.5\"></a>\r\n  - [9.5](#constructors--no-useless) Classes have a default constructor if one is not specified. An empty constructor function or one that just delegates to a parent class is unnecessary. eslint: [`no-useless-constructor`](http://eslint.org/docs/rules/no-useless-constructor)\r\n\r\n    ```javascript\r\n    // bad\r\n    class Jedi {\r\n      constructor() {}\r\n\r\n      getName() {\r\n        return this.name;\r\n      }\r\n    }\r\n\r\n    // bad\r\n    class Rey extends Jedi {\r\n      constructor(...args) {\r\n        super(...args);\r\n      }\r\n    }\r\n\r\n    // good\r\n    class Rey extends Jedi {\r\n      constructor(...args) {\r\n        super(...args);\r\n        this.name = 'Rey';\r\n      }\r\n    }\r\n    ```\r\n\r\n  <a name=\"classes--no-duplicate-members\"></a>\r\n  - [9.6](#classes--no-duplicate-members) Avoid duplicate class members. eslint: [`no-dupe-class-members`](http://eslint.org/docs/rules/no-dupe-class-members)\r\n\r\n    > Why? Duplicate class member declarations will silently prefer the last one - having duplicates is almost certainly a bug.\r\n\r\n    ```javascript\r\n    // bad\r\n    class Foo {\r\n      bar() { return 1; }\r\n      bar() { return 2; }\r\n    }\r\n\r\n    // good\r\n    class Foo {\r\n      bar() { return 1; }\r\n    }\r\n\r\n    // good\r\n    class Foo {\r\n      bar() { return 2; }\r\n    }\r\n    ```\r\n\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Modules\r\n\r\n  <a name=\"modules--use-them\"></a><a name=\"10.1\"></a>\r\n  - [10.1](#modules--use-them) Always use modules (`import`/`export`) over a non-standard module system. You can always transpile to your preferred module system.\r\n\r\n    > Why? Modules are the future, let's start using the future now.\r\n\r\n    ```javascript\r\n    // bad\r\n    const AirbnbStyleGuide = require('./AirbnbStyleGuide');\r\n    module.exports = AirbnbStyleGuide.es6;\r\n\r\n    // ok\r\n    import AirbnbStyleGuide from './AirbnbStyleGuide';\r\n    export default AirbnbStyleGuide.es6;\r\n\r\n    // best\r\n    import { es6 } from './AirbnbStyleGuide';\r\n    export default es6;\r\n    ```\r\n\r\n  <a name=\"modules--no-wildcard\"></a><a name=\"10.2\"></a>\r\n  - [10.2](#modules--no-wildcard) Do not use wildcard imports.\r\n\r\n    > Why? This makes sure you have a single default export.\r\n\r\n    ```javascript\r\n    // bad\r\n    import * as AirbnbStyleGuide from './AirbnbStyleGuide';\r\n\r\n    // good\r\n    import AirbnbStyleGuide from './AirbnbStyleGuide';\r\n    ```\r\n\r\n  <a name=\"modules--no-export-from-import\"></a><a name=\"10.3\"></a>\r\n  - [10.3](#modules--no-export-from-import) And do not export directly from an import.\r\n\r\n    > Why? Although the one-liner is concise, having one clear way to import and one clear way to export makes things consistent.\r\n\r\n    ```javascript\r\n    // bad\r\n    // filename es6.js\r\n    export { es6 as default } from './airbnbStyleGuide';\r\n\r\n    // good\r\n    // filename es6.js\r\n    import { es6 } from './AirbnbStyleGuide';\r\n    export default es6;\r\n    ```\r\n\r\n  <a name=\"modules--no-duplicate-imports\"></a>\r\n  - [10.4](#modules--no-duplicate-imports) Only import from a path in one place.\r\n eslint: [`no-duplicate-imports`](http://eslint.org/docs/rules/no-duplicate-imports)\r\n    > Why? Having multiple lines that import from the same path can make code harder to maintain.\r\n\r\n    ```javascript\r\n    // bad\r\n    import foo from 'foo';\r\n    // … some other imports … //\r\n    import { named1, named2 } from 'foo';\r\n\r\n    // good\r\n    import foo, { named1, named2 } from 'foo';\r\n\r\n    // good\r\n    import foo, {\r\n      named1,\r\n      named2,\r\n    } from 'foo';\r\n    ```\r\n\r\n  <a name=\"modules--no-mutable-exports\"></a>\r\n  - [10.5](#modules--no-mutable-exports) Do not export mutable bindings.\r\n eslint: [`import/no-mutable-exports`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-mutable-exports.md)\r\n    > Why? Mutation should be avoided in general, but in particular when exporting mutable bindings. While this technique may be needed for some special cases, in general, only constant references should be exported.\r\n\r\n    ```javascript\r\n    // bad\r\n    let foo = 3;\r\n    export { foo }\r\n\r\n    // good\r\n    const foo = 3;\r\n    export { foo }\r\n    ```\r\n\r\n  <a name=\"modules--prefer-default-export\"></a>\r\n  - [10.6](#modules--prefer-default-export) In modules with a single export, prefer default export over named export.\r\n eslint: [`import/prefer-default-export`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/prefer-default-export.md)\r\n\r\n    ```javascript\r\n    // bad\r\n    export function foo() {}\r\n\r\n    // good\r\n    export default function foo() {}\r\n    ```\r\n\r\n  <a name=\"modules--imports-first\"></a>\r\n  - [10.7](#modules--imports-first) Put all `import`s above non-import statements.\r\n eslint: [`import/imports-first`](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/imports-first.md)\r\n    > Why? Since `import`s are hoisted, keeping them all at the top prevents surprising behavior.\r\n\r\n    ```javascript\r\n    // bad\r\n    import foo from 'foo';\r\n    foo.init();\r\n\r\n    import bar from 'bar';\r\n\r\n    // good\r\n    import foo from 'foo';\r\n    import bar from 'bar';\r\n\r\n    foo.init();\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Iterators and Generators\r\n\r\n  <a name=\"iterators--nope\"></a><a name=\"11.1\"></a>\r\n  - [11.1](#iterators--nope) Don't use iterators. Prefer JavaScript's higher-order functions like `map()` and `reduce()` instead of loops like `for-of`. eslint: [`no-iterator`](http://eslint.org/docs/rules/no-iterator.html)\r\n\r\n    > Why? This enforces our immutable rule. Dealing with pure functions that return values is easier to reason about than side effects.\r\n\r\n    ```javascript\r\n    const numbers = [1, 2, 3, 4, 5];\r\n\r\n    // bad\r\n    let sum = 0;\r\n    for (let num of numbers) {\r\n      sum += num;\r\n    }\r\n\r\n    sum === 15;\r\n\r\n    // good\r\n    let sum = 0;\r\n    numbers.forEach(num => sum += num);\r\n    sum === 15;\r\n\r\n    // best (use the functional force)\r\n    const sum = numbers.reduce((total, num) => total + num, 0);\r\n    sum === 15;\r\n    ```\r\n\r\n  <a name=\"generators--nope\"></a><a name=\"11.2\"></a>\r\n  - [11.2](#generators--nope) Don't use generators for now.\r\n\r\n    > Why? They don't transpile well to ES5.\r\n\r\n  <a name=\"generators--spacing\"></a>\r\n  - [11.3](#generators--spacing) If you must use generators, or if you disregard [our advice](#generators--nope), make sure their function signature is spaced properly. eslint: [`generator-star-spacing`](http://eslint.org/docs/rules/generator-star-spacing)\r\n\r\n    > Why? `function` and `*` are part of the same conceptual keyword - `*` is not a modifier for `function`, `function*` is a unique construct, different from `function`.\r\n\r\n    ```js\r\n    // bad\r\n    function * foo() {\r\n    }\r\n\r\n    const bar = function * () {\r\n    }\r\n\r\n    const baz = function *() {\r\n    }\r\n\r\n    const quux = function*() {\r\n    }\r\n\r\n    function*foo() {\r\n    }\r\n\r\n    function *foo() {\r\n    }\r\n\r\n    // very bad\r\n    function\r\n    *\r\n    foo() {\r\n    }\r\n\r\n    const wat = function\r\n    *\r\n    () {\r\n    }\r\n\r\n    // good\r\n    function* foo() {\r\n    }\r\n\r\n    const foo = function* () {\r\n    }\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Properties\r\n\r\n  <a name=\"properties--dot\"></a><a name=\"12.1\"></a>\r\n  - [12.1](#properties--dot) Use dot notation when accessing properties. eslint: [`dot-notation`](http://eslint.org/docs/rules/dot-notation.html) jscs: [`requireDotNotation`](http://jscs.info/rule/requireDotNotation)\r\n\r\n    ```javascript\r\n    const luke = {\r\n      jedi: true,\r\n      age: 28,\r\n    };\r\n\r\n    // bad\r\n    const isJedi = luke['jedi'];\r\n\r\n    // good\r\n    const isJedi = luke.jedi;\r\n    ```\r\n\r\n  <a name=\"properties--bracket\"></a><a name=\"12.2\"></a>\r\n  - [12.2](#properties--bracket) Use bracket notation `[]` when accessing properties with a variable.\r\n\r\n    ```javascript\r\n    const luke = {\r\n      jedi: true,\r\n      age: 28,\r\n    };\r\n\r\n    function getProp(prop) {\r\n      return luke[prop];\r\n    }\r\n\r\n    const isJedi = getProp('jedi');\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Variables\r\n\r\n  <a name=\"variables--const\"></a><a name=\"13.1\"></a>\r\n  - [13.1](#variables--const) Always use `const` to declare variables. Not doing so will result in global variables. We want to avoid polluting the global namespace. Captain Planet warned us of that.\r\n\r\n    ```javascript\r\n    // bad\r\n    superPower = new SuperPower();\r\n\r\n    // good\r\n    const superPower = new SuperPower();\r\n    ```\r\n\r\n  <a name=\"variables--one-const\"></a><a name=\"13.2\"></a>\r\n  - [13.2](#variables--one-const) Use one `const` declaration per variable. eslint: [`one-var`](http://eslint.org/docs/rules/one-var.html) jscs: [`disallowMultipleVarDecl`](http://jscs.info/rule/disallowMultipleVarDecl)\r\n\r\n    > Why? It's easier to add new variable declarations this way, and you never have to worry about swapping out a `;` for a `,` or introducing punctuation-only diffs. You can also step through each declaration with the debugger, instead of jumping through all of them at once.\r\n\r\n    ```javascript\r\n    // bad\r\n    const items = getItems(),\r\n        goSportsTeam = true,\r\n        dragonball = 'z';\r\n\r\n    // bad\r\n    // (compare to above, and try to spot the mistake)\r\n    const items = getItems(),\r\n        goSportsTeam = true;\r\n        dragonball = 'z';\r\n\r\n    // good\r\n    const items = getItems();\r\n    const goSportsTeam = true;\r\n    const dragonball = 'z';\r\n    ```\r\n\r\n  <a name=\"variables--const-let-group\"></a><a name=\"13.3\"></a>\r\n  - [13.3](#variables--const-let-group) Group all your `const`s and then group all your `let`s.\r\n\r\n    > Why? This is helpful when later on you might need to assign a variable depending on one of the previous assigned variables.\r\n\r\n    ```javascript\r\n    // bad\r\n    let i, len, dragonball,\r\n        items = getItems(),\r\n        goSportsTeam = true;\r\n\r\n    // bad\r\n    let i;\r\n    const items = getItems();\r\n    let dragonball;\r\n    const goSportsTeam = true;\r\n    let len;\r\n\r\n    // good\r\n    const goSportsTeam = true;\r\n    const items = getItems();\r\n    let dragonball;\r\n    let i;\r\n    let length;\r\n    ```\r\n\r\n  <a name=\"variables--define-where-used\"></a><a name=\"13.4\"></a>\r\n  - [13.4](#variables--define-where-used) Assign variables where you need them, but place them in a reasonable place.\r\n\r\n    > Why? `let` and `const` are block scoped and not function scoped.\r\n\r\n    ```javascript\r\n    // bad - unnecessary function call\r\n    function checkName(hasName) {\r\n      const name = getName();\r\n\r\n      if (hasName === 'test') {\r\n        return false;\r\n      }\r\n\r\n      if (name === 'test') {\r\n        this.setName('');\r\n        return false;\r\n      }\r\n\r\n      return name;\r\n    }\r\n\r\n    // good\r\n    function checkName(hasName) {\r\n      if (hasName === 'test') {\r\n        return false;\r\n      }\r\n\r\n      const name = getName();\r\n\r\n      if (name === 'test') {\r\n        this.setName('');\r\n        return false;\r\n      }\r\n\r\n      return name;\r\n    }\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Hoisting\r\n\r\n  <a name=\"hoisting--about\"></a><a name=\"14.1\"></a>\r\n  - [14.1](#hoisting--about) `var` declarations get hoisted to the top of their scope, their assignment does not. `const` and `let` declarations are blessed with a new concept called [Temporal Dead Zones (TDZ)](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let#Temporal_dead_zone_and_errors_with_let). It's important to know why [typeof is no longer safe](http://es-discourse.com/t/why-typeof-is-no-longer-safe/15).\r\n\r\n    ```javascript\r\n    // we know this wouldn't work (assuming there\r\n    // is no notDefined global variable)\r\n    function example() {\r\n      console.log(notDefined); // => throws a ReferenceError\r\n    }\r\n\r\n    // creating a variable declaration after you\r\n    // reference the variable will work due to\r\n    // variable hoisting. Note: the assignment\r\n    // value of `true` is not hoisted.\r\n    function example() {\r\n      console.log(declaredButNotAssigned); // => undefined\r\n      var declaredButNotAssigned = true;\r\n    }\r\n\r\n    // the interpreter is hoisting the variable\r\n    // declaration to the top of the scope,\r\n    // which means our example could be rewritten as:\r\n    function example() {\r\n      let declaredButNotAssigned;\r\n      console.log(declaredButNotAssigned); // => undefined\r\n      declaredButNotAssigned = true;\r\n    }\r\n\r\n    // using const and let\r\n    function example() {\r\n      console.log(declaredButNotAssigned); // => throws a ReferenceError\r\n      console.log(typeof declaredButNotAssigned); // => throws a ReferenceError\r\n      const declaredButNotAssigned = true;\r\n    }\r\n    ```\r\n\r\n  <a name=\"hoisting--anon-expressions\"></a><a name=\"14.2\"></a>\r\n  - [14.2](#hoisting--anon-expressions) Anonymous function expressions hoist their variable name, but not the function assignment.\r\n\r\n    ```javascript\r\n    function example() {\r\n      console.log(anonymous); // => undefined\r\n\r\n      anonymous(); // => TypeError anonymous is not a function\r\n\r\n      var anonymous = function () {\r\n        console.log('anonymous function expression');\r\n      };\r\n    }\r\n    ```\r\n\r\n  <a name=\"hoisting--named-expresions\"></a><a name=\"14.3\"></a>\r\n  - [14.3](#hoisting--named-expresions) Named function expressions hoist the variable name, not the function name or the function body.\r\n\r\n    ```javascript\r\n    function example() {\r\n      console.log(named); // => undefined\r\n\r\n      named(); // => TypeError named is not a function\r\n\r\n      superPower(); // => ReferenceError superPower is not defined\r\n\r\n      var named = function superPower() {\r\n        console.log('Flying');\r\n      };\r\n    }\r\n\r\n    // the same is true when the function name\r\n    // is the same as the variable name.\r\n    function example() {\r\n      console.log(named); // => undefined\r\n\r\n      named(); // => TypeError named is not a function\r\n\r\n      var named = function named() {\r\n        console.log('named');\r\n      }\r\n    }\r\n    ```\r\n\r\n  <a name=\"hoisting--declarations\"></a><a name=\"14.4\"></a>\r\n  - [14.4](#hoisting--declarations) Function declarations hoist their name and the function body.\r\n\r\n    ```javascript\r\n    function example() {\r\n      superPower(); // => Flying\r\n\r\n      function superPower() {\r\n        console.log('Flying');\r\n      }\r\n    }\r\n    ```\r\n\r\n  - For more information refer to [JavaScript Scoping & Hoisting](http://www.adequatelygood.com/2010/2/JavaScript-Scoping-and-Hoisting/) by [Ben Cherry](http://www.adequatelygood.com/).\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Comparison Operators & Equality\r\n\r\n  <a name=\"comparison--eqeqeq\"></a><a name=\"15.1\"></a>\r\n  - [15.1](#comparison--eqeqeq) Use `===` and `!==` over `==` and `!=`. eslint: [`eqeqeq`](http://eslint.org/docs/rules/eqeqeq.html)\r\n\r\n  <a name=\"comparison--if\"></a><a name=\"15.2\"></a>\r\n  - [15.2](#comparison--if) Conditional statements such as the `if` statement evaluate their expression using coercion with the `ToBoolean` abstract method and always follow these simple rules:\r\n\r\n    + **Objects** evaluate to **true**\r\n    + **Undefined** evaluates to **false**\r\n    + **Null** evaluates to **false**\r\n    + **Booleans** evaluate to **the value of the boolean**\r\n    + **Numbers** evaluate to **false** if **+0, -0, or NaN**, otherwise **true**\r\n    + **Strings** evaluate to **false** if an empty string `''`, otherwise **true**\r\n\r\n    ```javascript\r\n    if ([0] && []) {\r\n      // true\r\n      // an array (even an empty one) is an object, objects will evaluate to true\r\n    }\r\n    ```\r\n\r\n  <a name=\"comparison--shortcuts\"></a><a name=\"15.3\"></a>\r\n  - [15.3](#comparison--shortcuts) Use shortcuts.\r\n\r\n    ```javascript\r\n    // bad\r\n    if (name !== '') {\r\n      // ...stuff...\r\n    }\r\n\r\n    // good\r\n    if (name) {\r\n      // ...stuff...\r\n    }\r\n\r\n    // bad\r\n    if (collection.length > 0) {\r\n      // ...stuff...\r\n    }\r\n\r\n    // good\r\n    if (collection.length) {\r\n      // ...stuff...\r\n    }\r\n    ```\r\n\r\n  <a name=\"comparison--moreinfo\"></a><a name=\"15.4\"></a>\r\n  - [15.4](#comparison--moreinfo) For more information see [Truth Equality and JavaScript](http://javascriptweblog.wordpress.com/2011/02/07/truth-equality-and-javascript/#more-2108) by Angus Croll.\r\n\r\n  <a name=\"comparison--switch-blocks\"></a><a name=\"15.5\"></a>\r\n  - [15.5](#comparison--switch-blocks) Use braces to create blocks in `case` and `default` clauses that contain lexical declarations (e.g. `let`, `const`, `function`, and `class`).\r\n\r\n  > Why? Lexical declarations are visible in the entire `switch` block but only get initialized when assigned, which only happens when its `case` is reached. This causes problems when multiple `case` clauses attempt to define the same thing.\r\n\r\n  eslint rules: [`no-case-declarations`](http://eslint.org/docs/rules/no-case-declarations.html).\r\n\r\n    ```javascript\r\n    // bad\r\n    switch (foo) {\r\n      case 1:\r\n        let x = 1;\r\n        break;\r\n      case 2:\r\n        const y = 2;\r\n        break;\r\n      case 3:\r\n        function f() {}\r\n        break;\r\n      default:\r\n        class C {}\r\n    }\r\n\r\n    // good\r\n    switch (foo) {\r\n      case 1: {\r\n        let x = 1;\r\n        break;\r\n      }\r\n      case 2: {\r\n        const y = 2;\r\n        break;\r\n      }\r\n      case 3: {\r\n        function f() {}\r\n        break;\r\n      }\r\n      case 4:\r\n        bar();\r\n        break;\r\n      default: {\r\n        class C {}\r\n      }\r\n    }\r\n    ```\r\n\r\n  <a name=\"comparison--nested-ternaries\"></a><a name=\"15.6\"></a>\r\n  - [15.6](#comparison--nested-ternaries) Ternaries should not be nested and generally be single line expressions.\r\n\r\n    eslint rules: [`no-nested-ternary`](http://eslint.org/docs/rules/no-nested-ternary.html).\r\n\r\n    ```javascript\r\n    // bad\r\n    const foo = maybe1 > maybe2\r\n      ? \"bar\"\r\n      : value1 > value2 ? \"baz\" : null;\r\n\r\n    // better\r\n    const maybeNull = value1 > value2 ? 'baz' : null;\r\n\r\n    const foo = maybe1 > maybe2\r\n      ? 'bar'\r\n      : maybeNull;\r\n\r\n    // best\r\n    const maybeNull = value1 > value2 ? 'baz' : null;\r\n\r\n    const foo = maybe1 > maybe2 ? 'bar' : maybeNull;\r\n    ```\r\n\r\n  <a name=\"comparison--unneeded-ternary\"></a><a name=\"15.7\"></a>\r\n  - [15.7](#comparison--unneeded-ternary) Avoid unneeded ternary statements.\r\n\r\n    eslint rules: [`no-unneeded-ternary`](http://eslint.org/docs/rules/no-unneeded-ternary.html).\r\n\r\n    ```javascript\r\n    // bad\r\n    const foo = a ? a : b;\r\n    const bar = c ? true : false;\r\n    const baz = c ? false : true;\r\n\r\n    // good\r\n    const foo = a || b;\r\n    const bar = !!c;\r\n    const baz = !c;\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Blocks\r\n\r\n  <a name=\"blocks--braces\"></a><a name=\"16.1\"></a>\r\n  - [16.1](#blocks--braces) Use braces with all multi-line blocks.\r\n\r\n    ```javascript\r\n    // bad\r\n    if (test)\r\n      return false;\r\n\r\n    // good\r\n    if (test) return false;\r\n\r\n    // good\r\n    if (test) {\r\n      return false;\r\n    }\r\n\r\n    // bad\r\n    function foo() { return false; }\r\n\r\n    // good\r\n    function bar() {\r\n      return false;\r\n    }\r\n    ```\r\n\r\n  <a name=\"blocks--cuddled-elses\"></a><a name=\"16.2\"></a>\r\n  - [16.2](#blocks--cuddled-elses) If you're using multi-line blocks with `if` and `else`, put `else` on the same line as your `if` block's closing brace. eslint: [`brace-style`](http://eslint.org/docs/rules/brace-style.html) jscs:  [`disallowNewlineBeforeBlockStatements`](http://jscs.info/rule/disallowNewlineBeforeBlockStatements)\r\n\r\n    ```javascript\r\n    // bad\r\n    if (test) {\r\n      thing1();\r\n      thing2();\r\n    }\r\n    else {\r\n      thing3();\r\n    }\r\n\r\n    // good\r\n    if (test) {\r\n      thing1();\r\n      thing2();\r\n    } else {\r\n      thing3();\r\n    }\r\n    ```\r\n\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Comments\r\n\r\n  <a name=\"comments--multiline\"></a><a name=\"17.1\"></a>\r\n  - [17.1](#comments--multiline) Use `/** ... */` for multi-line comments. Include a description, specify types and values for all parameters and return values.\r\n\r\n    ```javascript\r\n    // bad\r\n    // make() returns a new element\r\n    // based on the passed in tag name\r\n    //\r\n    // @param {String} tag\r\n    // @return {Element} element\r\n    function make(tag) {\r\n\r\n      // ...stuff...\r\n\r\n      return element;\r\n    }\r\n\r\n    // good\r\n    /**\r\n     * make() returns a new element\r\n     * based on the passed in tag name\r\n     *\r\n     * @param {String} tag\r\n     * @return {Element} element\r\n     */\r\n    function make(tag) {\r\n\r\n      // ...stuff...\r\n\r\n      return element;\r\n    }\r\n    ```\r\n\r\n  <a name=\"comments--singleline\"></a><a name=\"17.2\"></a>\r\n  - [17.2](#comments--singleline) Use `//` for single line comments. Place single line comments on a newline above the subject of the comment. Put an empty line before the comment unless it's on the first line of a block.\r\n\r\n    ```javascript\r\n    // bad\r\n    const active = true;  // is current tab\r\n\r\n    // good\r\n    // is current tab\r\n    const active = true;\r\n\r\n    // bad\r\n    function getType() {\r\n      console.log('fetching type...');\r\n      // set the default type to 'no type'\r\n      const type = this._type || 'no type';\r\n\r\n      return type;\r\n    }\r\n\r\n    // good\r\n    function getType() {\r\n      console.log('fetching type...');\r\n\r\n      // set the default type to 'no type'\r\n      const type = this._type || 'no type';\r\n\r\n      return type;\r\n    }\r\n\r\n    // also good\r\n    function getType() {\r\n      // set the default type to 'no type'\r\n      const type = this._type || 'no type';\r\n\r\n      return type;\r\n    }\r\n    ```\r\n\r\n  <a name=\"comments--actionitems\"></a><a name=\"17.3\"></a>\r\n  - [17.3](#comments--actionitems) Prefixing your comments with `FIXME` or `TODO` helps other developers quickly understand if you're pointing out a problem that needs to be revisited, or if you're suggesting a solution to the problem that needs to be implemented. These are different than regular comments because they are actionable. The actions are `FIXME: -- need to figure this out` or `TODO: -- need to implement`.\r\n\r\n  <a name=\"comments--fixme\"></a><a name=\"17.4\"></a>\r\n  - [17.4](#comments--fixme) Use `// FIXME:` to annotate problems.\r\n\r\n    ```javascript\r\n    class Calculator extends Abacus {\r\n      constructor() {\r\n        super();\r\n\r\n        // FIXME: shouldn't use a global here\r\n        total = 0;\r\n      }\r\n    }\r\n    ```\r\n\r\n  <a name=\"comments--todo\"></a><a name=\"17.5\"></a>\r\n  - [17.5](#comments--todo) Use `// TODO:` to annotate solutions to problems.\r\n\r\n    ```javascript\r\n    class Calculator extends Abacus {\r\n      constructor() {\r\n        super();\r\n\r\n        // TODO: total should be configurable by an options param\r\n        this.total = 0;\r\n      }\r\n    }\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Whitespace\r\n\r\n  <a name=\"whitespace--spaces\"></a><a name=\"18.1\"></a>\r\n  - [18.1](#whitespace--spaces) Use soft tabs set to 2 spaces. eslint: [`indent`](http://eslint.org/docs/rules/indent.html) jscs: [`validateIndentation`](http://jscs.info/rule/validateIndentation)\r\n\r\n    ```javascript\r\n    // bad\r\n    function foo() {\r\n    ∙∙∙∙const name;\r\n    }\r\n\r\n    // bad\r\n    function bar() {\r\n    ∙const name;\r\n    }\r\n\r\n    // good\r\n    function baz() {\r\n    ∙∙const name;\r\n    }\r\n    ```\r\n\r\n  <a name=\"whitespace--before-blocks\"></a><a name=\"18.2\"></a>\r\n  - [18.2](#whitespace--before-blocks) Place 1 space before the leading brace. eslint: [`space-before-blocks`](http://eslint.org/docs/rules/space-before-blocks.html) jscs: [`requireSpaceBeforeBlockStatements`](http://jscs.info/rule/requireSpaceBeforeBlockStatements)\r\n\r\n    ```javascript\r\n    // bad\r\n    function test(){\r\n      console.log('test');\r\n    }\r\n\r\n    // good\r\n    function test() {\r\n      console.log('test');\r\n    }\r\n\r\n    // bad\r\n    dog.set('attr',{\r\n      age: '1 year',\r\n      breed: 'Bernese Mountain Dog',\r\n    });\r\n\r\n    // good\r\n    dog.set('attr', {\r\n      age: '1 year',\r\n      breed: 'Bernese Mountain Dog',\r\n    });\r\n    ```\r\n\r\n  <a name=\"whitespace--around-keywords\"></a><a name=\"18.3\"></a>\r\n  - [18.3](#whitespace--around-keywords) Place 1 space before the opening parenthesis in control statements (`if`, `while` etc.). Place no space between the argument list and the function name in function calls and declarations. eslint: [`keyword-spacing`](http://eslint.org/docs/rules/keyword-spacing.html) jscs: [`requireSpaceAfterKeywords`](http://jscs.info/rule/requireSpaceAfterKeywords)\r\n\r\n    ```javascript\r\n    // bad\r\n    if(isJedi) {\r\n      fight ();\r\n    }\r\n\r\n    // good\r\n    if (isJedi) {\r\n      fight();\r\n    }\r\n\r\n    // bad\r\n    function fight () {\r\n      console.log ('Swooosh!');\r\n    }\r\n\r\n    // good\r\n    function fight() {\r\n      console.log('Swooosh!');\r\n    }\r\n    ```\r\n\r\n  <a name=\"whitespace--infix-ops\"></a><a name=\"18.4\"></a>\r\n  - [18.4](#whitespace--infix-ops) Set off operators with spaces. eslint: [`space-infix-ops`](http://eslint.org/docs/rules/space-infix-ops.html) jscs: [`requireSpaceBeforeBinaryOperators`](http://jscs.info/rule/requireSpaceBeforeBinaryOperators), [`requireSpaceAfterBinaryOperators`](http://jscs.info/rule/requireSpaceAfterBinaryOperators)\r\n\r\n    ```javascript\r\n    // bad\r\n    const x=y+5;\r\n\r\n    // good\r\n    const x = y + 5;\r\n    ```\r\n\r\n  <a name=\"whitespace--newline-at-end\"></a><a name=\"18.5\"></a>\r\n  - [18.5](#whitespace--newline-at-end) End files with a single newline character.\r\n\r\n    ```javascript\r\n    // bad\r\n    (function (global) {\r\n      // ...stuff...\r\n    })(this);\r\n    ```\r\n\r\n    ```javascript\r\n    // bad\r\n    (function (global) {\r\n      // ...stuff...\r\n    })(this);↵\r\n    ↵\r\n    ```\r\n\r\n    ```javascript\r\n    // good\r\n    (function (global) {\r\n      // ...stuff...\r\n    })(this);↵\r\n    ```\r\n\r\n  <a name=\"whitespace--chains\"></a><a name=\"18.6\"></a>\r\n  - [18.6](#whitespace--chains) Use indentation when making long method chains (more than 2 method chains). Use a leading dot, which\r\n    emphasizes that the line is a method call, not a new statement. eslint: [`newline-per-chained-call`](http://eslint.org/docs/rules/newline-per-chained-call) [`no-whitespace-before-property`](http://eslint.org/docs/rules/no-whitespace-before-property)\r\n\r\n    ```javascript\r\n    // bad\r\n    $('#items').find('.selected').highlight().end().find('.open').updateCount();\r\n\r\n    // bad\r\n    $('#items').\r\n      find('.selected').\r\n        highlight().\r\n        end().\r\n      find('.open').\r\n        updateCount();\r\n\r\n    // good\r\n    $('#items')\r\n      .find('.selected')\r\n        .highlight()\r\n        .end()\r\n      .find('.open')\r\n        .updateCount();\r\n\r\n    // bad\r\n    const leds = stage.selectAll('.led').data(data).enter().append('svg:svg').classed('led', true)\r\n        .attr('width', (radius + margin) * 2).append('svg:g')\r\n        .attr('transform', 'translate(' + (radius + margin) + ',' + (radius + margin) + ')')\r\n        .call(tron.led);\r\n\r\n    // good\r\n    const leds = stage.selectAll('.led')\r\n        .data(data)\r\n      .enter().append('svg:svg')\r\n        .classed('led', true)\r\n        .attr('width', (radius + margin) * 2)\r\n      .append('svg:g')\r\n        .attr('transform', 'translate(' + (radius + margin) + ',' + (radius + margin) + ')')\r\n        .call(tron.led);\r\n\r\n    // good\r\n    const leds = stage.selectAll('.led').data(data);\r\n    ```\r\n\r\n  <a name=\"whitespace--after-blocks\"></a><a name=\"18.7\"></a>\r\n  - [18.7](#whitespace--after-blocks) Leave a blank line after blocks and before the next statement. jscs: [`requirePaddingNewLinesAfterBlocks`](http://jscs.info/rule/requirePaddingNewLinesAfterBlocks)\r\n\r\n    ```javascript\r\n    // bad\r\n    if (foo) {\r\n      return bar;\r\n    }\r\n    return baz;\r\n\r\n    // good\r\n    if (foo) {\r\n      return bar;\r\n    }\r\n\r\n    return baz;\r\n\r\n    // bad\r\n    const obj = {\r\n      foo() {\r\n      },\r\n      bar() {\r\n      },\r\n    };\r\n    return obj;\r\n\r\n    // good\r\n    const obj = {\r\n      foo() {\r\n      },\r\n\r\n      bar() {\r\n      },\r\n    };\r\n\r\n    return obj;\r\n\r\n    // bad\r\n    const arr = [\r\n      function foo() {\r\n      },\r\n      function bar() {\r\n      },\r\n    ];\r\n    return arr;\r\n\r\n    // good\r\n    const arr = [\r\n      function foo() {\r\n      },\r\n\r\n      function bar() {\r\n      },\r\n    ];\r\n\r\n    return arr;\r\n    ```\r\n\r\n  <a name=\"whitespace--padded-blocks\"></a><a name=\"18.8\"></a>\r\n  - [18.8](#whitespace--padded-blocks) Do not pad your blocks with blank lines. eslint: [`padded-blocks`](http://eslint.org/docs/rules/padded-blocks.html) jscs:  [`disallowPaddingNewlinesInBlocks`](http://jscs.info/rule/disallowPaddingNewlinesInBlocks)\r\n\r\n    ```javascript\r\n    // bad\r\n    function bar() {\r\n\r\n      console.log(foo);\r\n\r\n    }\r\n\r\n    // also bad\r\n    if (baz) {\r\n\r\n      console.log(qux);\r\n    } else {\r\n      console.log(foo);\r\n\r\n    }\r\n\r\n    // good\r\n    function bar() {\r\n      console.log(foo);\r\n    }\r\n\r\n    // good\r\n    if (baz) {\r\n      console.log(qux);\r\n    } else {\r\n      console.log(foo);\r\n    }\r\n    ```\r\n\r\n  <a name=\"whitespace--in-parens\"></a><a name=\"18.9\"></a>\r\n  - [18.9](#whitespace--in-parens) Do not add spaces inside parentheses. eslint: [`space-in-parens`](http://eslint.org/docs/rules/space-in-parens.html) jscs: [`disallowSpacesInsideParentheses`](http://jscs.info/rule/disallowSpacesInsideParentheses)\r\n\r\n    ```javascript\r\n    // bad\r\n    function bar( foo ) {\r\n      return foo;\r\n    }\r\n\r\n    // good\r\n    function bar(foo) {\r\n      return foo;\r\n    }\r\n\r\n    // bad\r\n    if ( foo ) {\r\n      console.log(foo);\r\n    }\r\n\r\n    // good\r\n    if (foo) {\r\n      console.log(foo);\r\n    }\r\n    ```\r\n\r\n  <a name=\"whitespace--in-brackets\"></a><a name=\"18.10\"></a>\r\n  - [18.10](#whitespace--in-brackets) Do not add spaces inside brackets. eslint: [`array-bracket-spacing`](http://eslint.org/docs/rules/array-bracket-spacing.html) jscs: [`disallowSpacesInsideArrayBrackets`](http://jscs.info/rule/disallowSpacesInsideArrayBrackets)\r\n\r\n    ```javascript\r\n    // bad\r\n    const foo = [ 1, 2, 3 ];\r\n    console.log(foo[ 0 ]);\r\n\r\n    // good\r\n    const foo = [1, 2, 3];\r\n    console.log(foo[0]);\r\n    ```\r\n\r\n  <a name=\"whitespace--in-braces\"></a><a name=\"18.11\"></a>\r\n  - [18.11](#whitespace--in-braces) Add spaces inside curly braces. eslint: [`object-curly-spacing`](http://eslint.org/docs/rules/object-curly-spacing.html) jscs: [`requireSpacesInsideObjectBrackets`](http://jscs.info/rule/requireSpacesInsideObjectBrackets)\r\n\r\n    ```javascript\r\n    // bad\r\n    const foo = {clark: 'kent'};\r\n\r\n    // good\r\n    const foo = { clark: 'kent' };\r\n    ```\r\n\r\n  <a name=\"whitespace--max-len\"></a><a name=\"18.12\"></a>\r\n  - [18.12](#whitespace--max-len) Avoid having lines of code that are longer than 100 characters (including whitespace). eslint: [`max-len`](http://eslint.org/docs/rules/max-len.html) jscs: [`maximumLineLength`](http://jscs.info/rule/maximumLineLength)\r\n\r\n    > Why? This ensures readability and maintainability.\r\n\r\n    ```javascript\r\n    // bad\r\n    const foo = 'Whatever national crop flips the window. The cartoon reverts within the screw. Whatever wizard constrains a helpful ally. The counterpart ascends!';\r\n\r\n    // bad\r\n    $.ajax({ method: 'POST', url: 'https://airbnb.com/', data: { name: 'John' } }).done(() => console.log('Congratulations!')).fail(() => console.log('You have failed this city.'));\r\n\r\n    // good\r\n    const foo = 'Whatever national crop flips the window. The cartoon reverts within the screw. ' +\r\n      'Whatever wizard constrains a helpful ally. The counterpart ascends!';\r\n\r\n    // good\r\n    $.ajax({\r\n      method: 'POST',\r\n      url: 'https://airbnb.com/',\r\n      data: { name: 'John' },\r\n    })\r\n      .done(() => console.log('Congratulations!'))\r\n      .fail(() => console.log('You have failed this city.'));\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Commas\r\n\r\n<a name=\"commas--leading-trailing\"></a><a name=\"19.1\"></a>\r\n  - [19.1](#commas--leading-trailing) Leading commas: **Nope.** eslint: [`comma-style`](http://eslint.org/docs/rules/comma-style.html) jscs: [`requireCommaBeforeLineBreak`](http://jscs.info/rule/requireCommaBeforeLineBreak)\r\n\r\n    ```javascript\r\n    // bad\r\n    const story = [\r\n        once\r\n      , upon\r\n      , aTime\r\n    ];\r\n\r\n    // good\r\n    const story = [\r\n      once,\r\n      upon,\r\n      aTime,\r\n    ];\r\n\r\n    // bad\r\n    const hero = {\r\n        firstName: 'Ada'\r\n      , lastName: 'Lovelace'\r\n      , birthYear: 1815\r\n      , superPower: 'computers'\r\n    };\r\n\r\n    // good\r\n    const hero = {\r\n      firstName: 'Ada',\r\n      lastName: 'Lovelace',\r\n      birthYear: 1815,\r\n      superPower: 'computers',\r\n    };\r\n    ```\r\n\r\n  <a name=\"commas--dangling\"></a><a name=\"19.2\"></a>\r\n  - [19.2](#commas--dangling) Additional trailing comma: **Yup.** eslint: [`comma-dangle`](http://eslint.org/docs/rules/comma-dangle.html) jscs: [`requireTrailingComma`](http://jscs.info/rule/requireTrailingComma)\r\n\r\n    > Why? This leads to cleaner git diffs. Also, transpilers like Babel will remove the additional trailing comma in the transpiled code which means you don't have to worry about the [trailing comma problem](es5/README.md#commas) in legacy browsers.\r\n\r\n    ```javascript\r\n    // bad - git diff without trailing comma\r\n    const hero = {\r\n         firstName: 'Florence',\r\n    -    lastName: 'Nightingale'\r\n    +    lastName: 'Nightingale',\r\n    +    inventorOf: ['coxcomb graph', 'modern nursing']\r\n    };\r\n\r\n    // good - git diff with trailing comma\r\n    const hero = {\r\n         firstName: 'Florence',\r\n         lastName: 'Nightingale',\r\n    +    inventorOf: ['coxcomb chart', 'modern nursing'],\r\n    };\r\n\r\n    // bad\r\n    const hero = {\r\n      firstName: 'Dana',\r\n      lastName: 'Scully'\r\n    };\r\n\r\n    const heroes = [\r\n      'Batman',\r\n      'Superman'\r\n    ];\r\n\r\n    // good\r\n    const hero = {\r\n      firstName: 'Dana',\r\n      lastName: 'Scully',\r\n    };\r\n\r\n    const heroes = [\r\n      'Batman',\r\n      'Superman',\r\n    ];\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Semicolons\r\n\r\n  <a name=\"semicolons--required\"></a><a name=\"20.1\"></a>\r\n  - [20.1](#20.1) **Yup.** eslint: [`semi`](http://eslint.org/docs/rules/semi.html) jscs: [`requireSemicolons`](http://jscs.info/rule/requireSemicolons)\r\n\r\n    ```javascript\r\n    // bad\r\n    (function () {\r\n      const name = 'Skywalker'\r\n      return name\r\n    })()\r\n\r\n    // good\r\n    (function () {\r\n      const name = 'Skywalker';\r\n      return name;\r\n    }());\r\n\r\n    // good, but legacy (guards against the function becoming an argument when two files with IIFEs are concatenated)\r\n    ;(() => {\r\n      const name = 'Skywalker';\r\n      return name;\r\n    }());\r\n    ```\r\n\r\n    [Read more](http://stackoverflow.com/questions/7365172/semicolon-before-self-invoking-function/7365214%237365214).\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Type Casting & Coercion\r\n\r\n  <a name=\"coercion--explicit\"></a><a name=\"21.1\"></a>\r\n  - [21.1](#coercion--explicit) Perform type coercion at the beginning of the statement.\r\n\r\n  <a name=\"coercion--strings\"></a><a name=\"21.2\"></a>\r\n  - [21.2](#coercion--strings)  Strings:\r\n\r\n    ```javascript\r\n    // => this.reviewScore = 9;\r\n\r\n    // bad\r\n    const totalScore = this.reviewScore + ''; // invokes this.reviewScore.valueOf()\r\n\r\n    // bad\r\n    const totalScore = this.reviewScore.toString(); // isn't guaranteed to return a string\r\n\r\n    // good\r\n    const totalScore = String(this.reviewScore);\r\n    ```\r\n\r\n  <a name=\"coercion--numbers\"></a><a name=\"21.3\"></a>\r\n  - [21.3](#coercion--numbers) Numbers: Use `Number` for type casting and `parseInt` always with a radix for parsing strings. eslint: [`radix`](http://eslint.org/docs/rules/radix)\r\n\r\n    ```javascript\r\n    const inputValue = '4';\r\n\r\n    // bad\r\n    const val = new Number(inputValue);\r\n\r\n    // bad\r\n    const val = +inputValue;\r\n\r\n    // bad\r\n    const val = inputValue >> 0;\r\n\r\n    // bad\r\n    const val = parseInt(inputValue);\r\n\r\n    // good\r\n    const val = Number(inputValue);\r\n\r\n    // good\r\n    const val = parseInt(inputValue, 10);\r\n    ```\r\n\r\n  <a name=\"coercion--comment-deviations\"></a><a name=\"21.4\"></a>\r\n  - [21.4](#coercion--comment-deviations) If for whatever reason you are doing something wild and `parseInt` is your bottleneck and need to use Bitshift for [performance reasons](http://jsperf.com/coercion-vs-casting/3), leave a comment explaining why and what you're doing.\r\n\r\n    ```javascript\r\n    // good\r\n    /**\r\n     * parseInt was the reason my code was slow.\r\n     * Bitshifting the String to coerce it to a\r\n     * Number made it a lot faster.\r\n     */\r\n    const val = inputValue >> 0;\r\n    ```\r\n\r\n  <a name=\"coercion--bitwise\"></a><a name=\"21.5\"></a>\r\n  - [21.5](#coercion--bitwise) **Note:** Be careful when using bitshift operations. Numbers are represented as [64-bit values](http://es5.github.io/#x4.3.19), but bitshift operations always return a 32-bit integer ([source](http://es5.github.io/#x11.7)). Bitshift can lead to unexpected behavior for integer values larger than 32 bits. [Discussion](https://github.com/airbnb/javascript/issues/109). Largest signed 32-bit Int is 2,147,483,647:\r\n\r\n    ```javascript\r\n    2147483647 >> 0 //=> 2147483647\r\n    2147483648 >> 0 //=> -2147483648\r\n    2147483649 >> 0 //=> -2147483647\r\n    ```\r\n\r\n  <a name=\"coercion--booleans\"></a><a name=\"21.6\"></a>\r\n  - [21.6](#coercion--booleans) Booleans:\r\n\r\n    ```javascript\r\n    const age = 0;\r\n\r\n    // bad\r\n    const hasAge = new Boolean(age);\r\n\r\n    // good\r\n    const hasAge = Boolean(age);\r\n\r\n    // best\r\n    const hasAge = !!age;\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Naming Conventions\r\n\r\n  <a name=\"naming--descriptive\"></a><a name=\"22.1\"></a>\r\n  - [22.1](#naming--descriptive) Avoid single letter names. Be descriptive with your naming.\r\n\r\n    ```javascript\r\n    // bad\r\n    function q() {\r\n      // ...stuff...\r\n    }\r\n\r\n    // good\r\n    function query() {\r\n      // ..stuff..\r\n    }\r\n    ```\r\n\r\n  <a name=\"naming--camelCase\"></a><a name=\"22.2\"></a>\r\n  - [22.2](#naming--camelCase) Use camelCase when naming objects, functions, and instances. eslint: [`camelcase`](http://eslint.org/docs/rules/camelcase.html) jscs: [`requireCamelCaseOrUpperCaseIdentifiers`](http://jscs.info/rule/requireCamelCaseOrUpperCaseIdentifiers)\r\n\r\n    ```javascript\r\n    // bad\r\n    const OBJEcttsssss = {};\r\n    const this_is_my_object = {};\r\n    function c() {}\r\n\r\n    // good\r\n    const thisIsMyObject = {};\r\n    function thisIsMyFunction() {}\r\n    ```\r\n\r\n  <a name=\"naming--PascalCase\"></a><a name=\"22.3\"></a>\r\n  - [22.3](#naming--PascalCase) Use PascalCase only when naming constructors or classes. eslint: [`new-cap`](http://eslint.org/docs/rules/new-cap.html) jscs: [`requireCapitalizedConstructors`](http://jscs.info/rule/requireCapitalizedConstructors)\r\n\r\n    ```javascript\r\n    // bad\r\n    function user(options) {\r\n      this.name = options.name;\r\n    }\r\n\r\n    const bad = new user({\r\n      name: 'nope',\r\n    });\r\n\r\n    // good\r\n    class User {\r\n      constructor(options) {\r\n        this.name = options.name;\r\n      }\r\n    }\r\n\r\n    const good = new User({\r\n      name: 'yup',\r\n    });\r\n    ```\r\n\r\n  <a name=\"naming--leading-underscore\"></a><a name=\"22.4\"></a>\r\n  - [22.4](#naming--leading-underscore) Do not use trailing or leading underscores. eslint: [`no-underscore-dangle`](http://eslint.org/docs/rules/no-underscore-dangle.html) jscs: [`disallowDanglingUnderscores`](http://jscs.info/rule/disallowDanglingUnderscores)\r\n\r\n    > Why? JavaScript does not have the concept of privacy in terms of properties or methods. Although a leading underscore is a common convention to mean “private”, in fact, these properties are fully public, and as such, are part of your public API contract. This convention might lead developers to wrongly think that a change won't count as breaking, or that tests aren't needed. tl;dr: if you want something to be “private”, it must not be observably present.\r\n\r\n    ```javascript\r\n    // bad\r\n    this.__firstName__ = 'Panda';\r\n    this.firstName_ = 'Panda';\r\n    this._firstName = 'Panda';\r\n\r\n    // good\r\n    this.firstName = 'Panda';\r\n    ```\r\n\r\n  <a name=\"naming--self-this\"></a><a name=\"22.5\"></a>\r\n  - [22.5](#naming--self-this) Don't save references to `this`. Use arrow functions or Function#bind. jscs: [`disallowNodeTypes`](http://jscs.info/rule/disallowNodeTypes)\r\n\r\n    ```javascript\r\n    // bad\r\n    function foo() {\r\n      const self = this;\r\n      return function () {\r\n        console.log(self);\r\n      };\r\n    }\r\n\r\n    // bad\r\n    function foo() {\r\n      const that = this;\r\n      return function () {\r\n        console.log(that);\r\n      };\r\n    }\r\n\r\n    // good\r\n    function foo() {\r\n      return () => {\r\n        console.log(this);\r\n      };\r\n    }\r\n    ```\r\n\r\n  <a name=\"naming--filename-matches-export\"></a><a name=\"22.6\"></a>\r\n  - [22.6](#naming--filename-matches-export) A base filename should exactly match the name of its default export.\r\n\r\n    ```javascript\r\n    // file 1 contents\r\n    class CheckBox {\r\n      // ...\r\n    }\r\n    export default CheckBox;\r\n\r\n    // file 2 contents\r\n    export default function fortyTwo() { return 42; }\r\n\r\n    // file 3 contents\r\n    export default function insideDirectory() {}\r\n\r\n    // in some other file\r\n    // bad\r\n    import CheckBox from './checkBox'; // PascalCase import/export, camelCase filename\r\n    import FortyTwo from './FortyTwo'; // PascalCase import/filename, camelCase export\r\n    import InsideDirectory from './InsideDirectory'; // PascalCase import/filename, camelCase export\r\n\r\n    // bad\r\n    import CheckBox from './check_box'; // PascalCase import/export, snake_case filename\r\n    import forty_two from './forty_two'; // snake_case import/filename, camelCase export\r\n    import inside_directory from './inside_directory'; // snake_case import, camelCase export\r\n    import index from './inside_directory/index'; // requiring the index file explicitly\r\n    import insideDirectory from './insideDirectory/index'; // requiring the index file explicitly\r\n\r\n    // good\r\n    import CheckBox from './CheckBox'; // PascalCase export/import/filename\r\n    import fortyTwo from './fortyTwo'; // camelCase export/import/filename\r\n    import insideDirectory from './insideDirectory'; // camelCase export/import/directory name/implicit \"index\"\r\n    // ^ supports both insideDirectory.js and insideDirectory/index.js\r\n    ```\r\n\r\n  <a name=\"naming--camelCase-default-export\"></a><a name=\"22.7\"></a>\r\n  - [22.7](#naming--camelCase-default-export) Use camelCase when you export-default a function. Your filename should be identical to your function's name.\r\n\r\n    ```javascript\r\n    function makeStyleGuide() {\r\n    }\r\n\r\n    export default makeStyleGuide;\r\n    ```\r\n\r\n  <a name=\"naming--PascalCase-singleton\"></a><a name=\"22.8\"></a>\r\n  - [22.8](#naming--PascalCase-singleton) Use PascalCase when you export a constructor / class / singleton / function library / bare object.\r\n\r\n    ```javascript\r\n    const AirbnbStyleGuide = {\r\n      es6: {\r\n      }\r\n    };\r\n\r\n    export default AirbnbStyleGuide;\r\n    ```\r\n\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Accessors\r\n\r\n  <a name=\"accessors--not-required\"></a><a name=\"23.1\"></a>\r\n  - [23.1](#accessors--not-required) Accessor functions for properties are not required.\r\n\r\n  <a name=\"accessors--no-getters-setters\"></a><a name=\"23.2\"></a>\r\n  - [23.2](#accessors--no-getters-setters) Do not use JavaScript getters/setters as they cause unexpected side effects and are harder to test, maintain, and reason about. Instead, if you do make accessor functions, use getVal() and setVal('hello').\r\n\r\n    ```javascript\r\n    // bad\r\n    class Dragon {\r\n      get age() {\r\n        // ...\r\n      }\r\n\r\n      set age(value) {\r\n        // ...\r\n      }\r\n    }\r\n\r\n    // good\r\n    class Dragon {\r\n      getAge() {\r\n        // ...\r\n      }\r\n\r\n      setAge(value) {\r\n        // ...\r\n      }\r\n    }\r\n    ```\r\n\r\n  <a name=\"accessors--boolean-prefix\"></a><a name=\"23.3\"></a>\r\n  - [23.3](#accessors--boolean-prefix) If the property/method is a `boolean`, use `isVal()` or `hasVal()`.\r\n\r\n    ```javascript\r\n    // bad\r\n    if (!dragon.age()) {\r\n      return false;\r\n    }\r\n\r\n    // good\r\n    if (!dragon.hasAge()) {\r\n      return false;\r\n    }\r\n    ```\r\n\r\n  <a name=\"accessors--consistent\"></a><a name=\"23.4\"></a>\r\n  - [23.4](#accessors--consistent) It's okay to create get() and set() functions, but be consistent.\r\n\r\n    ```javascript\r\n    class Jedi {\r\n      constructor(options = {}) {\r\n        const lightsaber = options.lightsaber || 'blue';\r\n        this.set('lightsaber', lightsaber);\r\n      }\r\n\r\n      set(key, val) {\r\n        this[key] = val;\r\n      }\r\n\r\n      get(key) {\r\n        return this[key];\r\n      }\r\n    }\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Events\r\n\r\n  <a name=\"events--hash\"></a><a name=\"24.1\"></a>\r\n  - [24.1](#events--hash) When attaching data payloads to events (whether DOM events or something more proprietary like Backbone events), pass a hash instead of a raw value. This allows a subsequent contributor to add more data to the event payload without finding and updating every handler for the event. For example, instead of:\r\n\r\n    ```javascript\r\n    // bad\r\n    $(this).trigger('listingUpdated', listing.id);\r\n\r\n    ...\r\n\r\n    $(this).on('listingUpdated', (e, listingId) => {\r\n      // do something with listingId\r\n    });\r\n    ```\r\n\r\n    prefer:\r\n\r\n    ```javascript\r\n    // good\r\n    $(this).trigger('listingUpdated', { listingId: listing.id });\r\n\r\n    ...\r\n\r\n    $(this).on('listingUpdated', (e, data) => {\r\n      // do something with data.listingId\r\n    });\r\n    ```\r\n\r\n  **[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## jQuery\r\n\r\n  <a name=\"jquery--dollar-prefix\"></a><a name=\"25.1\"></a>\r\n  - [25.1](#jquery--dollar-prefix) Prefix jQuery object variables with a `$`. jscs: [`requireDollarBeforejQueryAssignment`](http://jscs.info/rule/requireDollarBeforejQueryAssignment)\r\n\r\n    ```javascript\r\n    // bad\r\n    const sidebar = $('.sidebar');\r\n\r\n    // good\r\n    const $sidebar = $('.sidebar');\r\n\r\n    // good\r\n    const $sidebarBtn = $('.sidebar-btn');\r\n    ```\r\n\r\n  <a name=\"jquery--cache\"></a><a name=\"25.2\"></a>\r\n  - [25.2](#jquery--cache) Cache jQuery lookups.\r\n\r\n    ```javascript\r\n    // bad\r\n    function setSidebar() {\r\n      $('.sidebar').hide();\r\n\r\n      // ...stuff...\r\n\r\n      $('.sidebar').css({\r\n        'background-color': 'pink'\r\n      });\r\n    }\r\n\r\n    // good\r\n    function setSidebar() {\r\n      const $sidebar = $('.sidebar');\r\n      $sidebar.hide();\r\n\r\n      // ...stuff...\r\n\r\n      $sidebar.css({\r\n        'background-color': 'pink'\r\n      });\r\n    }\r\n    ```\r\n\r\n  <a name=\"jquery--queries\"></a><a name=\"25.3\"></a>\r\n  - [25.3](#jquery--queries) For DOM queries use Cascading `$('.sidebar ul')` or parent > child `$('.sidebar > ul')`. [jsPerf](http://jsperf.com/jquery-find-vs-context-sel/16)\r\n\r\n  <a name=\"jquery--find\"></a><a name=\"25.4\"></a>\r\n  - [25.4](#jquery--find) Use `find` with scoped jQuery object queries.\r\n\r\n    ```javascript\r\n    // bad\r\n    $('ul', '.sidebar').hide();\r\n\r\n    // bad\r\n    $('.sidebar').find('ul').hide();\r\n\r\n    // good\r\n    $('.sidebar ul').hide();\r\n\r\n    // good\r\n    $('.sidebar > ul').hide();\r\n\r\n    // good\r\n    $sidebar.find('ul').hide();\r\n    ```\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## ECMAScript 5 Compatibility\r\n\r\n  <a name=\"es5-compat--kangax\"></a><a name=\"26.1\"></a>\r\n  - [26.1](#es5-compat--kangax) Refer to [Kangax](https://twitter.com/kangax/)'s ES5 [compatibility table](http://kangax.github.io/es5-compat-table/).\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## ECMAScript 6 Styles\r\n\r\n  <a name=\"es6-styles\"></a><a name=\"27.1\"></a>\r\n  - [27.1](#es6-styles) This is a collection of links to the various ES6 features.\r\n\r\n1. [Arrow Functions](#arrow-functions)\r\n1. [Classes](#constructors)\r\n1. [Object Shorthand](#es6-object-shorthand)\r\n1. [Object Concise](#es6-object-concise)\r\n1. [Object Computed Properties](#es6-computed-properties)\r\n1. [Template Strings](#es6-template-literals)\r\n1. [Destructuring](#destructuring)\r\n1. [Default Parameters](#es6-default-parameters)\r\n1. [Rest](#es6-rest)\r\n1. [Array Spreads](#es6-array-spreads)\r\n1. [Let and Const](#references)\r\n1. [Iterators and Generators](#iterators-and-generators)\r\n1. [Modules](#modules)\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Testing\r\n\r\n  <a name=\"testing--yup\"></a><a name=\"28.1\"></a>\r\n  - [28.1](#testing--yup) **Yup.**\r\n\r\n    ```javascript\r\n    function foo() {\r\n      return true;\r\n    }\r\n    ```\r\n\r\n  <a name=\"testing--for-real\"></a><a name=\"28.2\"></a>\r\n  - [28.2](#testing--for-real) **No, but seriously**:\r\n   - Whichever testing framework you use, you should be writing tests!\r\n   - Strive to write many small pure functions, and minimize where mutations occur.\r\n   - Be cautious about stubs and mocks - they can make your tests more brittle.\r\n   - We primarily use [`mocha`](https://www.npmjs.com/package/mocha) at Airbnb. [`tape`](https://www.npmjs.com/package/tape) is also used occasionally for small, separate modules.\r\n   - 100% test coverage is a good goal to strive for, even if it's not always practical to reach it.\r\n   - Whenever you fix a bug, _write a regression test_. A bug fixed without a regression test is almost certainly going to break again in the future.\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Performance\r\n\r\n  - [On Layout & Web Performance](http://www.kellegous.com/j/2013/01/26/layout-performance/)\r\n  - [String vs Array Concat](http://jsperf.com/string-vs-array-concat/2)\r\n  - [Try/Catch Cost In a Loop](http://jsperf.com/try-catch-in-loop-cost)\r\n  - [Bang Function](http://jsperf.com/bang-function)\r\n  - [jQuery Find vs Context, Selector](http://jsperf.com/jquery-find-vs-context-sel/13)\r\n  - [innerHTML vs textContent for script text](http://jsperf.com/innerhtml-vs-textcontent-for-script-text)\r\n  - [Long String Concatenation](http://jsperf.com/ya-string-concat)\r\n  - [Are Javascript functions like `map()`, `reduce()`, and `filter()` optimized for traversing arrays?](https://www.quora.com/JavaScript-programming-language-Are-Javascript-functions-like-map-reduce-and-filter-already-optimized-for-traversing-array/answer/Quildreen-Motta)\r\n  - Loading...\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n\r\n## Resources\r\n\r\n**Learning ES6**\r\n\r\n  - [Draft ECMA 2015 (ES6) Spec](https://people.mozilla.org/~jorendorff/es6-draft.html)\r\n  - [ExploringJS](http://exploringjs.com/)\r\n  - [ES6 Compatibility Table](https://kangax.github.io/compat-table/es6/)\r\n  - [Comprehensive Overview of ES6 Features](http://es6-features.org/)\r\n\r\n**Read This**\r\n\r\n  - [Standard ECMA-262](http://www.ecma-international.org/ecma-262/6.0/index.html)\r\n\r\n**Tools**\r\n\r\n  - Code Style Linters\r\n    + [ESlint](http://eslint.org/) - [Airbnb Style .eslintrc](https://github.com/airbnb/javascript/blob/master/linters/.eslintrc)\r\n    + [JSHint](http://jshint.com/) - [Airbnb Style .jshintrc](https://github.com/airbnb/javascript/blob/master/linters/.jshintrc)\r\n    + [JSCS](https://github.com/jscs-dev/node-jscs) - [Airbnb Style Preset](https://github.com/jscs-dev/node-jscs/blob/master/presets/airbnb.json)\r\n\r\n**Other Style Guides**\r\n\r\n  - [Google JavaScript Style Guide](https://google.github.io/styleguide/javascriptguide.xml)\r\n  - [jQuery Core Style Guidelines](http://contribute.jquery.org/style-guide/js/)\r\n  - [Principles of Writing Consistent, Idiomatic JavaScript](https://github.com/rwaldron/idiomatic.js)\r\n\r\n**Other Styles**\r\n\r\n  - [Naming this in nested functions](https://gist.github.com/cjohansen/4135065) - Christian Johansen\r\n  - [Conditional Callbacks](https://github.com/airbnb/javascript/issues/52) - Ross Allen\r\n  - [Popular JavaScript Coding Conventions on Github](http://sideeffect.kr/popularconvention/#javascript) - JeongHoon Byun\r\n  - [Multiple var statements in JavaScript, not superfluous](http://benalman.com/news/2012/05/multiple-var-statements-javascript/) - Ben Alman\r\n\r\n**Further Reading**\r\n\r\n  - [Understanding JavaScript Closures](http://javascriptweblog.wordpress.com/2010/10/25/understanding-javascript-closures/) - Angus Croll\r\n  - [Basic JavaScript for the impatient programmer](http://www.2ality.com/2013/06/basic-javascript.html) - Dr. Axel Rauschmayer\r\n  - [You Might Not Need jQuery](http://youmightnotneedjquery.com/) - Zack Bloom & Adam Schwartz\r\n  - [ES6 Features](https://github.com/lukehoban/es6features) - Luke Hoban\r\n  - [Frontend Guidelines](https://github.com/bendc/frontend-guidelines) - Benjamin De Cock\r\n\r\n**Books**\r\n\r\n  - [JavaScript: The Good Parts](http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742) - Douglas Crockford\r\n  - [JavaScript Patterns](http://www.amazon.com/JavaScript-Patterns-Stoyan-Stefanov/dp/0596806752) - Stoyan Stefanov\r\n  - [Pro JavaScript Design Patterns](http://www.amazon.com/JavaScript-Design-Patterns-Recipes-Problem-Solution/dp/159059908X)  - Ross Harmes and Dustin Diaz\r\n  - [High Performance Web Sites: Essential Knowledge for Front-End Engineers](http://www.amazon.com/High-Performance-Web-Sites-Essential/dp/0596529309) - Steve Souders\r\n  - [Maintainable JavaScript](http://www.amazon.com/Maintainable-JavaScript-Nicholas-C-Zakas/dp/1449327680) - Nicholas C. Zakas\r\n  - [JavaScript Web Applications](http://www.amazon.com/JavaScript-Web-Applications-Alex-MacCaw/dp/144930351X) - Alex MacCaw\r\n  - [Pro JavaScript Techniques](http://www.amazon.com/Pro-JavaScript-Techniques-John-Resig/dp/1590597273) - John Resig\r\n  - [Smashing Node.js: JavaScript Everywhere](http://www.amazon.com/Smashing-Node-js-JavaScript-Everywhere-Magazine/dp/1119962595) - Guillermo Rauch\r\n  - [Secrets of the JavaScript Ninja](http://www.amazon.com/Secrets-JavaScript-Ninja-John-Resig/dp/193398869X) - John Resig and Bear Bibeault\r\n  - [Human JavaScript](http://humanjavascript.com/) - Henrik Joreteg\r\n  - [Superhero.js](http://superherojs.com/) - Kim Joar Bekkelund, Mads Mobæk, & Olav Bjorkoy\r\n  - [JSBooks](http://jsbooks.revolunet.com/) - Julien Bouquillon\r\n  - [Third Party JavaScript](https://www.manning.com/books/third-party-javascript) - Ben Vinegar and Anton Kovalyov\r\n  - [Effective JavaScript: 68 Specific Ways to Harness the Power of JavaScript](http://amzn.com/0321812182) - David Herman\r\n  - [Eloquent JavaScript](http://eloquentjavascript.net/) - Marijn Haverbeke\r\n  - [You Don't Know JS: ES6 & Beyond](http://shop.oreilly.com/product/0636920033769.do) - Kyle Simpson\r\n\r\n**Blogs**\r\n\r\n  - [DailyJS](http://dailyjs.com/)\r\n  - [JavaScript Weekly](http://javascriptweekly.com/)\r\n  - [JavaScript, JavaScript...](http://javascriptweblog.wordpress.com/)\r\n  - [Bocoup Weblog](https://bocoup.com/weblog)\r\n  - [Adequately Good](http://www.adequatelygood.com/)\r\n  - [NCZOnline](https://www.nczonline.net/)\r\n  - [Perfection Kills](http://perfectionkills.com/)\r\n  - [Ben Alman](http://benalman.com/)\r\n  - [Dmitry Baranovskiy](http://dmitry.baranovskiy.com/)\r\n  - [Dustin Diaz](http://dustindiaz.com/)\r\n  - [nettuts](http://code.tutsplus.com/?s=javascript)\r\n\r\n**Podcasts**\r\n\r\n  - [JavaScript Jabber](https://devchat.tv/js-jabber/)\r\n\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## In the Wild\r\n\r\n  This is a list of organizations that are using this style guide. Send us a pull request and we'll add you to the list.\r\n\r\n  - **4Catalyzer**: [4Catalyzer/javascript](https://github.com/4Catalyzer/javascript)\r\n  - **Aan Zee**: [AanZee/javascript](https://github.com/AanZee/javascript)\r\n  - **Adult Swim**: [adult-swim/javascript](https://github.com/adult-swim/javascript)\r\n  - **Airbnb**: [airbnb/javascript](https://github.com/airbnb/javascript)\r\n  - **Apartmint**: [apartmint/javascript](https://github.com/apartmint/javascript)\r\n  - **Ascribe**: [ascribe/javascript](https://github.com/ascribe/javascript)\r\n  - **Avalara**: [avalara/javascript](https://github.com/avalara/javascript)\r\n  - **Avant**: [avantcredit/javascript](https://github.com/avantcredit/javascript)\r\n  - **Billabong**: [billabong/javascript](https://github.com/billabong/javascript)\r\n  - **Bisk**: [bisk/javascript](https://github.com/Bisk/javascript/)\r\n  - **Blendle**: [blendle/javascript](https://github.com/blendle/javascript)\r\n  - **Brainshark**: [brainshark/javascript](https://github.com/brainshark/javascript)\r\n  - **Chartboost**: [ChartBoost/javascript-style-guide](https://github.com/ChartBoost/javascript-style-guide)\r\n  - **ComparaOnline**: [comparaonline/javascript](https://github.com/comparaonline/javascript-style-guide)\r\n  - **Compass Learning**: [compasslearning/javascript-style-guide](https://github.com/compasslearning/javascript-style-guide)\r\n  - **DailyMotion**: [dailymotion/javascript](https://github.com/dailymotion/javascript)\r\n  - **DoSomething**: [DoSomething/eslint-config](https://github.com/DoSomething/eslint-config)\r\n  - **Digitpaint** [digitpaint/javascript](https://github.com/digitpaint/javascript)\r\n  - **Ecosia**: [ecosia/javascript](https://github.com/ecosia/javascript)\r\n  - **Evernote**: [evernote/javascript-style-guide](https://github.com/evernote/javascript-style-guide)\r\n  - **Evolution Gaming**: [evolution-gaming/javascript](https://github.com/evolution-gaming/javascript)\r\n  - **EvozonJs**: [evozonjs/javascript](https://github.com/evozonjs/javascript)\r\n  - **ExactTarget**: [ExactTarget/javascript](https://github.com/ExactTarget/javascript)\r\n  - **Expensify** [Expensify/Style-Guide](https://github.com/Expensify/Style-Guide/blob/master/javascript.md)\r\n  - **Flexberry**: [Flexberry/javascript-style-guide](https://github.com/Flexberry/javascript-style-guide)\r\n  - **Gawker Media**: [gawkermedia/javascript](https://github.com/gawkermedia/javascript)\r\n  - **General Electric**: [GeneralElectric/javascript](https://github.com/GeneralElectric/javascript)\r\n  - **GoodData**: [gooddata/gdc-js-style](https://github.com/gooddata/gdc-js-style)\r\n  - **Grooveshark**: [grooveshark/javascript](https://github.com/grooveshark/javascript)\r\n  - **How About We**: [howaboutwe/javascript](https://github.com/howaboutwe/javascript-style-guide)\r\n  - **Huballin**: [huballin/javascript](https://github.com/huballin/javascript)\r\n  - **HubSpot**: [HubSpot/javascript](https://github.com/HubSpot/javascript)\r\n  - **Hyper**: [hyperoslo/javascript-playbook](https://github.com/hyperoslo/javascript-playbook/blob/master/style.md)\r\n  - **InfoJobs**: [InfoJobs/JavaScript-Style-Guide](https://github.com/InfoJobs/JavaScript-Style-Guide)\r\n  - **Intent Media**: [intentmedia/javascript](https://github.com/intentmedia/javascript)\r\n  - **Jam3**: [Jam3/Javascript-Code-Conventions](https://github.com/Jam3/Javascript-Code-Conventions)\r\n  - **JeopardyBot**: [kesne/jeopardy-bot](https://github.com/kesne/jeopardy-bot/blob/master/STYLEGUIDE.md)\r\n  - **JSSolutions**: [JSSolutions/javascript](https://github.com/JSSolutions/javascript)\r\n  - **KickorStick**: [kickorstick/javascript](https://github.com/kickorstick/javascript)\r\n  - **Kinetica Solutions**: [kinetica/javascript](https://github.com/kinetica/Javascript-style-guide)\r\n  - **Mighty Spring**: [mightyspring/javascript](https://github.com/mightyspring/javascript)\r\n  - **MinnPost**: [MinnPost/javascript](https://github.com/MinnPost/javascript)\r\n  - **MitocGroup**: [MitocGroup/javascript](https://github.com/MitocGroup/javascript)\r\n  - **ModCloth**: [modcloth/javascript](https://github.com/modcloth/javascript)\r\n  - **Money Advice Service**: [moneyadviceservice/javascript](https://github.com/moneyadviceservice/javascript)\r\n  - **Muber**: [muber/javascript](https://github.com/muber/javascript)\r\n  - **National Geographic**: [natgeo/javascript](https://github.com/natgeo/javascript)\r\n  - **National Park Service**: [nationalparkservice/javascript](https://github.com/nationalparkservice/javascript)\r\n  - **Nimbl3**: [nimbl3/javascript](https://github.com/nimbl3/javascript)\r\n  - **Orion Health**: [orionhealth/javascript](https://github.com/orionhealth/javascript)\r\n  - **OutBoxSoft**: [OutBoxSoft/javascript](https://github.com/OutBoxSoft/javascript)\r\n  - **Peerby**: [Peerby/javascript](https://github.com/Peerby/javascript)\r\n  - **Razorfish**: [razorfish/javascript-style-guide](https://github.com/razorfish/javascript-style-guide)\r\n  - **reddit**: [reddit/styleguide/javascript](https://github.com/reddit/styleguide/tree/master/javascript)\r\n  - **React**: [/facebook/react/blob/master/CONTRIBUTING.md#style-guide](https://github.com/facebook/react/blob/master/CONTRIBUTING.md#style-guide)\r\n  - **REI**: [reidev/js-style-guide](https://github.com/rei/code-style-guides/blob/master/docs/javascript.md)\r\n  - **Ripple**: [ripple/javascript-style-guide](https://github.com/ripple/javascript-style-guide)\r\n  - **SeekingAlpha**: [seekingalpha/javascript-style-guide](https://github.com/seekingalpha/javascript-style-guide)\r\n  - **Shutterfly**: [shutterfly/javascript](https://github.com/shutterfly/javascript)\r\n  - **Springload**: [springload/javascript](https://github.com/springload/javascript)\r\n  - **StudentSphere**: [studentsphere/javascript](https://github.com/studentsphere/guide-javascript)\r\n  - **SysGarage**: [sysgarage/javascript-style-guide](https://github.com/sysgarage/javascript-style-guide)\r\n  - **Target**: [target/javascript](https://github.com/target/javascript)\r\n  - **TheLadders**: [TheLadders/javascript](https://github.com/TheLadders/javascript)\r\n  - **The Nerdery**: [thenerdery/javascript-standards](https://github.com/thenerdery/javascript-standards)\r\n  - **T4R Technology**: [T4R-Technology/javascript](https://github.com/T4R-Technology/javascript)\r\n  - **VoxFeed**: [VoxFeed/javascript-style-guide](https://github.com/VoxFeed/javascript-style-guide)\r\n  - **WeBox Studio**: [weboxstudio/javascript](https://github.com/weboxstudio/javascript)\r\n  - **Weggo**: [Weggo/javascript](https://github.com/Weggo/javascript)\r\n  - **Zillow**: [zillow/javascript](https://github.com/zillow/javascript)\r\n  - **ZocDoc**: [ZocDoc/javascript](https://github.com/ZocDoc/javascript)\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Translation\r\n\r\n  This style guide is also available in other languages:\r\n\r\n  - ![br](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Brazil.png) **Brazilian Portuguese**: [armoucar/javascript-style-guide](https://github.com/armoucar/javascript-style-guide)\r\n  - ![bg](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Bulgaria.png) **Bulgarian**: [borislavvv/javascript](https://github.com/borislavvv/javascript)\r\n  - ![ca](https://raw.githubusercontent.com/fpmweb/javascript-style-guide/master/img/catala.png) **Catalan**: [fpmweb/javascript-style-guide](https://github.com/fpmweb/javascript-style-guide)\r\n  - ![cn](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/China.png) **Chinese (Simplified)**: [sivan/javascript-style-guide](https://github.com/sivan/javascript-style-guide)\r\n  - ![tw](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Taiwan.png) **Chinese (Traditional)**: [jigsawye/javascript](https://github.com/jigsawye/javascript)\r\n  - ![fr](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/France.png) **French**: [nmussy/javascript-style-guide](https://github.com/nmussy/javascript-style-guide)\r\n  - ![de](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Germany.png) **German**: [timofurrer/javascript-style-guide](https://github.com/timofurrer/javascript-style-guide)\r\n  - ![it](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Italy.png) **Italian**: [sinkswim/javascript-style-guide](https://github.com/sinkswim/javascript-style-guide)\r\n  - ![jp](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Japan.png) **Japanese**: [mitsuruog/javacript-style-guide](https://github.com/mitsuruog/javacript-style-guide)\r\n  - ![kr](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/South-Korea.png) **Korean**: [tipjs/javascript-style-guide](https://github.com/tipjs/javascript-style-guide)\r\n  - ![pl](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Poland.png) **Polish**: [mjurczyk/javascript](https://github.com/mjurczyk/javascript)\r\n  - ![ru](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Russia.png) **Russian**: [uprock/javascript](https://github.com/uprock/javascript)\r\n  - ![es](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Spain.png) **Spanish**: [paolocarrasco/javascript-style-guide](https://github.com/paolocarrasco/javascript-style-guide)\r\n  - ![th](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Thailand.png) **Thai**: [lvarayut/javascript-style-guide](https://github.com/lvarayut/javascript-style-guide)\r\n  - ![vn](https://raw.githubusercontent.com/gosquared/flags/master/flags/flags/shiny/24/Vietnam.png) **Vietnam**: [giangpii/javascript-style-guide](https://github.com/giangpii/javascript-style-guide)\r\n\r\n## The JavaScript Style Guide Guide\r\n\r\n  - [Reference](https://github.com/airbnb/javascript/wiki/The-JavaScript-Style-Guide-Guide)\r\n\r\n## Chat With Us About JavaScript\r\n\r\n  - Find us on [gitter](https://gitter.im/airbnb/javascript).\r\n\r\n## Contributors\r\n\r\n  - [View Contributors](https://github.com/airbnb/javascript/graphs/contributors)\r\n\r\n\r\n## License\r\n\r\n(The MIT License)\r\n\r\nCopyright (c) 2014-2016 Airbnb\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining\r\na copy of this software and associated documentation files (the\r\n'Software'), to deal in the Software without restriction, including\r\nwithout limitation the rights to use, copy, modify, merge, publish,\r\ndistribute, sublicense, and/or sell copies of the Software, and to\r\npermit persons to whom the Software is furnished to do so, subject to\r\nthe following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be\r\nincluded in all copies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,\r\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF\r\nMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.\r\nIN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY\r\nCLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,\r\nTORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE\r\nSOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\r\n\r\n**[⬆ back to top](#table-of-contents)**\r\n\r\n## Amendments\r\n\r\nWe encourage you to fork this guide and change the rules to fit your team's style guide. Below, you may list some amendments to the style guide. This allows you to periodically update your style guide without having to deal with merge conflicts.\r\n\r\n# };\r\n",
-  "google": "",
-  "note": "Don't delete this file! It's used internally to help with page regeneration."
-}
\ No newline at end of file
