<ul dir="auto">
<li>VSCode Version:1.1.0-alpha</li>
<li>OS Version:Windows 10</li>
</ul>
<p dir="auto">Steps to Reproduce:</p>
<ol dir="auto">
<li>Run code-alpha --help</li>
</ol>
<p dir="auto">Shown as "list-extensions", should be "uninstall-extension"</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content=" --list-extensions     List the installed extensions.
  --install-extension &lt;extension&gt;
                        Installs an extension.
  --list-extensions &lt;extension&gt;
                        Uninstalls an extension."><pre class="notranslate"><code class="notranslate"> --list-extensions     List the installed extensions.
  --install-extension &lt;extension&gt;
                        Installs an extension.
  --list-extensions &lt;extension&gt;
                        Uninstalls an extension.
</code></pre></div>
<p dir="auto">See <a class="commit-link" href="https://github.com/microsoft/vscode/commit/b455db9f356a9e395aefa44d9b3f5597c67b7aa0#diff-e255a28340d4f20061d11494e99bd60b"><tt>b455db9</tt>#diff-e255a28340d4f20061d11494e99bd60b</a></p>
<p dir="auto">Using mainly the default generated files from <code class="notranslate">generator-code</code>, a significant number of devDependencies (mostly recursive) are pulled in - mainly because of Mocha. For development this is fine (I love Mocha). But why blindly package them all with <code class="notranslate">vsce package</code>? Perhaps create an output directory of everything <code class="notranslate">vsce ls</code> would find but <em>node_modules</em>, then run <code class="notranslate">npm install --production</code> and package that directory. Would certainly reduce the size of VSCode extensions. Mine - with only the addition of 1 small module (with no dependencies itself) is over 5MB.</p>