pretty-ts-errors VS Vim

Besides the features TypeScript itself proposed, the most important thing it brought to the community was the ability to create cool features around this compiler that enhance the developer experience and productivity. Tools like tsserver, pretty ts errors, and many others are actively improving the ecosystem for both JavaScript and TypeScript writers.

Being heavily inspired by VSCode plugin for prettifying TS error messages, I decided to try and create similar as Neovim plugin.

#1: VSCode extension that makes TypeScript errors prettier and human-readable | 28 comments #2: Those who know, know... | 63 comments #3: Announcing TypeScript 5.0 Beta | 24 comments

Is there anything similar to this project for neovim: https://github.com/yoavbls/pretty-ts-errors

It is already reported though: https://github.com/yoavbls/pretty-ts-errors/issues/3

I find the Vim extension for VS Code has macro support that is good enough for most of my use cases (if you’re a fan of Vim key bindings - obviously).

https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...

that's why I just use https://github.com/VSCodeVim/Vim if I have to use VSCode

They have discussions enabled on the GitHub repository; eventually r/vscode might be of help.

What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.

The extension does have visualedit. You can check the list of supported features here: https://github.com/VSCodeVim/Vim/blob/HEAD/ROADMAP.md

I though VSCode's vim emulation had issues with code folding

Either I go with K552 or save for RK84 if not CB-GK-16 and both of these are pretty good choice that's certain, or I go with 617 Fizz and use VIM keybinding which Isn't an issue for me cause I've been using NeoVim for more than 1 year, you can grab my dotfiles if you want. Most people won't go with 60% cause they are used to arrow, home, end ... keys so am I with vs code but today I found out about vscodevim extension which enables vim keybinding , these keybindings pretty easy to use more than arrow, home, end .. keys if yo're a vim user like Shift + $ = end, Shift + 0 = home, in visual mode V to select text etc ...