That was my thinking also but it was simpler to do it then to explain 
Cabbage: Path To Cabbage Binary
c:\Users\lovre\.vscode\extensions\cabbageaudio.vscabbage-1.0.34-alpha\src\CabbageBundle
Cabbage: Path To JS Source
C:\Users\lovre\.vscode\extensions\cabbageaudio.vscabbage-1.0.34-alpha
I also tried here with C:\Users\lovre\.vscode\extensions\cabbageaudio.vscabbage-1.0.34-alpha\src but no difference
I solved It!! It was a conflict with Csound6! I now removed Csound6 completely from my PC and now it works
P.S. And only now I see your post " If you wish to use Cabbage 3, just rename the Csound6 folder." 
If I wasn’t so happy, I’d be quite frustrated by this 
Happy days. Give it a go and see what you think!
I have attached the exported .log file from pluginval. Something I have noticed is that on neither of the two computers I have is the .vst3 recognized in Ableton Live (not even on the laptop where I was able to run the plugin in Cubase). I hadn’t tested it in Ableton before, and there it is not detected and does not appear in the list.
Plugin val .log:
Starting tests in: pluginval / Scan for plugins located in: C:\Program Files\Common Files\VST3\Cabbage\keyb.vst3\Contents\x86_64-win\Release\keyb.vst3…
creating serverCabbage DEBUG: Resetting csound …
csound = 0x00000265BC4738C0 Cabbage.cpp (114) cabbage::Engine::setupCsound [Thread ID: 10388]
Num plugins found: 1
Starting tests in: pluginval / Plugin info…
Starting tests in: pluginval / Editor…
Finished validating: C:\Program Files\Common Files\VST3\Cabbage\keyb.vst3\Contents\x86_64-win\Release\keyb.vst3
*** FAILED WITH EXIT CODE: 3221225477
Finished batch validation
I will test with Ableton Live tomorrow. Pluginval doesn’t give us much info in this case. I’ll try it myself tomorrow at the highest level and see if I can manage to trip it up.
