Member-only story
The Trouble Plugin in Neovim
I have been using the trouble.nvim plugin in Neovim for a while now and it really has improved my development experience. I work predominantly in Typescript and as such I run into many type errors throughout the day.
When working in large codebases, half the battle is finding the right file to update and then finding the right code in that file which needs fixing. This is where Trouble comes in. It provides a convinient interface to list all the current errors or warnings you may have and enables you to find them quickly.
Working With Trouble
When you are working in a file that has warnings or errors, you can open the Trouble window pane (in the latest version this is configurable in how it opens) and it lists all the errors/warnings that are in that file (or any file you have open in Neovim).
You can then traverse this list and if you select any item in this list then you jump to the specific line in the code where that item happens to be. This way you can quickly and easily navigate to where you errors/warnings are and fix them one by one.
Setting Up Trouble
On the Trouble Github page there are plenty of instructions about how to setup and configure the Trouble plugin. The standard setup and installation if you are using Lazy plugin manager…
