vim-code-dark VS neovim

I'm new to Neovim stuff so I could have gone wrong in my configuration but everything seems working. For now, I've switched to tomasiser/vim-code-dark since it supports treesitter out of box but the module mismatch issue I'd mentioned is still in vim-code-dark and every other colorscheme I've tried. Is this a treesitter bug? Any advice would be appreciated

try out this theme instead, it might work better: https://github.com/tomasiser/vim-code-dark

I made a port of vim code dark, which is the vscode dark+ default theme.

codedark? https://github.com/tomasiser/vim-code-dark

FYI, vim-code-dark, a vscode dark+ port, has been around since 2017.

tomasiser/vim-code-dark Dunno why, but I just love this theme

I am using treesitter for typescript, and now markdown too. I want the standard VS Code colour scheme you can see at https://vscode.dev/github/Microsoft/vscode. I am using https://github.com/tomasiser/vim-code-dark, but there is also https://github.com/Mofiqul/vscode.nvim available.

The picture is Neovim using https://github.com/tomasiser/vim-code-dark and https://microsoft.github.io/vscode-codicons/

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.