I took another break from VSCode to continuing playing around with NeoVim and coc.vim. The initial testing had pretty cool results, like showing basic lint warnings. Next was to get some of the doc popups like this:
When learning new tools I typically start at the beginning of the README and just learn as much as I can front to back. I didn’t have to read too far on the coc page to find the example Vim configuration, which opened up a huge world of options including the floating doc menu from VSCode:
The only bad part was the colors. After hacking around a bit on my color scheme I returned to the coc github page to read the FAQ. It has to be a common problem, right? YUP! The quick answer was to use gruvbox color scheme:
The following night I dug into the TS/JS language server. Following the same RTFM process, I went to the coc-tsserver README which calls out right away that you should configure a jsconfig.json file.
Not sure how I missed this when using VSCode as they indicate that a hint will be offered. It should probably be a long unstoppable nag screen due to how useful it’s been for my codebase :) More on that later.
The JavaScript experience is improved when you have a jsconfig.json file in your workspace that defines the project context. For this reason, we offer a hint to create a jsconfig.json file when you open a JavaScript file in a fresh workspace.
Here’s the basic jsconfig.json I’ve got right now. Be sure to keep these settings and the similiar ones in your eslint config in sync.