Vscode plugin not starting on windows, had to add to path variable.

[MichaelMorozovCodit]

I got an error when setting up the vscode extension:

[Error - 3:03:59 PM] Starting client failed
Launching server using command vacuum.cmd failed.

So I figured it had to be because it's not added to PATH on Windows when installing through npm. Thought you should know. I ended up creating a symlink explicitly called vacuum.cmd in order for it to work, which it now does.

[LasneF]

it looks strange , are you sure you have install it globally ? with -g option
i mean if you open a shell it should run wherever you are , and so it is for the vscode
it might requires to restart a terminal ,

[MichaelMorozovCodit]

Yes, I ran the npm install -g @quobix/vacuum command like in the description.

[MichaelMorozovCodit]

Maybe related to this, the extension doesn't start automatically every time I open up VScode.

[daveshanley]

I will update the extension to autostart on boot with VSCode.