document sourceType option; add supported versions to recurseDepth option (#166)

Author: hegemonic

about-configuring-jsdoc.html

@@ -39,6 +39,9 @@ <h2>Table of Contents</h2>
       <li>
         <a href="#specifying-input-files">Specifying input files</a>
       </li>
+      <li>
+        <a href="#specifying-the-source-type">Specifying the source type</a>
+      </li>
       <li>
         <a href="#incorporating-command-line-options-into-the-configuration-file">Incorporating command-line options into the configuration file</a>
       </li>
@@ -87,6 +90,7 @@ <h2 id="default-configuration-options">Default configuration options</h2>
         "includePattern": ".+\\.js(doc|x)?$",
         "excludePattern": "(^|\\/|\\\\)_"
     },
+    "sourceType": "module",
     "tags": {
         "allowUnknownTags": true,
         "dictionaries": ["jsdoc","closure"]
@@ -104,6 +108,7 @@ <h2 id="default-configuration-options">Default configuration options</h2>
       <li>If recursion is enabled with the <a href="about-commandline.html"><code>-r</code> command-line flag</a>, JSDoc will search for files 10 levels deep (<code>recurseDepth</code>).</li>
       <li>Only files ending in <code>.js</code>, <code>.jsdoc</code>, and <code>.jsx</code> will be processed (<code>source.includePattern</code>).</li>
       <li>Any file starting with an underscore, or in a directory starting with an underscore, will be ignored (<code>source.excludePattern</code>).</li>
+      <li>JSDoc supports code that uses <a href="howto-es2015-modules.html">ES2015 modules</a> (<code>sourceType</code>).</li>
       <li>JSDoc allows you to use unrecognized tags (<code>tags.allowUnknownTags</code>).</li>
       <li>Both standard JSDoc tags and <a href="https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags">Closure Compiler tags</a>        are enabled (
         <code>tags.dictionaries</code>).</li>
@@ -130,9 +135,9 @@ <h2 id="configuring-plugins">Configuring plugins</h2>
     <p>You can configure the Markdown plugin by adding a <code>markdown</code> object to your configuration file. See
       <a href="plugins-markdown.html">Configuring the Markdown Plugin</a> for details.</p>
     <h2 id="specifying-recursion-depth">Specifying recursion depth</h2>
-    <p>The <code>recurseDepth</code> option controls how many levels deep JSDoc will recursively search for source files and tutorials. This option is used only if
-      you also specify the <a href="about-commandline.html"><code>-r</code> command-line
-flag</a>, which tells JSDoc to recursively search for input files.</p>
+    <p>The <code>recurseDepth</code> option controls how many levels deep JSDoc will recursively search for source files and tutorials. This option is available in
+      JSDoc 3.5.0 and later. This option is used only if you also specify the <a href="about-commandline.html"><code>-r</code> command-line flag</a>, which tells
+      JSDoc to recursively search for input files.</p>
     <figure><pre class="prettyprint lang-js"><code>{
     "recurseDepth": 10
 }
@@ -222,6 +227,19 @@ <h2 id="specifying-input-files">Specifying input files</h2>
       <li>JSDoc applies <code>source.excludePattern</code>, which removes <code>myProject/_private/a.js</code>.</li>
       <li>JSDoc applies <code>source.exclude</code>, which removes <code>myProject/lib/ignore.js</code>.</li>
     </ol>
+    <h2 id="specifying-the-source-type">Specifying the source type</h2>
+    <p>The <code>sourceType</code> option affects how JSDoc parses your JavaScript files. This option is available in JSDoc 3.5.0 and later. This option accepts the
+      following values:</p>
+    <ul>
+      <li><code>module</code> (default): Use this value for most types of JavaScript files.</li>
+      <li><code>script</code>: Use this value if JSDoc logs errors such as <code>Delete of an unqualified identifier in
+strict mode</code> when it parses your code.</li>
+    </ul>
+    <figure><pre class="prettyprint lang-js"><code>{
+    "sourceType": "module"
+}
+</code></pre>
+    </figure>
     <h2 id="incorporating-command-line-options-into-the-configuration-file">Incorporating command-line options into the configuration file</h2>
     <p>You can put many of JSDoc&#39;s <a href="about-commandline.html">command-line options</a> into the configuration file instead of specifying them on the command
       line. To do this, add the long names of the relevant options into an

content/en/about-configuring-jsdoc.md

@@ -65,6 +65,7 @@ If you do not specify a configuration file, JSDoc uses the following configurati
         "includePattern": ".+\\.js(doc|x)?$",
         "excludePattern": "(^|\\/|\\\\)_"
     },
+    "sourceType": "module",
     "tags": {
         "allowUnknownTags": true,
         "dictionaries": ["jsdoc","closure"]
@@ -85,6 +86,7 @@ for files 10 levels deep (`recurseDepth`).
 + Only files ending in `.js`, `.jsdoc`, and `.jsx` will be processed (`source.includePattern`).
 + Any file starting with an underscore, or in a directory starting with an underscore, will be
 ignored (`source.excludePattern`).
++ JSDoc supports code that uses [ES2015 modules][es2015-modules] (`sourceType`).
 + JSDoc allows you to use unrecognized tags (`tags.allowUnknownTags`).
 + Both standard JSDoc tags and [Closure Compiler tags][closure-tags] are enabled
 (`tags.dictionaries`).
@@ -95,6 +97,7 @@ These options and others are explained in the following sections.
 
 [about-commandline]: about-commandline.html
 [closure-tags]: https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#jsdoc-tags
+[es2015-modules]: howto-es2015-modules.html
 [tags-inline-link]: tags-inline-link.html
 
 
@@ -132,8 +135,9 @@ You can configure the Markdown plugin by adding a `markdown` object to your conf
 ## Specifying recursion depth
 
 The `recurseDepth` option controls how many levels deep JSDoc will recursively search for source
-files and tutorials. This option is used only if you also specify the [`-r` command-line
-flag][about-commandline], which tells JSDoc to recursively search for input files.
+files and tutorials. This option is available in JSDoc 3.5.0 and later. This option is used only if
+you also specify the [`-r` command-line flag][about-commandline], which tells JSDoc to recursively
+search for input files.
 
 {% example %}
 
@@ -249,6 +253,25 @@ files:
 [about-commandline]: about-commandline.html
 
 
+## Specifying the source type
+
+The `sourceType` option affects how JSDoc parses your JavaScript files. This option is available in
+JSDoc 3.5.0 and later. This option accepts the following values:
+
++ `module` (default): Use this value for most types of JavaScript files.
++ `script`: Use this value if JSDoc logs errors such as `Delete of an unqualified identifier in
+strict mode` when it parses your code.
+
+{% example %}
+
+```js
+{
+    "sourceType": "module"
+}
+```
+{% endexample %}
+
+
 ## Incorporating command-line options into the configuration file
 
 You can put many of JSDoc's [command-line options][options] into the configuration file instead of