Whichever library you are working with I strongly suggest you download the snippets for them. This makes it easier to see where you may be missing one and can help you see where your functions are efficiently. This makes it easier to see where all your brackets are and which bracket they match up to. Speaking of a missing bracket… This extension colors your brackets and parens n pairs. missing that stupid bracket since your format will start looking off once it hits that spot that is missing one. This helps keep your code clean and readable and can help you figure out where you may be.

These are based on rules your set or the default rules that they provide for you. This extension makes it really easy to see where your mistakes are, gives you a point and click the option to fix most of them, and auto formats for you. It can also give you some insight about the progression of the file to get a better understanding of requirements and so you don’t fall into the same traps someone before you may have already fallen into.ĭepending on your setup or your team’s setup you may use ESLint, Prettier, or both. This makes it really easy to see where an issue may have occurred and where you should start debugging at, what mistakes you had made, or potentially what changes you have made locally that may have caused an issue. HOWEVER, what most people don’t know is it also lets you see each commit diff that has been made on that file and the changes that were made. Most people use it just to see inline who made the last commit for each line and what the commit message was. This extension is by far the most useful extension in VS Code. Throughout the years I have tried a lot of different Visual Studio Code extensions but there are a few extensions that I always download with every new computer and struggle to work without.

Visual studio code extensions eslint