vscode-recipes VS vim-plug

have you tried vscode team recipe for angular debugging? https://github.com/Microsoft/vscode-recipes/tree/master/Angular-CLI

Now let's learn how to debug a Jest test. For this section, I will be using the vscode-recipes repository. First go to the site and clone the repository. Then go to the debugging-jest-tests/ directory. You will find two directories: lib/ and a test/. This is our workspace root directory.

Vue.js debugging in Chrome and VS Code This recipe shows how to use the Debugger for Chrome extension with VS Code to debug Vue.js applications generated by the Vue CLI.

https://github.com/microsoft/vscode-recipes/tree/master/Electron did you try this?

You debug the electron main process with the node-debugger (Node.js Preview) and the renderer process with the Chrome Debugger (Chrome Preview), You don't need to install any extension as they are both bundled with VScode, you need to set up your launch.json properly. as mentioned in the other comment, follow https://github.com/Microsoft/vscode-recipes/tree/master/Electron

vim-plug

Did you really install VimTeX? Did you run :PlugInstall? Ensure you installed and set up vim-plug correctly (https://github.com/junegunn/vim-plug). If VimTeX is installed, it should be installed to '~/.vim/plugged', thus you can open a terminal, then cd ~/.vim/plugged/vimtex and you should find the files there.

If you're determined to use vim for some reason, I'd suggest checking out vim-plug: https://github.com/junegunn/vim-plug. Quite useful for installing and maintaining all of the plugins that you're going to need to get vim to provide even a subset of the features offered by modern editors.

I encourage you to add plugins to your vim (tip: use vim-plug). Use vimawesome.com for inspiration.

Personally, I like https://github.com/junegunn/vim-plug

But the plugin manager https://github.com/junegunn/vim-plug can also install from offline sources, without accessing Github:

To get started, simply install the plugin using your favorite plugin manager, such as vim-plug or packer.nvim. You can find detailed installation instructions in the README.

Not sure if Vundle did anything particularly fancy, but I'm using vim-plug [0] and have no complaints. It stays out of my way to the point that I had to look at my .vimrc just now to make sure that's what I was using.

[0] https://github.com/junegunn/vim-plug

I chose to move on to vim-plug and can report it was a simple switch from Vundle.