VS Code Extensions For Web Dev Productivity

-

Replace your editor colorful, elegant, and robust.



Photo by luis gomes from Pexels




VS Code is an open-source, cross-platform source code editor that’s become famous, particularly in the web development community. One of the most impressive parts of the Visual Studio Code is customizability, especially via extensions.  Let's see!!




 # Debugger For Chrome






This extension gives you all (or close to all) of those debugging features right inside of VS Code!


 # Javascript (ES6) Code Snippets





This extensions provides you with snippets for popular pieces of modern (ES6) JavaScript code.


  # ESLint{ }




This extension can be configured to auto-format your code as well as "yell" with linting errors/warnings.



 # Bracket Pair Colorizer






Bracket Pair Colorizer (as you might expect) colors matching brackets to make your code much more readable. This is actually cool!



 # Browser preview 





It gives you a live-reloading preview right inside of VS Code. No more having to tab over to your browser to see your code changes.


 # Prettier






If you don't need the linting part, then go with Prettier. It's super easy to setup and can be configured to formatted your code automatically on save.


 # Prettier
     






 # Path Intellisense





This extension is the best at autocompleting filenames.


If anything is not clear or you want to point out something, please reach me -- Mail me !.



Location: Coimbatore, Tamil Nadu, India

Comments

Post a Comment

Popular posts from this blog

Essential git commands every developer should know

-
Image
There are some lesser-known  Git  commands that may make your life easier. We all have our everyday  Git  commands that we use over and over. But what if I told you there are some lesser-known  Git  commands that may make your life easier . Let's See! Photo by  Luke Chesser  on  Unsplash   # git add-p       We all may know the command  git add <file>  or  git add. But Why do we need to know git add -p      Ever wanted to commit just a section of a file and not the entire thing? Once this command runs, we’ll be asked about " hunks ". " Hunks " are the  chunks  of code that we'll decide what to do with. You’ll see the question, " Stage this hunk [y, n, g, a, d, e, ?] ?" at the bottom of the terminal.     What Do those letters mean: y: stage this hunk n: do not stage this hunk g: select a different hunk to go to a: stage this hunk and all the other hunks in this file d: do not stage this hunk or any of the other hunks in this file e: edit the c
Read more