Version: 1.50.1 (system setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.18363

Steps to Reproduce:

1. Create a sample Electron project.

   In the

• [X ] I have searched through existing issues

Feature Request

At the moment it seems that the vti diagnostics command only accepts directories as an argument?
E.g., running vti diagnostics src/components/ will check all .vue inside the src/components directory. Passing a single file as an argument results in an ENOTDIR exception. It would be helpful to pass single files or a list of sin

Most of the time when I'm using this extension I am using it to mark points of interest during research. A task that I've had to perform lately is looking for hard coded text in various applications that needs to be moved to our CMS. This extension works great for that with one exception:

Generally after I have performed my research I need to document it. Using this extension I need to go to ea

Setting peacock.color or peacock.remoteColor in the user settings.json can be done manually. If set, peacock will use that color as the default color to colorize VS Code.

This should be documented in the readme, along with considerations.

Considerations:

• this can only be set or unset manually.
• this will make every vs code instance that doesnt have a color in their workspace use t