<p dir="auto">Hello,</p>
<p dir="auto">I just tried VS Code recently and I was surprised to see it didn't exclude the files and folders listed in my <code class="notranslate">.gitignore</code> file.</p>
<p dir="auto">I think an option allowing us to hide those files in the Explorer would be really nice.</p>
<p dir="auto">Here is how Atom does it:</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/89233/13565344/d476f9ea-e44f-11e5-896b-3a637ee36153.png"><img width="770" alt="screen shot 2016-03-07 at 10 31 42" src="https://cloud.githubusercontent.com/assets/89233/13565344/d476f9ea-e44f-11e5-896b-3a637ee36153.png" style="max-width: 100%;"></a></p>
<p dir="auto">And when this option isn't on, Atom colorizes the excluded files like that:</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/89233/13565471/8abf97a2-e450-11e5-94ad-771193dd25c0.png"><img width="167" alt="screen shot 2016-03-07 at 10 36 52" src="https://cloud.githubusercontent.com/assets/89233/13565471/8abf97a2-e450-11e5-94ad-771193dd25c0.png" style="max-width: 100%;"></a></p>
<p dir="auto">The whole process of cloning mock-debug to make a debugger extension and then changing it is cumbersome. Like for normal extensions, there should be a yeoman generator that asks you questions about what languages the debugger is for, what the name should be etc.</p>
<p dir="auto">Secondly, in the docs you express the intent to move the common part of the mock-debug repo to a NPM module, which makes sense, as it's the TS implementation of the debugger protocol so we can write extensions in TS using it. You would be able to add more features over time etc.</p>
<p dir="auto">I think this would make writing debugger extensions more straight forward.</p>